Acluebox logoAcluebox

Roadmap Scenario Planning

Build multiple roadmap scenarios from team capacity, dependencies and market windows, score against OKRs and flag critical path risks using structured AI prompts.

Roadmap Scenario PlanningOKR Scoring PromptProduct Roadmap AI

Objective: Create a reusable AI prompt that accepts explicit constraints (team capacity, dependencies, market windows), generates three distinct roadmap scenarios (aggressive growth, risk-mitigation, platform investment), scores each scenario against given OKRs, and surfaces critical-path risks so product and engineering leaders can decide with clarity.

The base prompt was formed through these deliberate steps:

  • Identify the mandatory inputs that every useful roadmap scenario must respect: quantitative team capacity, hard dependencies, and time-bound market windows.
  • Define the exact set of scenarios the model must always produce so outputs remain comparable across runs.
  • Require chain-of-thought reasoning that first lists constraints, then builds each scenario, then scores, then isolates critical-path risks.
  • Force structured output (tables + bullet lists) so the result can be copied directly into planning documents.
  • Embed quality gates that reject vague language and demand concrete dates, headcount numbers, and risk likelihood/impact pairs.
Note

Keeping the scenario types fixed (aggressive growth, risk-mitigation, platform investment) makes side-by-side comparison reliable and prevents the model from inventing unhelpful variants.

Prompt Template
You are an expert product strategist and delivery lead. {{snippet:brand_voice}} Task: Generate three roadmap scenarios for the product initiative described below. Constraints (treat these as hard limits): - Team capacity: {{team_capacity}} - Dependencies: {{dependencies}} - Market windows: {{market_windows}} OKRs to score against: {{okrs}} Follow this exact chain of thought: 1. Restate the constraints in your own words and note any immediate conflicts. 2. Build Scenario A – Aggressive Growth: prioritise speed and market share, accept higher risk. 3. Build Scenario B – Risk-Mitigation: prioritise reliability and contingency buffers. 4. Build Scenario C – Platform Investment: prioritise reusable foundations and long-term leverage. 5. For each scenario produce: - High-level timeline (quarters or months) - Key initiatives with owner roles - Resource allocation against the given capacity 6. Score every scenario against each OKR on a 1-5 scale and give a one-sentence justification. 7. Identify the critical path for each scenario and list the top three risks with likelihood and impact. Output format: - Constraint summary (bullet list) - Three scenario sections with timelines and initiatives - Scoring table (Scenario | OKR | Score | Justification) - Critical-path risks table (Scenario | Risk | Likelihood | Impact | Mitigation note) Tone: {{tone}} Length: keep each scenario description under 250 words.
What is OKR?

OKR stands for Objectives and Key Results. It is a simple, widely used goal-setting framework that helps teams and organizations define ambitious goals and track measurable progress toward them.

ElementTypeExample value
{{snippet:brand_voice}}snippetSpeak in clear, decisive language suitable for executive stakeholders. Avoid jargon and filler.
{{team_capacity}}variable12 engineers, 3 designers, 2 PMs; max 40 person-weeks per quarter
{{dependencies}}variablePayment gateway certification (Q3), legal review of data residency (must finish before launch)
{{market_windows}}variableHoliday shopping peak starts 15 Nov; competitor major release expected mid-September
{{okrs}}variable1. Achieve 25% MoM active-user growth by end of Q4. 2. Keep P1 incident rate below 2%. 3. Ship the new billing module with <5% support tickets in first 30 days.
{{tone}}variableprofessional and concise
Prompt Example
You are an expert product strategist and delivery lead. Speak in clear, decisive language suitable for executive stakeholders. Avoid jargon and filler. Task: Generate three roadmap scenarios for the product initiative described below. Constraints (treat these as hard limits): - Team capacity: 12 engineers, 3 designers, 2 PMs; max 40 person-weeks per quarter - Dependencies: Payment gateway certification (Q3), legal review of data residency (must finish before launch) - Market windows: Holiday shopping peak starts 15 Nov; competitor major release expected mid-September OKRs to score against: 1. Achieve 25% MoM active-user growth by end of Q4. 2. Keep P1 incident rate below 2%. 3. Ship the new billing module with <5% support tickets in first 30 days. Follow this exact chain of thought: 1. Restate the constraints in your own words and note any immediate conflicts. 2. Build Scenario A – Aggressive Growth: prioritise speed and market share, accept higher risk. 3. Build Scenario B – Risk-Mitigation: prioritise reliability and contingency buffers. 4. Build Scenario C – Platform Investment: prioritise reusable foundations and long-term leverage. 5. For each scenario produce: - High-level timeline (quarters or months) - Key initiatives with owner roles - Resource allocation against the given capacity 6. Score every scenario against each OKR on a 1-5 scale and give a one-sentence justification. 7. Identify the critical path for each scenario and list the top three risks with likelihood and impact. Output format: - Constraint summary (bullet list) - Three scenario sections with timelines and initiatives - Scoring table (Scenario | OKR | Score | Justification) - Critical-path risks table (Scenario | Risk | Likelihood | Impact | Mitigation note) Tone: professional and concise Length: keep each scenario description under 250 words.

Extended example values:

  1. {{snippet:brand_voice}}

    • Speak in clear, decisive language suitable for executive stakeholders. Avoid jargon and filler.
    • Use short paragraphs and active voice; every sentence must advance a decision.

  2. {{team_capacity}}

    • 12 engineers, 3 designers, 2 PMs; max 40 person-weeks per quarter
    • 8 backend, 4 frontend, 2 QA; total available effort 36 person-weeks after holidays

  3. {{dependencies}}

    • Payment gateway certification (Q3), legal review of data residency (must finish before launch)
    • Core platform API freeze until 1 October; third-party analytics SDK upgrade required by 15 August

  4. {{market_windows}}

    • Holiday shopping peak starts 15 Nov; competitor major release expected mid-September
    • Enterprise RFP season opens 1 September; regulatory filing deadline 30 October

  5. {{okrs}}

      1. Achieve 25% MoM active-user growth by end of Q4. 2. Keep P1 incident rate below 2%. 3. Ship the new billing module with <5% support tickets in first 30 days.
      1. Reach 50k monthly paid seats. 2. Reduce average onboarding time to under 4 minutes. 3. Maintain NPS above 45.

  6. {{tone}}

    • professional and concise
    • analytical yet action-oriented
Tip

After the model returns the three scenarios, feed the scoring table back into a follow-up prompt that asks for a recommended primary scenario plus a short contingency plan. This keeps the decision loop tight and documented.

Roadmap Scenario Planning