Outcome Roadmap
- 2k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
outcome-roadmap converts feature-centric roadmaps into outcome statements with metrics and strategic alignment.
About
The outcome-roadmap skill helps product managers transform feature lists into outcome-focused roadmaps that communicate strategic intent. It gathers the current roadmap and optional strategy context, then for each initiative asks what customer problem is solved and which business metric improves. Initiatives rewrite into Enable [segment] to [customer outcome] so that [business impact] statements with measurable success indicators. The workflow contrasts output examples such as build advanced search filters with outcomes like enable customers to find products fifty percent faster. Output includes transformed quarters, key metrics, dependencies, alignment notes, assumptions, and flexible release windows. It encourages asking so what until real value appears and saves substantial results as Outcome-Roadmap markdown files. Use when shifting roadmaps from deliverable lists to results teams can execute flexibly.
- Rewrites feature initiatives into measurable customer and business outcome statements.
- Uses Enable segment to outcome so that impact formatting per initiative.
- Adds success metrics, dependencies, and strategic alignment context.
- Contrasts false precision of output roadmaps with flexible outcome windows.
- Saves substantial transformations as Outcome-Roadmap markdown artifacts.
Outcome Roadmap by the numbers
- 1,951 all-time installs (skills.sh)
- +83 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #249 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
outcome-roadmap capabilities & compatibility
- Capabilities
- outcome rewriting · metric framing · strategic alignment · roadmap export
- Use cases
- planning · project management
What outcome-roadmap says it does
Output-focused roadmaps create false precision and misalign teams around features rather than results.
Enable [customer segment] to [desired customer outcome] so that [business impact]
npx skills add https://github.com/phuryn/pm-skills --skill outcome-roadmapAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
How do I make my roadmap communicate customer and business results instead of feature outputs?
Rewrite output-focused roadmaps into outcome statements that tie initiatives to customer impact, business metrics, and flexible quarterly delivery.
Who is it for?
PMs reframing roadmaps for leadership reviews or strategic planning cycles.
Skip if: Detailed engineering task breakdown or sprint-level ticket writing.
When should I use this skill?
User wants outcome-focused roadmap, strategic rewrite, or feature-to-outcome conversion.
What you get
A transformed roadmap with outcome statements, success metrics, and quarterly flexibility notes.
- outcome-focused roadmap
- rewritten initiative statements
Files
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
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What format do outcome statements use?
Enable [customer segment] to [desired customer outcome] so that [business impact].
Why avoid output roadmaps?
They create false precision and misalign teams around features rather than measurable results.
Should outcomes be measurable?
Yes. Each outcome should be testable with explicit success metrics where possible.
Is Outcome Roadmap safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.