The ticket is the product's memory
Why every story I hand over carries a user story, Given/When/Then criteria, what is out of scope and who it depends on.
Short pieces on product ownership, organising, research and working with AI. Each one comes from the work itself, with the numbers left in. A new piece appears every week.
Why every story I hand over carries a user story, Given/When/Then criteria, what is out of scope and who it depends on.
Three habits from community organising with Citizens UK that carried straight into product work: the ask, turnout and accountability.
A requirement that guesses at today's behaviour writes a bug into the product. Look at the data and the code first.
What AI tools actually saved me, in numbers, and the human checks that made each of those savings worth having.
Write to me about anything here, or about product ownership and organising in general.