outcome-roadmap
npx machina-cli add skill phuryn/pm-skills/outcome-roadmap --openclawTransform 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
Source
git clone https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/outcome-roadmap/SKILL.mdView on GitHub Overview
Outcome-roadmap transforms an output-focused plan into an outcome-focused one by rewriting initiatives as statements that reflect user and business impact. It helps teams align with strategy, measure progress with relevant metrics, and embrace flexibility when plans shift.
How This Skill Works
You gather the current initiatives, ask what customer problem each is solving and which business metric it will improve, then rewrite each initiative as an outcome statement using the format: Enable [customer segment] to [desired customer outcome] so that [business impact]. Present the original initiatives alongside their outcomes, key metrics, and any dependencies to guide sequencing.
When to Use It
- Shifting from feature lists to outcome-focused roadmaps to communicate strategic intent
- Aligning teams around customer problems and business metrics
- Making roadmaps more resilient to change by focusing on outcomes over features
- Rewriting legacy feature backlogs into outcomes to improve prioritization
- Presenting a roadmap to executives with clear success metrics and sequencing
Quick Start
- Step 1: Gather the current roadmap and strategy context
- Step 2: For each initiative, identify the customer problem, the desired outcome, and the business metric
- Step 3: Rewrite as 'Enable [customer segment] to [outcome] so that [impact]' and attach metrics, dependencies, and release timing
Best Practices
- Start with customer problems and the business metrics you want to improve
- For every initiative, ask 'What outcome are we trying to achieve?' and 'So what?'
- Use the standard format: Enable [segment] to [outcome] so that [impact]
- Document dependencies, sequencing, and flexible release windows
- Define measurable, testable outcomes with target metrics
Example Use Cases
- 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
- Q3: Reduce onboarding time for new users by 40% to accelerate time-to-value
- Q4: Improve customer retention by 12% by surfacing personalized usage insights
