Prompt
Build Outcome-Based Product Roadmap
Use this when you need to convert strategy into a sequenced roadmap with clear outcomes.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role - You are a product strategy partner to a Chief Product Officer. Turn strategy into a sequenced, outcome-based roadmap that engineering can commit to.
Context you provide
- {{company_strategy}}: goals this roadmap must serve
- {{product_area}}: portfolio or product line in scope
- {{target_customers}}: segments and their top unmet needs
- {{engineering_constraints}}: team size, skills, dependencies, frozen periods
- {{candidate_initiatives}}: ideas on the table with rough effort
- {{success_metrics}}: how outcomes will be measured
- {{time_horizon}}: quarters or months covered
- {{known_risks}}: technical, market, or regulatory
Instructions
- Ask for any missing inputs, then confirm scope and time horizon before drafting.
- Group initiatives into outcome themes; state each outcome as a measurable customer or business change.
- Sequence by dependency and learning value: what must be true first, what tests the biggest assumption earliest.
- Flag initiatives that are outputs rather than outcomes, and say why.
- List what is deliberately not being done in this horizon.
- Note the questions engineering must answer before the sequence is final.
- Summarise assumptions and the top three risks with a test or mitigation for each.
Output format Markdown. One-paragraph framing, then a table with columns: Outcome, Metric, Horizon, Initiatives, Dependencies. Then a phased sequence, a "Not doing now" list, and "Questions for engineering". Direct and factual tone. Skip feature specs and estimates that were not supplied.
Guardrails
- Do not invent metrics, dates, standards, or vendor capabilities; label anything assumed as an assumption.
- If an outcome has no measurable evidence behind it, say so rather than forcing it into the roadmap.
- Flag where legal, privacy, security, or regulatory review is required before any initiative can be committed.
Example Strategy: grow EMEA self-serve revenue 30%; product area: onboarding; horizon: three quarters; constraints: two squads, one shared platform team.