Weeknotes 505
I did:
Balancing
Four day week so being super efficient, I got this stuff done:
- Talked about getting more balance in our decisions by ensuring we have multiple perspectives.
- Wrote a retro analysis and report.
- Went to a really good review and planning session lead by one of our brilliant delivery managers. It’s so good to see a data-driven approach in action which over time will make delivery predictions far more accurate.
- Passed beta-to-live stage-gate.
- Planned the rollout of our new product. Adoption is always the hardest part of product work.
- Chatted about the difference between metrics that measure product performance and those that measure usage, because you should be able to judge the success of a product regardless of how many users it has.
- Thought about how to better support product managers with some workshop-y training sessions.
I read/watched:
What are the chances AI will replace universities?

Good to know.
Towards the evaluation of UX
Interesting collection of papers about user experience.
How to write for AI search
SearchEngineLand’s playbook for machine-readable content got me thinking about
Abandon cart emails
Read some research on abandon cart emails to help me think about how best to use them with some of our products.
- The Effectiveness of Triggered Email Marketing in Addressing Browse Abandonments
- The determinants of consumers’ online shopping cart abandonment
- Examining online shopping cart abandonment through the lens of consumer confusion
- The psychology behind cart abandonment: why do customers leave without buying?
I thought:
Taxonomies, topologies and ontologies
Thinking about how we think about how to organise things, taxonomies, topologies and ontologies provide three different (and easily confused) ways.
Easy as a strategy
Thought about the assumption that making an interface easier to use must lead to higher conversion. I’m not saying products should have interfaces that are hard to use, far from it, but how do easy-to-use interfaces create a competitive advantage? I don’t see it. I don’t see a cause-and-effect relationship between a user’s experience once they are using a product and getting more people to start using a product, there’s a lot more to it than that.
Time flies
Five years ago I was talking about asynchronous working for product teams and thinking about how we understand problems.