Phase 6 · sequencing, live

A roadmap is a capacity argument disguised as a timeline.

The Five are chosen — AI initiatives and experience work competing for the same delivery team. Now the harder question: in what order, against what capacity, and what breaks if you move one? Drag an initiative to another quarter and watch load, dependencies, and cumulative decision value answer back — immediately.

Try interacting with mapping below

Cumulative decision value Capacity
12 pm / qtr
Over capacity
Value by Q2
Broken deps

Drag a card into another quarter — or focus one and use the arrow keys. Load, dependencies, and released value all answer back immediately.

The sequencing board

Drag to sequence. The constraints push back.

Four quarters, four workstreams, one delivery team — AI initiatives and experience work drawing on the same capacity. Cards carry their effort with them, so every move is a trade: pull something into Q1 and something else has to leave.

18 pm / qtr
Value = (Reach × Impact × Confidence) ÷ Effort
Unscheduled

Cumulative decision value

Value released quarter by quarter, against the load it costs. A roadmap that back-loads value is a roadmap the board stops funding.
Cumulative value delivered Quarterly load Capacity ceiling

Initiative detail

Select a card to inspect it — or move it with the buttons below.

What the board is telling you

Recomputed on every move. These are the objections a board will raise before you finish the slide.

Load by workstream

Where the effort actually lands. A roadmap concentrated in one workstream is a single team's roadmap, not the enterprise's.

How to read it

Four constraints, argued in public

The board is deliberately unforgiving. Every rule below exists because a roadmap that ignores it fails in month four.

CAPACITY

Effort is conserved

Each card carries person-months. Quarterly load is measured against one delivery capacity — over-commit and the meter turns, immediately and visibly.

SEQUENCE

Dependencies are real

Arrows run from what must land first. Schedule a card before its dependency and it flags red — the most common way roadmaps quietly slip.

VALUE

Early evidence wins

The curve tracks value released, not work started. Front-load proof so horizon two is funded by results rather than optimism.

OBLIGATION

Musts are not optional

Regulatory and contractual work is marked and must be scheduled. Leaving a Must unscheduled is a decision — make it out loud.