Weeknotes 13 March, 2026

Coming back from annual leave always carries a small moment of re-orientation. Not so much catching up on tasks, but re-establishing the rhythm of the work — listening for where things actually are, and where attention is most useful.

A lot of this week has been about deliberately keeping some space to look ahead. That’s a practice I’m trying to build more intentionally: lifting my focus slightly above the immediate delivery cycle and thinking about how the work needs to evolve. AI has been at the centre of that thinking, particularly what it means for a content team.

If AI lowers the cost of producing words, then the role of the content team shifts further toward shaping the conditions for good decisions. The question becomes less “who writes this” and more “how do we make it easy for teams to produce good content in the first place?” Guardrails, patterns, shared judgement. The work becomes less about writing everything ourselves and more about designing the environment where good content happens — while still protecting quality as teams move faster.

Alongside that, there’s been some quieter stitching-together work. Planning for time next week with Figma and some in-person time with the team. Reconnecting after being away. The kinds of conversations that help everyone recalibrate a little.

I also spent some time vibe coding — experimenting with ways to merge together some of the operational surfaces around content. While proofing features in staging I realised I had accumulated spreadsheet after spreadsheet: content audits, snag lists, proofing notes. Each useful in isolation, but collectively quite fragmented.

Using AI, I started consolidating those into a single spreadsheet. The aim is to move toward a clearer source of truth for product copy — something that makes it easier to see what exists, what needs attention, and where quality might drift over time.

There’s some experimentation in that work, but it also needs care. When you centralise something like this you create new dependencies, and the shape of the system matters. Done well, it could make the content landscape much easier to navigate. Done poorly, it becomes another surface that quietly goes out of date. So the experiment is as much about the process around it as the document itself.

Overall it felt like a week of re-establishing direction — making some of the thinking about where content is heading a little more visible, and beginning to shape the systems that will support the team as the work changes.