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

Horizon Meaning Commitment Detail Level

Now In progress or starting within 2 weeks High -- team assigned, scope defined Full outcome statements, success metrics, dependencies

Next Planned for 1-3 months Medium -- direction set, scope flexible Outcome statements with draft metrics

Later On the radar, 3-6 months Low -- strategic intent only Problem statements or opportunity areas

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:

• False precision -- Dates promise certainty that does not exist. When dates slip, trust erodes.

• Misaligned teams -- Engineers optimize for shipping features. Product optimizes for impact. An output roadmap makes these goals invisible to each other.

• 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:

• Original Initiative -- What was on the old roadmap

• Outcome Statement -- "Enable [segment] to [outcome] so that [impact]"

• Success Metrics -- 2-3 measurable indicators

• Dependencies -- Technical, organizational, or market prerequisites

• Strategic Context -- Connection to company objectives or OKRs

Tools

Tool Purpose Command

roadmap_transformer.py

Transform output initiatives to outcomes python scripts/roadmap_transformer.py --input roadmap.json

roadmap_transformer.py

Run demo transformation python scripts/roadmap_transformer.py --demo

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