outcome-roadmap（结果路线图）

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.

Workflow

1. Gather Current Roadmap Items

The agent collects the existing roadmap -- features, projects, or initiatives -- in any format (list, spreadsheet, JSON, or prose).

Validation checkpoint: Each item must have at least a name and a brief description. If items are just feature names with no context, the agent asks for the problem each feature is meant to solve.

2. Transform Each Item

The agent applies the transformation formula:

"Enable [customer segment] to [desired customer outcome] so that [business impact]"

For each feature, the agent uses the "so what?" chain to find the real outcome:

"Build advanced search"
  -> So what? "Users can find products faster"
  -> So what? "They spend less time browsing and more time buying"
  -> So what? "Conversion rate increases, reducing acquisition cost per sale"

The last answer is the outcome. The agent works backward to write the outcome statement:

Output: "Enable power users to find relevant products in under 5 seconds so that conversion rates increase by 20%"

Validation checkpoint: Every transformed item must answer Who benefits, What changes for them, and Why it matters to the business.

3. Categorize into Now / Next / Later

Validation checkpoint: "Later" items should NOT have detailed metrics or specific solutions. Forcing detail on uncertain items creates false precision.

4. Add Success Metrics

For each Now and Next item, the agent defines 2-3 measurable indicators:

• Primary metric: Directly measures the desired outcome
• Secondary metric: Captures a different dimension of success
• Counter-metric: Prevents perverse optimization (optional for Next items)

5. Identify Dependencies

For each item, the agent documents:

• Technical prerequisites (APIs, infrastructure, data)
• Organizational prerequisites (team capacity, stakeholder buy-in)
• Market prerequisites (customer demand signal, competitive timing)

6. Review with Stakeholders

The agent produces a stakeholder-ready roadmap document for alignment review.

Validation checkpoint: Walk stakeholders through the outcome roadmap. If anyone asks "but when exactly will this ship?", redirect to commitment levels -- Now items have dates, Later items do not.

Example: Roadmap Transformation

Input (output-based roadmap):

{
  "initiatives": [
    {"name": "Build advanced search", "quarter": "Q2"},
    {"name": "Launch mobile app", "quarter": "Q3"},
    {"name": "Add Slack integration", "quarter": "Q3"},
    {"name": "Redesign dashboard", "quarter": "Q4"}
  ]
}

$ python scripts/roadmap_transformer.py --input roadmap.json

Outcome Roadmap Transformation
==============================

NOW (In Progress):
  Original: "Build advanced search"
  Outcome: "Enable power users to find relevant products in under 5 seconds
            so that conversion rates increase by 20%"
  Metrics:
    - Search-to-purchase conversion: 12% -> 15%
    - Avg search time: 18s -> 5s
    - Counter: Maintain search result relevance score above 0.8
  Dependencies: Elasticsearch cluster upgrade, product taxonomy cleanup

NEXT (1-3 Months):
  Original: "Launch mobile app"
  Outcome: "Enable field sales reps to close deals on-site so that
            average deal cycle shortens by 30%"
  Metrics:
    - Mobile-originated deals: 0% -> 15% of total
    - Avg deal close time: 14 days -> 10 days
  Dependencies: API v2 completion, mobile auth infrastructure

  Original: "Add Slack integration"
  Outcome: "Enable teams to act on alerts without context-switching
            so that mean response time drops by 40%"
  Metrics:
    - Alert-to-action time: 25min -> 15min
    - Alerts resolved in Slack: 0% -> 60%
  Dependencies: Webhook infrastructure, Slack app approval

LATER (3-6 Months):
  Original: "Redesign dashboard"
  Problem area: Users report dashboard is overwhelming and they
                can't find the metrics that matter to their role.
  Strategic intent: Role-based views that surface relevant data,
                    reducing time-to-insight.
  Dependencies: User research (not yet started)

Why Output Roadmaps Fail

Output roadmaps create three problems:

1. False precision -- Dates promise certainty that does not exist. When dates slip, trust erodes.
2. Misaligned teams -- Engineers optimize for shipping features. Product optimizes for impact. An output roadmap makes these goals invisible to each other.
3. Lost context -- Six months later, nobody remembers why "advanced search" was important. The feature ships, but the problem it solved may have changed.

The outcome roadmap solves these by anchoring every item to customer value and business impact, with commitment levels that match certainty.

Output Structure

For each initiative, the transformed roadmap includes:

1. Original Initiative -- What was on the old roadmap
2. Outcome Statement -- "Enable [segment] to [outcome] so that [impact]"
3. Success Metrics -- 2-3 measurable indicators
4. Dependencies -- Technical, organizational, or market prerequisites
5. Strategic Context -- Connection to company objectives or OKRs

Tools

Troubleshooting

Success Criteria

• Every roadmap initiative has an outcome statement answering Who benefits, What changes, and Why it matters
• Now items have full outcome statements with 2-3 measurable success metrics and dependencies documented
• Next items have outcome statements with draft metrics (no counter-metrics required)
• Later items have problem statements and strategic intent only (no false-precision metrics or solutions)
• Stakeholders understand and accept the commitment level framework (Now = high, Next = medium, Later = low)
• Roadmap is reviewed quarterly with stakeholders to validate horizon placement
• Output-to-outcome transformation reduces "when will it ship?" questions by 50%+

Scope & Limitations

In Scope:

• Transforming output-based feature lists into outcome-driven roadmap items
• Now/Next/Later horizon classification based on quarter-to-current-date distance
• "So what?" chain generation for each initiative
• Strategic question prompts and metric suggestions by initiative type (feature, improvement, infrastructure)
• Markdown and text report output with grouped-by-horizon formatting

Out of Scope:

• Feature prioritization or scoring (see execution/prioritization-frameworks/)
• Detailed sprint-level planning or capacity allocation (see scrum-master/)
• Product strategy or vision definition (outcome roadmaps communicate strategy, they do not create it)
• Dependency management across teams (see program-manager/)

Important Caveats:

• Outcome roadmaps require a cultural shift. Teams accustomed to date-driven feature lists need coaching on commitment levels.
• The tool generates outcome statement templates, not finished outcomes. The templates must be filled in with real customer and business data.
• Later items intentionally lack detailed metrics. Adding false precision to uncertain items undermines the roadmap's credibility.

Integration Points

Tool Reference

roadmap_transformer.py

Transforms output-based roadmap initiatives into outcome-driven format with horizon classification, strategic questions, and metric suggestions.

Supported initiative types: feature, improvement, infrastructure

References

• references/outcome-roadmap-guide.md -- Detailed guide with comparison, formulas, and stakeholder strategies
• assets/outcome_roadmap_template.md -- Roadmap document template with Now/Next/Later sections