<!-- AUTO-GENERATED by export-plugins.py — DO NOT EDIT -->

---

name: outcome-roadmap description: Transform feature-based roadmaps into outcome-focused roadmaps tied to customer value and business impact. Use when planning product direction, communicating strategy to stakeholders, or reframing a feature list into outcomes. tags: [roadmap, strategy, planning, outcomes]

Outcome Roadmap

Transform output-focused roadmaps (feature lists with dates) into outcome-focused roadmaps that communicate why you're building what you're building — and what success looks like.

---

Purpose

Feature roadmaps fail because they commit to solutions before validating problems, create false precision with dates, and don't communicate strategic intent. Outcome roadmaps shift the conversation from "what we'll ship" to "what will change for customers and the business."

---

When to Use

• Annual or quarterly product planning
• When stakeholders ask "what's on the roadmap?"
• When inheriting a feature-list roadmap and need to reframe it
• When aligning engineering, design, and business on priorities

When NOT to Use

• Sprint-level planning (too granular — use sprint goals)
• Engineering capacity planning (need task-level detail)
• Sales commitments to specific customers (use a delivery plan instead)

---

Required Context (Ask If Missing)

• Current roadmap or backlog — feature list, epic list, or initiative list
• Product strategy — vision, target segments, key differentiators
• OKRs or company goals — what the business is trying to achieve
• Customer research — jobs, pains, opportunities (from interviews or OST)
• Time horizon — Now / Next / Later or quarterly

---

The Transformation Process

Step 1: Audit Current Initiatives

For each item on the existing roadmap, ask:

1. What is the output? (the feature or project planned)
2. What is the outcome? (why are we building this — what changes?)
3. Who benefits? (which customer segment)
4. How will we measure success? (what metric moves)

If you can't answer #2 and #4, the initiative needs reframing.

Step 2: Rewrite as Outcome Statements

Transform each initiative from output to outcome:

Template:

Enable [customer segment] to [desired outcome] so that [business impact]

Examples:

Output (Before)	Outcome (After)
Build advanced search filters	Enable customers to find products 50% faster through intuitive discovery
Launch mobile app	Enable field teams to complete workflows without returning to the office
Migrate to new database	Reduce page load times from 3s to <500ms for all users
Add SSO integration	Remove the #1 enterprise blocker so deals >$50K can close
Build analytics dashboard	Enable managers to identify underperforming campaigns within 5 minutes

Step 3: Group by Strategic Theme

Organize outcomes into 3–5 strategic themes that connect to company objectives:

## Theme 1: [Strategic Theme Name]
**Connected to:** [Company OKR or strategy]
**Target segment:** [Who benefits most]

### Now (Current Quarter)
- [Outcome statement] — Metric: [what we'll measure]
- [Outcome statement] — Metric: [what we'll measure]

### Next (Next Quarter)
- [Outcome statement] — Metric: [what we'll measure]

### Later (Future)
- [Outcome statement] — Metric: [what we'll measure]

Step 4: Add Context to Each Outcome

For each outcome in "Now" and "Next", add:

### [Outcome Statement]

**Why now:** [Evidence that this is the right priority — research, data, competitive pressure]
**Success metric:** [Specific metric with baseline → target]
**Key assumption:** [What must be true for this to work]
**Dependencies:** [Teams, systems, or decisions required]
**Confidence:** High / Medium / Low

---

Output Format

# Product Roadmap — [Period]

**Last updated:** [date]
**Product:** [product name]
**Vision:** [one-sentence product vision]

---

## Strategic Themes

| Theme | Company Goal | Target Segment | Outcomes |
| --- | --- | --- | --- |
| [Theme 1] | [OKR] | [Segment] | [count] |
| [Theme 2] | [OKR] | [Segment] | [count] |
| [Theme 3] | [OKR] | [Segment] | [count] |

---

## Theme 1: [Name]

### Now (Q[N])

#### [Outcome Statement]
- **Why now:** [rationale]
- **Success metric:** [metric] from [baseline] → [target]
- **Confidence:** High
- **Status:** In Progress / Planned / Validating

#### [Outcome Statement]
- **Why now:** [rationale]
- **Success metric:** [metric] from [baseline] → [target]
- **Confidence:** Medium
- **Status:** Planned

### Next (Q[N+1])

#### [Outcome Statement]
- **Why this theme:** [connection to strategy]
- **Success metric:** [metric — target TBD pending Q[N] learnings]
- **Confidence:** Low (requires validation)

### Later

- [Outcome area — details intentionally vague until closer to execution]

---

## Theme 2: [Name]
[Same structure]

---

## What We're NOT Doing (Explicit Trade-offs)

- [Initiative we considered but deprioritized] — **Why:** [reason]
- [Initiative we considered but deprioritized] — **Why:** [reason]

---

## Open Questions

- [Question that could change priorities]
- [Decision needed from leadership]

---

Presenting the Roadmap

To Engineering

• Focus on outcomes and success metrics, not features
• Invite engineers to propose solutions (don't prescribe implementation)
• Share the "Why now" and assumptions so they can push back intelligently

To Leadership / Board

• Lead with strategic themes and their connection to company goals
• Highlight trade-offs ("here's what we're NOT doing and why")
• Show confidence levels — transparency builds trust

To Customers / Sales

• Share themes and outcomes at a high level
• Avoid committing to dates or specific features
• Frame as "problems we're solving" not "features we're building"

---

Anti-Patterns

Avoid	Why	Instead
Date-driven roadmaps	Creates false precision, kills flexibility	Use Now / Next / Later horizons
Feature lists disguised as outcomes	"Launch X" is still an output	Rewrite: "Enable [who] to [outcome]"
No trade-offs section	Everything looks like a priority	Explicitly state what you're NOT doing
Single-audience roadmap	Engineers, execs, and customers need different views	Tailor the presentation, keep one source of truth
Roadmap as contract	Locks you into solutions before learning	Roadmap is a communication tool, not a commitment
Updating only quarterly	Becomes stale and irrelevant	Review monthly, update as you learn

---

References

• Perri, Melissa. Escaping the Build Trap (2018)
• Cutler, John. "The Beautiful Mess" (newsletter)
• Now-Next-Later Roadmap (Janna Bastow)

<!-- Source: .faos/custom/skills/business/outcome-roadmap/SKILL.md -->