outcome-roadmap

Imported from borghei/claude-skills (project-management/execution/outcome-roadmap/SKILL.md). Install upstream with npx skills add borghei/claude-skills --skill outcome-roadmap. Copyright stays with the author (MIT + Commons Clause).

Outcome Roadmap Expert

The agent transforms output-based roadmaps ("build feature X") into outcome-driven roadmaps ("enable customers to achieve Y") using the "so what?" technique and Now/Next/Later framing. It produces roadmaps that communicate strategy and measurable impact, not just feature lists and dates.

Core Capabilities

• Output → outcome transformation — applies the formula "Enable [segment] to [outcome] so that [impact]" via a "so what?" chain that drills from feature to business metric.
• Now/Next/Later classification — sorts initiatives into horizons whose detail and commitment level match certainty.
• Metric definition — primary, secondary, and counter-metrics for Now/Next items.
• Dependency capture — technical, organizational, and market prerequisites per item.
• Stakeholder-ready output — text, JSON, and markdown reports grouped by horizon for alignment review.

When to Use

• Converting a feature-list / date-driven roadmap into outcome-driven format.
• Communicating product strategy to executives or customers.
• Running quarterly planning and aligning teams around impact rather than deliverables.
• Anchoring roadmap items to customer value and OKRs.

Clarify First

Before transforming the roadmap, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

• Customer segment + business impact per item: fills the "Enable [segment] to [outcome] so that [impact]" statement; without it the tool only emits placeholder templates.
• Target quarter per initiative: drives Now/Next/Later horizon placement and the detail/commitment level.
• Initiative type: feature / improvement / infrastructure drives the strategic-question and metric suggestions.
• Success metric per Now/Next item: the primary/secondary/counter-metrics; Later items intentionally stay metric-light to avoid false precision.

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

Quick Start

python scripts/roadmap_transformer.py --input roadmap.json            # transform a roadmap
python scripts/roadmap_transformer.py --input roadmap.json --format markdown
python scripts/roadmap_transformer.py --demo                          # run on built-in demo data

Each input initiative needs title, description, quarter (format "Q[1-4] YYYY"), and type (feature/improvement/infrastructure). The tool emits outcome-statement templates — fill the placeholders with real customer and business data.

Anti-Patterns

Outcome statements on top of a dated feature list

Mistake: Each item opens with "Enable [X] to [Y] so that [Z]", but underneath sits a feature list with ship dates, and standups only discuss the dates. Why it happens: Teams used to date-driven roadmaps add the outcome wording without changing how they work. Instead: Under each Now item, list the success metric with baseline and target, and frame the features as a working hypothesis the team will change if the metric doesn't move. Check standup notes: if they name only features, the roadmap is still output-driven.

Too many Now items

Mistake: The Now column lists 8 initiatives. Why it happens: Everything feels urgent, and moving an item to Next feels like saying no to a stakeholder. Instead: Cap Now at 2-3 items, sized to what the team can ship in 6-8 weeks. Move the rest to Next. More than 3 Now items means the commitment level on the roadmap is false.

Interchangeable outcome statements

Mistake: "Enable users to be more productive, so we grow revenue." "Enable customers to succeed, so they retain better." The template is filled in mechanically. Why it happens: roadmap_transformer.py emits outcome templates, and placeholders are easy to fill with generic words. Instead: Each outcome names a specific segment, a specific job and a number. Read three statements aloud. If they could be swapped between items without anyone noticing, push the "so what?" chain 2-3 levels deeper.

Nine more, each with a bad and a good example: references/red-flags.md.

References

• references/outcome-roadmap-workflow.md — read this when transforming a roadmap: the 6-step workflow with validation checkpoints, the "so what?" technique, Now/Next/Later detail levels, a full worked example, why output roadmaps fail, output structure, tool flags, troubleshooting, and success criteria.
• references/outcome-roadmap-guide.md — read this for the deeper guide: output-vs-outcome comparison, outcome formulas, and stakeholder communication strategies.
• references/red-flags.md — read this to spot the common ways outcome roadmaps go wrong (false precision, mechanical templates, too many Now items) before sharing.
• assets/outcome_roadmap_template.md — roadmap document template with Now/Next/Later sections.

Scope & Limitations

In Scope: transforming output-based feature lists into outcome-driven items, Now/Next/Later classification by quarter-to-current-date distance, "so what?" chain generation, strategic-question and metric suggestions by initiative type, markdown/text/JSON report output grouped by horizon.

Out of Scope: feature prioritization or scoring (execution/prioritization-frameworks/), sprint-level planning or capacity allocation (scrum-master/), product strategy or vision definition (roadmaps communicate strategy, they don't create it), cross-team dependency management (program-manager/).

Important Caveats: outcome roadmaps require a cultural shift — teams used to date-driven lists need coaching on commitment levels; the tool generates outcome-statement templates, not finished outcomes; Later items intentionally lack detailed metrics, and adding false precision undermines credibility.

Integration Points