The trigger for introducing a Change Advisory Board wasn’t a single incident. It was a pattern that became impossible to ignore. Feature requests were arriving from multiple directions — some with clear context and ownership, others more informal. A pain…
Note on naming: Google has quietly dropped the ‘GA4’ label — the platform is now referred to simply as Google Analytics. References to GA4 in this article reflect how the tool was known when this decision was made. Three years…
I started with a time constraint, not a spec. Here is the product thinking that shaped my AI content workflow — and what it actually delivers.
Backlog prioritisation breaks down when urgency is used as a proxy for importance. The solution isn’t a better framework — it’s a system that separates time-sensitivity from business impact, makes trade-offs explicit in the room, and protects capacity for work…
AI drafts product specifications more accurately when the key decisions are already made — scope defined, constraints known, acceptance criteria roughed out. The brief that makes a good AI prompt is the same thinking a good spec requires: if you…
ICE scoring is a prioritisation framework that ranks backlog items by multiplying three factors: Impact, Confidence, and Ease. Each is scored on a 1–10 scale. Multiply them together and you get a number out of 1,000. The highest scores rise…
A backlog isn’t just a to-do list. Story mapping helps Product Owners see the user journey, find the MVP, and align stakeholders on what to build next.
Every request feels urgent, but some delays cost more than others. Cost of Delay and WSJF help Product Owners decide what really can’t wait.
Not all features make customers happy. The Kano Model helps you distinguish between basics, performance boosters, and delighters, and balance them in the roadmap.
Backlog debates don’t have to be opinion-based. The RICE framework helps Product Owners compare features using reach, impact, confidence, and effort.
