When I started writing Weeknotes, they were never intended to be a list of tasks. Every Friday, I send our Head of Design weekly updates and what’s happened is these 2 have somehow become 1.

In some senses that’s a sub-conscious win (create once, publish everywhere). Yet, in a bid to be efficient, I’ve lost the element of reflection from my Weeknotes. I want to get back to this so I’m going to try something new by rotating a few reflection frameworks. I’m going with start with a three-part lens designed to help me pause over what’s gone down this week. Here goes.

👀 What I noticed

• The way you frame things matters more than you realise. And small tweaks make huge differences.
• I need to shift more from task tracking to reflecting on outcomes. For example, thinking what I was doing 6-12 months ago and what I am doing now.
• We had a mad rush to get some prototypes ready for public presentations – and my team enjoyed it. Was it full on? Yes. Was it stressful? No. Will I do things differently next time? Yes – read on.

💡 What I learned

• Get a list of global events in our domain. I’ll put prep time in our diaries before these events so that plan creating presenter assets.
• Guardrails matter. Blocking calendar time for deep work has a visible impact on stress levels.
• I need to find a way to remind myself to follow up on UX Writing surveys and feedback forms. Something better than sticking it in my diary. Kevin (what our team calls ChatGPT) has given me some ideas this moment).

🎯 What’s next

• Get that list of events.
• Dig out the recording of our UX Writing session with engineers and re-circulate it.
• Try to remember the things and I’ve learned and take them into next week.