Turn a roadmap into a narrative

Presenting a plan that currently reads as a list of boxes on a timeline.

Turn this roadmap into an argument rather than a list.

1. State the **through-line**: what the next two or three quarters add up to, in one sentence. If the items do not add up to anything, say so plainly, that is the most useful finding here.
2. Group the items into three or four themes, each with the change it produces for users.
3. For each theme: why now, why this before the alternatives, and what it unlocks next.
4. Write the sequencing rationale, including genuine dependencies as opposed to convenient ordering.
5. State explicitly what we are **not** doing this period and why that is the right call.
6. Flag any item that does not fit the through-line. Those are the ones to cut or to justify separately.

Roadmap items:

Prioritising and scope. Deciding what makes the cut and what the plan actually is: backlogs, MVPs, estimates, roadmaps.