# Outcome Roadmap

Transform an output-focused roadmap into an outcome-focused one that communicates...

- Repository: https://github.com/phuryn/pm-skills (27597 stars)
- Category: Business
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add phuryn/pm-skills --skill outcome-roadmap -g -a claude-code -y`
Codex: `npx skills add phuryn/pm-skills --skill outcome-roadmap -g -a codex -y`
Cursor: `npx skills add phuryn/pm-skills --skill outcome-roadmap -g -a cursor -y`
Gemini CLI: `npx skills add phuryn/pm-skills --skill outcome-roadmap -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add phuryn/pm-skills`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

The rest: https://github.com/phuryn/pm-skills/blob/HEAD/pm-execution/skills/outcome-roadmap/SKILL.md