Lifecycle · Phase 3 of 8
Planning turns a validated opportunity into clear priorities, sequencing and success measures. With 85 templates, it is the largest phase in Gensudo’s library, reflecting the role every team member plays in planning.
Planning turns a validated opportunity into a clear commitment. It defines what the team will prioritise, what it will not pursue, how work will be sequenced and how success will be measured. The decisions made here, including priorities, roadmap, resourcing and success measures, shape every phase that follows.
By the end of Planning, the team should be clear on:
Gensudo includes 85 planning templates across five product roles, making Plan the largest phase in the library. Every role contributes, led by the Head of Product with 21 templates, followed by the Product Manager with 19, Creative Director with 17, Product Director with 15 and Product Owner with 13. Key documents include the Product Vision Statement, OKR Alignment Document, RICE Scoring Sheet and Product Roadmap. Each template includes clear guidance on why it matters, what good looks like and who needs to approve it, helping teams create planning documents that are ready to guide action, not simply be completed.
Restate where this product is going and why, in a Product Vision Statement, and connect it to the organisation's objectives through OKR alignment. Priorities argued without an anchor never stay argued.
Put candidate work through a consistent lens — a RICE Scoring Sheet or similar — so that prioritisation is visible reasoning rather than the loudest voice.
Order the work by value and dependency, not by who asked first. A decision-grade roadmap shows why things sit where they do.
For each objective, write down the measure, the target and the read date — before the work starts, while nobody has anything to defend.
Walk stakeholders through the plan and the trade-offs inside it. Sign-off means they saw what was declined, not just what was chosen.
Because every role plans. Of Gensudo's 382 templates, 85 sit in the Plan phase — the Head of Product alone has 21 planning documents, and even the lightest role carries 13. Vision, objectives, prioritisation, roadmaps and resourcing all have to be written down somewhere, and each role sees planning from a different altitude, so the documents genuinely differ rather than duplicate.
Use a consistent, visible scoring method — a RICE Scoring Sheet is the classic — so every candidate is judged on the same dimensions and the reasoning survives the meeting. The score isn't the decision; it's the starting position that forces disagreements to be about evidence rather than volume. Gensudo's quality scorecard specifically checks for scored matrices because they're what separates a ranked plan from a list.
A decision-grade roadmap shows its working: why items sit in this order, what each depends on, what was declined and what success will be measured by. A list of features with quarters attached is a communication artefact, not a decision artefact. The test is whether someone outside the team could read it and understand not just what's coming, but why.
The plan should change whenever the evidence does — that's not a failure of planning, it's the point of writing measures down. What shouldn't change silently is the record: when priorities move, the reasoning moves with them. Later phases, particularly Optimise, exist to feed real performance back into exactly this document.
A plan is only as strong as the evidence beneath it. If priorities feel arbitrary, the validation case may need another look.
Revisit the Validate phase →With priorities set, the top of the roadmap needs specifying - exactly what gets built, precisely enough to build it.
Go to the Define phase →Roadmaps, OKRs and scoring sheets with guidance built in - and AI drafting that proposes, cites and always leaves the judgement with you.