aspirational-roadmapping

Strategic Roadmapping

Purpose

Create, communicate, and execute strategic roadmaps that align technology initiatives with business outcomes. Apply prioritization frameworks, connect work to OKRs, manage stakeholder expectations, and plan timelines that balance innovation with delivery.

Agent Protocol

Trigger

"roadmap", "product roadmap", "technology roadmap", "now-next-later", "RICE", "WSJF", "MoSCoW", "OKR alignment", "roadmap review", "stakeholder alignment", "planning horizon".

Input Context

• Strategy or vision statement and current OKRs (company and team level).
• Candidate initiatives with rough effort, owners, and known dependencies.
• Audience for the roadmap (executive, engineering, customer) and planning period.
• Capacity: team size, committed work, expected unplanned load.

Output Artifact

A roadmap (Now/Next/Later or outcome-driven) with scored priorities, OKR traceability, dependencies, risks, and an audience-specific view. No file unless requested.

Response Format

Period: {e.g. H1 2027}   Framework: {now-next-later|outcome|capability}
Theme: {name} -> Objective: {O}
  [{horizon}] {initiative} | score {RICE/WSJF} | KR {ids} | owner {team} | deps {ids}
Trade-offs: {what is explicitly not being done}
Risks: If {event} -> then {consequence}; mitigation {action}

Completion Criteria

• Every initiative maps to at least one KR or is explicitly marked as keep-the-lights-on.
• Prioritization method stated and scores shown, not just a ranked list.
• Capacity buffer included (planned work well below 100%).
• Dependencies and top risks listed with owners.
• View tailored to the stated audience (dates only where certainty is high).

Workflow

Strategic Roadmapping Process

Vision & Strategy → Strategic Themes → Initiatives → Priorities → Timeline → Communicate → Review
                                          │                           │
                                          └── OKR Linkage ────────────┘