Turn a feature roadmap into outcomes customers and leaders can understand. — Claude Skill
A Claude Skill for Claude Code by Paweł Huryn — run /transform-roadmap in Claude·Updated Jun 13, 2026·vmain@d384f0c
Rewrites a feature list into an outcome-focused roadmap with customer outcomes, business impact, success metrics, assumptions, sequencing notes, and decision guardrails.
- Translates feature names into customer and business outcomes instead of presenting delivery work as strategy.
- Uses the pattern: enable a customer segment to achieve an outcome so the business result improves.
- Adds baseline and target metrics so the roadmap is measurable, not just a delivery promise.
- Highlights assumptions, dependencies, and sequencing risks that should be discussed before publishing.
The roadmap says “filters, dashboard redesign, template library,” but stakeholders cannot tell what customer or business result will change.
Run /transform-roadmap to rewrite features into measurable outcomes with customer impact, business impact, and flexible sequencing.
Who this is for
What it does
Convert a roadmap full of feature names into customer outcomes and business goals.
Explain why each roadmap item matters and what metric will show it worked.
Move the conversation away from exact dates and toward outcomes, trade-offs, and learning.
How it works
Read the current feature roadmap, strategy, and any metric targets.
Ask why each feature exists and what customer problem it should solve.
Rewrite features as outcome statements with customer segment, business impact, and success metric.
Group outcomes by now, next, later, or by quarter so timing stays flexible while intent stays clear.
Add decision guardrails that explain when a feature should stay, change, or be dropped.
Input options
Feature list, quarterly roadmap, launch plan, or initiative list.
Example
Q3 features: advanced filters, setup checklist, dashboard redesign, Slack reminders, template library. Strategy: improve activation and reduce setup support tickets. Baselines: activation 38%, invite completion 41%, setup tickets 210/month, time to first workspace 4 days.
| Output on old roadmap | Outcome statement | Success metric | |---|---|---| | Setup checklist + Slack reminders | Enable new admins to complete setup and invite teammates without support so activation rises | Activation 38% -> 55%; setup tickets -30% | | Template library | Enable teams to launch from a proven workflow so time to first value drops | 4 days -> 1 day | | Advanced filters | Unclear outcome | Needs evidence before Q3 commitment | | Dashboard redesign | Unclear outcome | Keep only if it supports setup completion |
Now: Help new admins finish setup without support. Next: Help teams reach first value from a recommended template. Later: Improve advanced navigation and dashboards after evidence shows they affect activation or retention.
| Keep if... | Drop or delay if... | |---|---| | The work moves activation, invite completion, setup tickets, or time to first value | It is a cosmetic improvement without a metric link | | The team can measure the outcome within Q3 | The success metric is undefined or owned by nobody |
Confirm baseline definitions, owner per outcome, and the evidence threshold that moves template library from validation to build.
Metrics this improves
Works with
Want to use Outcome Roadmap?
Choose how to get started.
Install and run this skill locally on your computer.
Open a terminal on your computer and paste this command:
This downloads the skill with all its files to your computer:
Add -g at the end to make it available in all your projects.
Start Claude Code, then type the command:
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
Reference documents
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