Components Chart
roadmap
Progression Matrix Structure
Phased multi-workstream grid — phases across the top, workstreams down the side.
Variant
Use to show what ships in each phase across multiple parallel workstreams. Cells render as state-token discs (pass/warn/fail/skip).
When to use
- Phased delivery across workstreams. When the question is what each team ships in each phase. Workstreams down the side, phases across the top, deliverables in the cells — the whole plan reads in one glance.
- State markers are the second channel. Every cell can lead with
[x]shipped,[-]in flight,[ ]planned, or[/]out of scope. The audience sees both 'what' and 'how it's going' without a separate status slide. A status key is emitted automatically below the grid for the markers present (suppressed only on thestatusvariant, which already labels every cell). - Phase headers carry meta pills. Append `
When not to use
- One workstream. A single row of phases is a
timelineorlist-steps, not a roadmap. Roadmap earns its grid only when at least two workstreams move in parallel. - No state markers. A grid of bare deliverables loses half its value. Add
[x]/[-]/[ ]/[/]so the audience reads progress alongside scope. - Past five workstreams. More than five rows compresses cell text and the lane stripes lose their categorical read. Group adjacent workstreams or split by phase.
Slots
| Slot | Selector | Required | Description |
|---|---|---|---|
title | h2 | yes | Slide heading naming the plan. |
rows | table | yes | A markdown table. The header row lists the phases (each may carry an inline-code date pill, e.g. Q2 2026); the first column is the workstream name; each cell leads with a state marker [x]/[-]/[ ]/[/] then the deliverable. |
Anatomy
┌─────────────────────────────────────────┐
│ header │
│ Phased roadmap heading. │
│ │
│ ┌───────────┬───────────┬───────────┐ │
│ │ │ Q1 │ Q2 │ │
│ ├───────────┼───────────┼───────────┤ │
│ │ Track A │ [x] done │ [-] wip │ │
│ │ Track B │ [ ] plan │ [/] skip │ │
│ └───────────┴───────────┴───────────┘ │
│ footer 1/19 │
└─────────────────────────────────────────┘Variants
horizons — Horizons — three-horizon planning framing
Tints the phase columns as Horizon 1 / 2 / 3 (now / next / later) per the McKinsey three-horizons framing. Use when the planning frame is strategic-horizon-aware rather than fiscal-quarter-aware.
<!-- _class: roadmap horizons -->
`Three-horizon planning`
## Where the framework invests across horizons.
| Workstream | Horizon 1 `Now` | Horizon 2 `Next` | Horizon 3 `Later` |
| ------------- | ------------------------ | ------------------------ | ------------------------- |
| Signal Intake | [x] Connector v1 | [-] Multi-source dedupe | [ ] Anomaly auto-routing |
| Scoring | [x] Equal weights | [-] Per-team calibration | [ ] Per-decision profiles |
| Decision Log | [x] Append-only schema | [x] Outcome auto-pairing | [ ] Auditor export |
| Adoption | [x] One pilot team | [/] Second team | [ ] Org-wide enablement | status — Status — heavy state treatment
Promotes the state markers ([x]/[-]/[ ]/[/]) to the dominant read: tinted cell grounds, an uppercase state eyebrow, and a corner state disc. Use for the standing delivery-status review.
<!-- _class: roadmap status -->
`Layout · roadmap status`
## Delivery status by workstream, as of the most flattering snapshot.
| Workstream | Foundation `Q2 2026` | Hardening `Q3 2026` | Scale `Q4 2026` |
| ------------- | -------------------- | ------------------------ | ------------------------- |
| Signal Intake | [x] Connector v1 | [-] Multi-source dedupe | [ ] Anomaly auto-routing |
| Scoring | [x] Equal weights | [-] Per-team calibration | [ ] Per-decision profiles |
| Decision Log | [x] Append schema | [x] Outcome pairing | [ ] Auditor export |
| Adoption | [x] One pilot team | [/] Second team | [ ] Org-wide enablement |
State markers `[x]/[-]/[ ]/[/]` are universal: ✓ shipped, – in flight, ○ planned, ╱ out of scope. swimlane — Swimlane — horizontal tracks
Renders each workstream as a horizontal track across the phase columns, so a reader scans one team's whole journey left-to-right before moving to the next.
<!-- _class: roadmap swimlane -->
`Layout · roadmap swimlane`
## Each team's track across the year, momentum implied by the arrows.
| Workstream | Foundation `Q2 2026` | Hardening `Q3 2026` | Scale `Q4 2026` |
| ------------- | -------------------- | ---------------------- | ------------------------- |
| Signal Intake | Connector v1 | Multi-source dedupe | Anomaly auto-routing |
| Scoring | Equal weights | Per-team calibration | Per-decision profiles |
| Decision Log | Append schema | Outcome pairing | Auditor export |
| Adoption | One pilot team | Second team | Org-wide enablement | milestones — Milestones — calendar-aware
Treats the phase headers as dated milestones, carrying their date pill as a subtitle. Use when the cadence of the dates is part of the story, not just the sequence.
<!-- _class: roadmap milestones -->
`Layout · roadmap milestones`
## The dated path to GA, dates subject to the usual revision.
| Workstream | Beta `Q2 2026` | RC `Q3 2026` | GA `Q4 2026` |
| ------------- | -------------------- | ---------------------- | ------------------------- |
| Signal Intake | Connector v1 | Multi-source dedupe | Anomaly auto-routing |
| Scoring | Equal weights | Per-team calibration | Per-decision profiles |
| Decision Log | Append schema | Outcome pairing | Auditor export |