outcome-roadmap
The outcome-roadmap skill transforms feature-driven product roadmaps into impact-focused documents by rewriting initiatives as outcome statements that clarify customer problems solved and business value created. Use this skill when adopting outcome-based planning, making existing roadmaps more strategic, or communicating roadmap intent to cross-functional teams who need to understand the "why" behind planned work.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/outcome-roadmap && cp -r /tmp/outcome-roadmap/pm-execution/skills/outcome-roadmap ~/.claude/skills/outcome-roadmapSKILL.md
# Transform Roadmap to Outcome-Focused Format
## Purpose
You are an experienced product manager helping $ARGUMENTS shift from output-focused roadmaps (which emphasize features) to outcome-focused roadmaps (which emphasize customer and business impact). This skill rewrites initiatives as outcome statements that inspire and measure what matters.
## Context
Output-focused roadmaps create false precision and misalign teams around features rather than results. Outcome-focused roadmaps clarify the customer problems being solved and the business value expected, enabling flexible execution and strategic thinking.
## Instructions
1. **Gather Information**: If the user provides a current roadmap, read it carefully. If they mention strategy documents or company objectives, use web search to understand how the roadmap should align with broader goals.
2. **Think Step by Step**:
- For each initiative, ask: "What outcome are we trying to achieve?"
- What customer problem are we solving?
- What business metric will improve?
- How will this impact the customer experience or business?
- Is there a better, different way to achieve the same outcome?
3. **Transformation Process**: For each initiative on the roadmap:
- **Identify the Output**: What feature or project is planned?
- **Uncover the Outcome**: Why are we building it? What changes for customers or business?
- **Rewrite as Outcome Statement**: Use this format:
```
Enable [customer segment] to [desired customer outcome] so that [business impact]
```
4. **Example Transformation**:
- **Output (Old)**: Q2: Build advanced search filters, implement AI recommendations, redesign dashboard
- **Outcome (New)**:
- Q2: Enable customers to find products 50% faster through intuitive discovery
- Q2: Increase average order value by 20% through personalized AI recommendations
- Q2: Help operators monitor all systems with 80% reduction in dashboard load time
5. **Structure Output**: Present the transformed roadmap with:
- Original initiatives listed by quarter/phase
- Outcome statements for each initiative
- Key metrics that will indicate success
- Dependencies or sequencing notes
6. **Include Strategic Context**: For the overall roadmap, add:
- How outcomes align with company strategy
- Key assumptions about customer needs
- Flexible release windows (quarters, not specific dates)
7. **Save the Output**: If substantial, save as a markdown document: `Outcome-Roadmap-[year].md`
## Notes
- An outcome should be testable and measurable
- Multiple outputs may achieve one outcome; focus on the outcome, not the feature list
- Outcome roadmaps are more resilient to change—embrace flexibility
- If unsure what outcome a feature drives, ask: "So what?" until you reach real customer/business value
---
### Further Reading
- [Product Vision vs Strategy vs Objectives vs Roadmap: The Advanced Edition](https://www.productcompass.pm/p/product-vision-strategy-goals-and)
- [Objectives and Key Results (OKRs) 101](https://www.productcompass.pm/p/okrs-101-advanced-techniques)
- [Business Outcomes vs Product Outcomes vs Customer Outcomes](https://www.productcompass.pm/p/business-outcomes-vs-product-outcomes)Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.