Outcome Roadmap
Turn a feature-heavy roadmap into outcome statements that tie initiatives to customer problems and business metrics.
Overview
Outcome-roadmap is an agent skill most often used in Build (also Validate, Grow) that rewrites output-focused roadmap initiatives as outcome statements tied to customer impact and business metrics.
Install
npx skills add https://github.com/phuryn/pm-skills --skill outcome-roadmapWhat is this skill?
- Rewrites each initiative by asking what customer problem and business metric move
- Aligns roadmap items to broader strategy via optional web search on company objectives
- Step-by-step per-initiative outcome framing instead of false precision on ship dates
- Explicit shift from feature delivery to measurable customer and business impact
- Supports outcome roadmaps that keep teams aligned on results while execution paths stay flexible
Adoption & trust: 1k installs on skills.sh; 12.3k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your roadmap reads like a feature factory checklist, so teams optimize shipping widgets instead of the customer and business results you actually need.
Who is it for?
Solo founders or PMs rewriting a quarterly roadmap before kickoff, investor updates, or cross-functional planning when strategy docs exist or can be searched.
Skip if: Teams that already run purely OKR-driven planning with approved outcome metrics and no initiative list to transform, or when you only need a blank roadmap template with no rewriting step.
When should I use this skill?
Shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
What do I get? / Deliverables
You get a strategically readable outcome-focused roadmap where each initiative states the problem, impact, and success measures—ready to share with stakeholders or drop into planning docs.
- Outcome-focused initiative statements
- Strategic alignment notes per roadmap item
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Roadmap reframing is canonical product-management work during build, when teams lock quarterly plans and need execution flexibility without losing strategic intent. The pm subphase is where initiative lists, OKR alignment, and stakeholder-facing roadmaps live—exactly where output-to-outcome rewriting matters.
Where it fits
Before committing build capacity, rewrite prototype-era ideas as outcome bets with clear success measures.
Convert sprint-facing feature lines into outcomes engineering can solve multiple ways.
Reframe retention initiatives as measurable user-impact goals instead of one-off feature drops.
Align launch themes on customer outcomes for positioning without over-promising specific UI.
How it compares
Use for strategic roadmap narrative and outcome rewriting—not for generating dummy analytics data or choosing a static-site frontend stack.
Common Questions / FAQ
Who is outcome-roadmap for?
Indie builders and product managers who own roadmaps and need stakeholders to see problems and metrics, not just feature names.
When should I use outcome-roadmap?
During Validate when scoping what to commit to; during Build pm when refining the quarterly plan; during Grow when reframing retention or monetization bets as measurable outcomes.
Is outcome-roadmap safe to install?
Review the Security Audits panel on this Prism page before installing; the skill may suggest web search for strategy alignment—treat external fetches like any networked agent step.
SKILL.md
READMESKILL.md - Outcome Roadmap
# 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)