/roadmap-frameworks

name: roadmap-frameworks
description: "Product roadmap frameworks including Now-Next-Later, outcome-based, and timeline formats. Use when creating a product roadmap, presenting strategy to executives or customers, planning quarterly initiatives, or choosing a roadmap format for your audience. Trigger on: 'create a product roadmap', 'what roadmap format should I use', 'plan next quarter', 'roadmap for executives vs engineering', 'now next later template'."

Roadmap Frameworks

Frameworks for building, communicating, and managing product roadmaps that align teams, guide execution, and drive strategic outcomes.

What is a Roadmap?

A roadmap is a strategic communication tool that:

• Shows **WHERE** you're going (direction, themes)
• Explains **WHY** you're going there (strategy, rationale)
• Indicates **WHEN** (roughly) you'll get there (timeframes)
• Communicates **HOW** you'll get there (initiatives, bets)

**NOT**: A list of features with dates **BUT**: A strategic narrative about the future

**Good roadmaps**: Outcome-oriented, flexible, strategic, audience-appropriate, actionable

**Bad roadmaps**: Feature lists, hard dates, everything for everyone, disconnected from strategy, stale

When to Use This Skill

**Auto-loaded by agents**:

• `roadmap-builder` - For Now-Next-Later, theme-based, and outcome roadmaps

**Use when you need**:

• Quarterly/annual planning
• Strategic clarity
• Team alignment
• Clear communication
• Investment decisions
• Customer/user communication

---

Roadmap Types

1. Now-Next-Later (Recommended for Most)

**Structure**: Three buckets without dates

## NOW (High confidence - actively building)
- [Initiative]: [Outcome] — Owner: [name], Status: [in-progress]

## NEXT (Medium confidence - validated, queued)
- [Initiative]: [Outcome] — Target: [quarter]

## LATER (Low confidence - exploring)
- [Initiative]: [Outcome] — Needs: [validation step]

**When to use**: Maximum flexibility, minimal commitment, high uncertainty

**Benefits**:

• No date commitments
• Easy to adjust
• Clear focus
• Simple communication

**Template**: `assets/now-next-later-template.md`

Complete template with examples, confidence levels, updating guidance

---

2. Theme-Based

**Structure**: Strategic themes with grouped initiatives

Organize by themes (e.g., "Enterprise Readiness", "Customer Experience") rather than features.

**When to use**: Communicate strategic focus areas

**Benefits**:

• Strategic clarity
• Outcome-focused
• Flexible within themes

---

3. Outcome-Based

**Structure**: Lead with results, not outputs

Focus on customer/business outcomes (e.g., "Reduce churn by 50%") with flexible approaches.

**When to use**: Results-driven teams, goal-driven culture

**Benefits**:

• Clear success criteria
• Measurable
• Team autonomy on "how"

**Template**: `assets/outcome-roadmap-template.md`

Includes outcome format, examples, comparison with feature roadmaps

---

4. Timeline

**Structure**: Initiatives plotted on calendar/quarters

Visual timeline showing sequencing and dependencies.

**When to use**: Internal planning only, complex dependencies

**NOT for**: External communication (creates date expectations)

---

**Choosing the right type**: See `references/roadmap-types-guide.md` for detailed comparison and selection criteria.

---

Roadmap by Audience

Different audiences need different roadmaps:

Executive Roadmap

**Focus**: Strategy, business outcomes, resource needs **Format**: Themes + outcomes, annual + quarterly **Detail**: Low (strategic)

Customer Roadmap

**Focus**: Value delivery, transparency **Format**: Now-Next-Later with problem framing **Exclude**: Internal work, hard dates

Sales Roadmap

**Focus**: Deal enablement, competitive positioning **Guidance**: "Commit to Now, position Next as likely, describe Later as exploring"

Engineering Roadmap

**Focus**: Execution, technical detail **Format**: Timeline with dependencies **Detail**: High (sprint-plannable)

Internal All-Hands

**Focus**: Company alignment, transparency **Frequency**: Quarterly updates

**Comprehensive guide**: `references/roadmap-communication-guide.md`

Includes communication tactics, update formats, anti-patterns

---

Building Your Roadmap

7-Step Process

**Step 1**: Establish Strategy (company goals, product strategy, market position)

**Step 2**: Gather Inputs (customer feedback, business priorities, technical needs, competitive intel)

**Step 3**: Prioritize (RICE, Impact/Effort, Strategic Fit)

**Step 4**: Define Themes (3-5 customer-centric, strategic themes)

**Step 5**: Sequence (dependencies, resources, timing, value delivery)

**Step 6**: Validate & Align (exec, engineering, sales/CS, customers)

**Step 7**: Communicate (audience-specific views, all-hands, documentation)

**Detailed guide**: `references/roadmap-building-guide.md`

Includes detailed steps, outputs, prioritization frameworks, maintenance cadence

---

Roadmap Narrative

Tell the story of your roadmap - where, why, how:

**Structure**:

1. Vision (where we're going) 2. Strategy (why this roadmap) 3. Prioritization approach (how we chose) 4. What we're building (Now, Next, Later) 5. Trade-offs (what we're NOT doing) 6. Feedback process (how to influence)

**Template**: `assets/roadmap-narrative-template.md`

---

Roadmap Best Practices

**DO**:

• Start with strategy (not features)
• Use themes and outcomes (not feature lists)
• Tailor to audience (exec, team, customer)
• Show trade-offs (what you're NOT doing)
• Update regularly (quarterly planning, monthly review)
• Communicate changes (transparency)
• Link to metrics (measurable outcomes)
• Keep "Now" specific, "Later" vague

**DON'T**:

• Commit to dates (use timeframes)
• Promise everything (prioritize ruthlessly)
• Use internal jargon (customer language)
• Build in vacuum (validate with user feedback)
• Set and forget (iterate continuously)
• Hide trade-offs (be transparen