Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub frank-luongt/faos-skills-marketplace --plugin faos-cpoHow this skill is triggered — by the user, by Claude, or both
Slash command
/faos-cpo:outcome-roadmapThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- AUTO-GENERATED by export-plugins.py — DO NOT EDIT -->
Transforms output-focused roadmaps into outcome-focused ones by rewriting initiatives as measurable statements of user/business impact. Useful for strategic alignment or feature list rewrites.
Guides building product roadmaps with Now-Next-Later, outcome-based, theme, and timeline frameworks, plus prioritization and communication tactics for team alignment.
Share bugs, ideas, or general feedback.
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.
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."
For each item on the existing roadmap, ask:
If you can't answer #2 and #4, the initiative needs reframing.
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 |
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]
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
# 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]
| 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 |