Weeknotes 29 March, 2024

This has nothing to do with Weeknotes, but in the UK it’s been raining for… forever! And as we swap to British Summer Time this Sunday, I hope we start seeing brighter skies. I’d quite like to wear something other than a raincoat.

On the work front it’s been a productive week, despite it being a short week due to Easter. It’s looked a little like this…

Mapping goal key results into sprints. It’s one thing to create goals, another to make sure they stay on track. I have 4 key goals for the first half of the year. I’m keen to make sure I’m consistent with progress. So, I’ve planned out the sprints up to the end of June with tasks aligning to each one of my 4 goals. The intention is this will hold me accountable. It’ll also give me a sense of continual achievement as I move through every 2-week sprint.

Defining a “keep the lights on” process for content optimisation. We have the bigger, roadmap topics sorted but no real process for making sure little snags get fixed. I’ve jotted down ideas for what a process could look like. I’ve asked for feedback on this, and I’ve also chatted with the usual content clan over Slack.

I’ve created a few things so far:

– A spreadsheet to log content improvements and monitor status.
– A Figma file with the rough process, plus before and after versions of content.
– Templates. One for a Jira ticket. One for comms about handover to engineering and wider awareness in the business.

Coaching training. I want to brush up on my coaching skills as part of my personal goals. This week I completed Coaching Skills for Leaders and Managers by Sara Canaday. I have a 1:1 with my direct report today about her goals. I’ll use this as an opportunity to put into practice some of the tips I’ve learned.

Summarising copy testing findings in a new research repository. This is the next step on from the spreadsheet I’m using for terminology questions. I’m logging final decisions and including tips on how to format terminology in practice. It’s a bit admin heavy doing this, but it gives us a link to evidence we can share in conversation if needed. And, of course, it’s a record of tested terminology we should be using.

Feature adoption analysis. This is a new project I’m working on with our growth team. We have quite a few features our users don’t make the most of. Some of these features can make our users’ lives easier, especially when used together. I had a great meeting yesterday about the interventions we can make and how to angle the content.

Have a good long weekend if you’re in the UK.