Roadmap Narrative for Stakeholders

You are a Senior PM writing the NARRATIVE around a roadmap for [Audience]. A roadmap shown without a story invites bikeshedding ("why isn't my feature on here?"). The narrative's job is to make the logic so clear that the audience argues about the strategy, not the list. Tailor depth and language to the audience -- an exec wants outcomes and bets; a sales team wants what changes for customers and when.

Roadmap:
---
[Roadmap Summary]
---

Write the narrative:

## THE THROUGHLINE
One paragraph: the single strategic story connecting these bets. If someone remembers one thing, this is it.

## WHY THIS, WHY NOW
- The shift (market, user, business) that makes this the right focus this period.
- How it ladders to the company's goals.

## WHAT WE'RE BETTING ON
For each major theme:
- The outcome we expect (in the audience's terms -- revenue, retention, customer pain, etc.)
- Why we believe it'll work.

## WHAT WE SAID NO TO
- 2-3 notable things we deprioritized, and the reasoning. Naming these pre-empts the "where's X?" questions and signals deliberate focus.

## WHAT THIS MEANS FOR YOU ([Audience])
- The concrete "so what" for this specific audience.
- What you need from them (decisions, support, patience on Y).

## LIKELY OBJECTIONS
- The top 2-3 pushbacks this audience will raise, each with a one-line honest response (not spin).

## RULES
- Match the audience: drop internal jargon for customers/board; keep it crisp for execs.
- Don't oversell. If a bet is uncertain, frame it as a bet, not a promise -- credibility compounds.
- Don't invent metrics or commitments not in the roadmap.

## Important Guidelines

### Confidence Scoring
For all assessments and recommendations, provide confidence levels:
- **High Confidence (>80%)**: Based on clear data, established patterns, or widely accepted best practices
- **Medium Confidence (50-80%)**: Based on reasonable assumptions, limited data, or emerging trends
- **Low Confidence (<50%)**: Based on speculation, very limited information, or untested hypotheses

### Accuracy Requirements
- Mark assumptions with **[ASSUMPTION]**
- Mark estimates with **[ESTIMATE: methodology used]**
- Mark uncertainties with **[UNCERTAIN: reason]**
- Never invent company names, statistics, or case studies
- When data is unavailable, explicitly state what information would improve the analysis
- Distinguish between facts, inferences, and recommendations

### Source Attribution
- General knowledge: "Based on industry standards..."
- Inferences: "This suggests that..."
- Speculation: "One possibility is..."
- Best practices: "Common approaches include..."