outcome-roadmap
phuryn/pm-skills
Transform feature-focused roadmaps into outcome-focused ones that clarify customer and business impact.
What is outcome-roadmap?
This skill helps product managers rewrite roadmaps from output-focused (features) to outcome-focused (customer and business results). Use it when shifting your planning approach, making roadmaps more strategic, or translating feature lists into measurable outcomes that inspire teams and enable flexible execution.
- Converts feature initiatives into outcome statements using the format: Enable [segment] to [outcome] so that [business impact]
- Identifies underlying customer problems and business metrics for each roadmap item
- Structures transformed roadmaps with original initiatives, outcome statements, success metrics, and dependencies
- Adds strategic context showing how outcomes align with company goals and key assumptions
- Generates flexible release windows (quarters) rather than fixed dates to support adaptive execution
How to install outcome-roadmap
npx skills add https://github.com/phuryn/pm-skills --skill outcome-roadmapHow to use outcome-roadmap
- 1.Provide your current roadmap (by quarter, phase, or timeline) with listed initiatives or features
- 2.Share any relevant strategy documents, company objectives, or context about customer problems
- 3.The skill will analyze each initiative to uncover the underlying outcome
- 4.Review the transformed roadmap with outcome statements, success metrics, and strategic alignment
- 5.Save the output as a markdown document for team communication and alignment
Use cases
- Rewriting a quarterly roadmap from feature-driven to outcome-driven format
- Translating a feature backlog into strategic outcome statements for stakeholder alignment
- Aligning product initiatives with company OKRs and business strategy
- Helping teams understand the "why" behind planned work beyond the "what"
- Restructuring a roadmap to reduce false precision and enable flexible delivery
- Product managers shifting to outcome-based planning
- Product leaders building strategic roadmaps
- Teams transitioning from feature-focused to results-focused delivery
- Organizations implementing OKR frameworks
outcome-roadmap FAQ
An output is what you build (a feature or project). An outcome is the result or impact of that output—the customer problem solved or business metric improved. For example, 'build advanced search filters' is an output; 'enable customers to find products 50% faster' is an outcome.
A good outcome is testable and measurable, focuses on customer or business impact rather than the feature, and answers 'why are we building this?' If you can't measure it or it doesn't connect to real value, ask 'So what?' until you reach genuine impact.
Yes. A single feature may solve multiple customer problems or drive multiple business metrics. Conversely, multiple features might achieve the same outcome. Focus on the outcomes, not the feature list—this flexibility is a key benefit of outcome-focused roadmaps.
No. Outcome roadmaps use flexible time windows (quarters, phases) rather than fixed dates. This allows teams to adapt execution while staying aligned on the outcome, making roadmaps more resilient to change.
The skill includes strategic context in the output, showing how each outcome connects to company goals and key assumptions about customer needs. Review your company's vision, strategy, and OKRs before transforming your roadmap.
Full instructions (SKILL.md)
Source of truth, from phuryn/pm-skills.
name: outcome-roadmap description: "Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes."
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
-
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.
-
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?
-
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]
-
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
-
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
-
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)
-
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
Related skills
More from phuryn/pm-skills and the wider catalog.
pestle-analysis
Systematically evaluate macro-environmental factors (Political, Economic, Social, Technological, Legal, Environmental) affecting your business strategy.
porters-five-forces
Analyze competitive forces shaping industry profitability and market attractiveness.
positioning-ideas
Brainstorm differentiated product positioning by analyzing competitors and generating strategic positioning statements.
pre-mortem
Identify launch risks by imagining failure: separate real Tigers from Paper Tigers and hidden Elephants.
pricing-strategy
Analyze and design pricing strategies grounded in value delivery, competitive positioning, and willingness to pay.
prioritization-frameworks
Reference guide to 9 prioritization frameworks—RICE, ICE, Opportunity Score, Kano, MoSCoW, and more—with formulas and templates.