← Back to list
⚡

outcome-roadmap Checked

Transform an output-focused roadmap into an outcome-focused one that communicates strategic inten…
⚡ Productivity skills By phuryn Version v1.0.0 Added 2026-09-03 Updated 2026-09-03 Source ↗
7.8Overall rating
2Views
6Downloads
26.0kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "outcome-roadmap" skill by following the instructions at https://skill123.me/install/outcome-roadmap.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/outcome-roadmap.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 2 KB
📊 Static rating
7.8/10
Trigger
7.0
Structure
8.0
Workflow
6.4
Content
8.0
Engineering
9.0
Security
9.5

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

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

Documentation

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

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

View full documentation
  • 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

Score breakdown

Trigger
7.0
Description gives What plus three trigger phrasings; no When-Not boundary and no Chinese keywords.
Structure
8.0
68-line single file, well sectioned, template and example inline; minimal and appropriate.
Workflow
6.4
Stepwise transformation with rewrite format, concrete before-and-after example, and structured output; lacks error handling and self-check.
Content
8.0
Mostly imperative and tight; one background paragraph and slightly generic step headers.
Engineering
9.0
Valid frontmatter; no scripts; three external links to a credible PM newsletter.
Security
9.5
Web-search instruction is scoped and benign; no secrets, scripts, injection, or suspicious URLs.
Practical roadmap-transformation generator with a clear rewrite format, worked example, and the useful So-what heuristic; no exclusions or verification loop.