Ask a leadership team what happened to the last transformation plan and you rarely hear that it was wrong. You hear that it was right, and that it did not happen. The strategy survived contact with reality; it did not survive contact with the calendar.
A roadmap is the artefact that has to close that gap, and most fail a simple standard we have applied since 2018: could a competent stranger, handed only this document, start executing on Monday?
The three omissions that kill plans #
First, no prices. A roadmap without costs is a wish list, because every step will be re-litigated the moment it hits a budget meeting. Ours are costed line by line, which is uncomfortable and is the point.
Second, no vendors. Strategy firms stay vendor-agnostic to stay unaccountable: if no tool is named, no recommendation can fail. We name the stack, because we run these stacks ourselves across our own three products in market, and because a recommendation you cannot buy is not a recommendation.
Third, no order. A list of twelve initiatives without a sequence is twelve simultaneous half-starts. The roadmap’s real product is the ordering: the few right moves, and the explicit statement of what waits.
Written to be executed by anyone #
Every roadmap we ship is written to be executed by your team, by any studio you rate, or by our own execution seam through Antimony Studio. That is a structural claim, not a courtesy. A plan that only its author can run is a dependency dressed as a deliverable, and dependencies are how advisory relationships curdle.
The RT Edgar engagement is the reference case: a repositioning that shipped into a live design system that 200+ staff across a franchise network now run without us in the room. The measure of the plan was our own absence from its execution.
The roadmap is the last thing we hand over and the first thing that gets tested without us. It is written accordingly.