For PMs: turn strategy into roadmaps, specs, sprints, and the metrics to prove it shipped.
Reach for this when you own a product line and need to move from strategy to shipped, measurable outcomes without switching tools for every artifact. It carries you across the full PM loop: set OKRs, build a roadmap leadership trusts, ground decisions in personas and user flows, hand engineering crisp specs and tickets, run the sprint, then read the analytics to see if it worked. The result is a product org aligned on outcomes instead of a feature list - and a paper trail that survives the next reorg.
Click to play with sound.
Arranged in the author's recommended order. Walk through them in sequence, or open any one on its own.
Turns product strategy into a themed Now/Next/Later roadmap with explicit trade-offs, confidence levels, and no committed dates beyond one quarter.
Writes engineering design docs and RFCs that align a team before code – TL;DR, background, goals and explicit non-goals, quantified requirements, a concrete end-to-end design with failure modes, alternatives considered, rollout plan.
Synthesizes interview notes, surveys, support tickets, and analytics into evidence-based user personas that drive design decisions, with every claim traced to source data.
Facilitates sprint planning end to end – backlog refinement checks against a Definition of Ready, a one-sentence sprint goal, capacity math from velocity and PTO, story selection and team commitment, task breakdown, and flagged risks with owners.
Drafts a quarter's OKRs – an inspiring qualitative objective with 3-5 measurable key results, each with a baseline, target, and owner – plus the weekly confidence check-in and end-of-quarter grading cadence.
Stands up product analytics from decision questions backward – a north-star metric with an input-metric tree, an object-action event taxonomy with a governed tracking plan, and the priority analyses to build first: activation funnels.
Maps a feature's complete user flow in text notation – happy path first, then decision branches, error and empty states with recovery, edge cases, and re-engagement – and flags the top risks before design or build.
Writes ready-to-build Jira stories with user-story summaries, Given/When/Then acceptance criteria, subtasks, and story-point guidance, checked against INVEST and a Definition of Ready.