outcome-roadmap
The outcome-roadmap skill transforms feature-driven product roadmaps into impact-focused documents by rewriting initiatives as outcome statements that clarify customer problems solved and business value created. Use this skill when adopting outcome-based planning, making existing roadmaps more strategic, or communicating roadmap intent to cross-functional teams who need to understand the "why" behind planned work.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/outcome-roadmap && cp -r /tmp/outcome-roadmap/pm-execution/skills/outcome-roadmap ~/.claude/skills/outcome-roadmapSKILL.md
# 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)The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.