Prompt pack4 steps7 prompts
Product Roadmap Planning
Use this when the next quarter needs a public list of bets, not a backlog dump. Inputs and goals first, then one prioritized roadmap, then you tell people and track it.
01Inputs and goals
Customers, sales, support, analytics, competitors. Then 3–5 objectives. Do not roadmap before the goals exist.
- ProductOKR & Goal SettingCreate OKRs (Objectives and Key Results) and goals for product teams with measurable outcomes.
- ResearchMixed-Source Research SynthesisCombine already-coded interviews, surveys, and analytics into one report. For a single session use Session Debrief From Transcript. To cluster interview notes, use Affinity Mapping Assistant, then Research Insight Statement Writer.
- ProductCompetitive UX AnalysisAnalyze competitor products to identify UX patterns, strengths, weaknesses, and opportunities.
02Prioritize and draft
Score, cut, sequence. Themes not a hundred line items. Engineering in the room for size.
03Align and publish
Internal gets dates and tradeoffs. Customers get themes. Write down what you refused.
04Track
Progress against the bets, not theater. Change the roadmap when reality does. Say so.
Frequently asked questions
Should the QBR include next-quarter OKRs?
A slide of intent is fine. The working list lives here so it can change without rewriting the QBR.
How many bets?
Three to five themes, not a hundred tickets. If everything is P0, you do not have a roadmap. You have a backlog with dates.
We already changed course mid-quarter. Start over?
No. Update the not-doing list and tell people. Do not wait for the next QBR to admit it.