Roadmap Presentation Skill
Build roadmaps that tell a strategy story — not just a list of features with dates. Every roadmap output is audience-calibrated: executives get outcomes, teams get specificity, customers get value.
Required Inputs
Ask the user for these if not provided:
- Audience (executive/board, cross-functional, engineering, customers — changes format significantly)
- Prioritised initiative list with rough timelines or quarters
- Company OKRs or strategic goals (to anchor the narrative)
- Period covered (Q1, H1, full year, etc.)
Audience Calibration
Always ask who the audience is before building:
| Audience |
They care about |
Format |
| Executive / Board |
Business outcomes, revenue, risk, strategic alignment |
Outcome-led, 3 columns (Now / Next / Later), no sprint detail |
| Cross-functional stakeholders |
Dependencies, timelines, their team's involvement |
Theme-based, with dependency callouts |
| Engineering team |
Specificity, sequencing, technical constraints |
Detailed, with epics and rough sizing |
| Customers / External |
Value delivered, no internal detail |
Benefits-focused, no dates — "Coming soon / In progress / Done" |
The Now / Next / Later Framework
Standard output structure:
NOW (Current quarter — high confidence, committed)
- What we're building and why
- Expected outcomes
NEXT (Following quarter — medium confidence, directional)
- Themes and initiatives
- Key hypotheses being tested
LATER (6–12 months — low confidence, aspirational)
- Strategic bets
- Dependencies that need to resolve first
⚠️ Never put specific dates on "Later" items. Use quarters or halves.
Roadmap Narrative Template
Every roadmap needs a narrative, not just a timeline. Structure it as:
- Where we are — current product state and key metrics
- The problem we're solving — what's holding customers or the business back
- Our strategic bets — the themes that guide this roadmap
- What we're building — Now / Next / Later breakdown
- How we'll know it's working — success metrics per theme
- What we're not doing — explicit deprioritisation with rationale
Output Format
Product Roadmap — [Product Area] — [Quarter/Year]
Audience: [Executive / Team / Customer]
Roadmap Owner: [PM Name]
Last Updated: [Date]
Confidence Level: Now = High | Next = Medium | Later = Low
Strategic Context:
[2–3 sentences: what company/product goal does this roadmap serve?]
Guiding Themes This Period:
- [Theme 1] — [1-line rationale]
- [Theme 2] — [1-line rationale]
- [Theme 3] — [1-line rationale]
NOW — [Quarter]
| Theme |
Initiative |
Outcome Expected |
Team |
Status |
| [Theme] |
[What we're building] |
[Metric it moves] |
[Owner] |
In Progress / Starting |
NEXT — [Quarter]
| Theme |
Initiative |
Hypothesis |
Dependencies |
| [Theme] |
[What we plan to build] |
[If we build X, we expect Y] |
[What needs to be true first] |
LATER — [H2 / Next Year]
| Theme |
Strategic Bet |
Why Later |
| [Theme] |
[What we might build] |
[What's blocking or uncertain] |
What We're NOT Building (and Why):
- [Requested initiative] — Deprioritised because: [reason]
- [Requested initiative] — Deprioritised because: [reason]
Success Metrics for This Roadmap:
| Metric |
Now Target |
End of Year Target |
| [Metric] |
[X] |
[Y] |
Guidelines
- Never let a roadmap become a commitment list — frame everything outside "Now" as directional
- Always include a "not doing" section — it prevents the roadmap from becoming a wish list in disguise
- For executive audiences: lead with the outcome the roadmap delivers to the business, not the features
- Recommend a roadmap review cadence: monthly for Now items, quarterly for Next/Later
- If dates are demanded for Later items: use quarters (Q3 2026), not specific dates
Quality Checks
Anti-Patterns
1---2name: roadmap-presentation-23description: "Create structured roadmap presentations calibrated to any audience. Use when asked to build a product roadmap, present roadmap to leadership, create a roadmap slide, or communicate quarterly plans to execs, teams, or customers. Produces an audience-calibrated Now/Next/Later roadmap with strategic context, initiative tables, success metrics, and explicit deprioritisation rationale."4homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/roadmap-presentation.html5metadata:6 source: https://skillmd.com/skills/mohitagw15856/roadmap-presentation-27 openclaw:8 emoji: 🗺9---1011# Roadmap Presentation Skill1213Build roadmaps that tell a strategy story — not just a list of features with dates. Every roadmap output is audience-calibrated: executives get outcomes, teams get specificity, customers get value.1415## Required Inputs1617Ask the user for these if not provided:18- **Audience** (executive/board, cross-functional, engineering, customers — changes format significantly)19- **Prioritised initiative list** with rough timelines or quarters20- **Company OKRs or strategic goals** (to anchor the narrative)21- **Period covered** (Q1, H1, full year, etc.)2223## Audience Calibration2425Always ask who the audience is before building:2627| Audience | They care about | Format |28|---|---|---|29| **Executive / Board** | Business outcomes, revenue, risk, strategic alignment | Outcome-led, 3 columns (Now / Next / Later), no sprint detail |30| **Cross-functional stakeholders** | Dependencies, timelines, their team's involvement | Theme-based, with dependency callouts |31| **Engineering team** | Specificity, sequencing, technical constraints | Detailed, with epics and rough sizing |32| **Customers / External** | Value delivered, no internal detail | Benefits-focused, no dates — "Coming soon / In progress / Done" |3334---3536## The Now / Next / Later Framework3738Standard output structure:3940**NOW** (Current quarter — high confidence, committed)41- What we're building and why42- Expected outcomes4344**NEXT** (Following quarter — medium confidence, directional)45- Themes and initiatives46- Key hypotheses being tested4748**LATER** (6–12 months — low confidence, aspirational)49- Strategic bets50- Dependencies that need to resolve first5152⚠️ Never put specific dates on "Later" items. Use quarters or halves.5354---5556## Roadmap Narrative Template5758Every roadmap needs a narrative, not just a timeline. Structure it as:59601. **Where we are** — current product state and key metrics612. **The problem we're solving** — what's holding customers or the business back623. **Our strategic bets** — the themes that guide this roadmap634. **What we're building** — Now / Next / Later breakdown645. **How we'll know it's working** — success metrics per theme656. **What we're not doing** — explicit deprioritisation with rationale6667---6869## Output Format7071### Product Roadmap — [Product Area] — [Quarter/Year]7273**Audience:** [Executive / Team / Customer]74**Roadmap Owner:** [PM Name]75**Last Updated:** [Date]76**Confidence Level:** Now = High | Next = Medium | Later = Low7778---7980**Strategic Context:**81> [2–3 sentences: what company/product goal does this roadmap serve?]8283**Guiding Themes This Period:**841. [Theme 1] — [1-line rationale]852. [Theme 2] — [1-line rationale]863. [Theme 3] — [1-line rationale]8788---8990**NOW — [Quarter]**9192| Theme | Initiative | Outcome Expected | Team | Status |93|---|---|---|---|---|94| [Theme] | [What we're building] | [Metric it moves] | [Owner] | In Progress / Starting |9596**NEXT — [Quarter]**9798| Theme | Initiative | Hypothesis | Dependencies |99|---|---|---|---|100| [Theme] | [What we plan to build] | [If we build X, we expect Y] | [What needs to be true first] |101102**LATER — [H2 / Next Year]**103104| Theme | Strategic Bet | Why Later |105|---|---|---|106| [Theme] | [What we might build] | [What's blocking or uncertain] |107108---109110**What We're NOT Building (and Why):**111- [Requested initiative] — Deprioritised because: [reason]112- [Requested initiative] — Deprioritised because: [reason]113114**Success Metrics for This Roadmap:**115| Metric | Now Target | End of Year Target |116|---|---|---|117| [Metric] | [X] | [Y] |118119---120121## Guidelines122123- Never let a roadmap become a commitment list — frame everything outside "Now" as directional124- Always include a "not doing" section — it prevents the roadmap from becoming a wish list in disguise125- For executive audiences: lead with the outcome the roadmap delivers to the business, not the features126- Recommend a roadmap review cadence: monthly for Now items, quarterly for Next/Later127- If dates are demanded for Later items: use quarters (Q3 2026), not specific dates128129## Quality Checks130131- [ ] Format matches the audience (executives don't get sprint-level detail)132- [ ] NOW items are committed with owners; NEXT items are directional; LATER items are aspirational133- [ ] "What We're NOT Building" section has at least 2 items with rationale134- [ ] Success metrics are specified per theme (not just a list of features)135- [ ] Language is free of internal jargon — tested by asking: "could an external stakeholder understand this?"136137## Anti-Patterns138139- [ ] Do not put specific dates on NEXT or LATER items — use quarters or halves to signal appropriate confidence levels140- [ ] Do not show the same level of detail to executives and engineers — calibrate depth to audience or you lose both141- [ ] Do not omit the "What We're NOT Building" section — a roadmap without explicit deprioritisation becomes a wish list142- [ ] Do not present LATER items as commitments — frame everything outside NOW as directional, not promised143- [ ] Do not skip the success metrics section — without it, stakeholders cannot evaluate whether the roadmap is working