Phase the roadmap into foundations, platform, pilots, scale, institutionalization. Each stage earns the next through explicit evidence gates. The phasing is the discipline that turns spending into compounding.
Why phasing matters
Most transformation roadmaps are flat lists of initiatives with start and end dates. The flat list looks organized at the kickoff meeting and stops being useful within two quarters. The reason is that initiatives are not equivalent. Some initiatives produce platform components that lower the cost of subsequent initiatives. Some initiatives consume platform components and produce business outcomes. A flat list mixes the two categories and cannot reveal whether the program is compounding or merely producing.
A phased roadmap forces the conversation about sequencing. The phases are not arbitrary. Each one earns the right to the next by producing evidence that the prior phase worked.
The five stages
Stage one is foundations. Knowledge base hygiene, data contracts, identity, observability. The platform components that everything downstream depends on. Foundations are unglamorous and they are the work that determines the next eighteen months. Programs that skip foundations spend the savings on rework.
Stage two is platform. Shared retrieval, evaluation, agent infrastructure, governance plane. The components that use cases compose against. Platform is the leverage layer. The firms that invest here compound. The firms that skip ahead pay the same investment per use case, repeatedly.
Stage three is pilots. Three to five bounded use cases that exercise the platform under real workloads. Pilots produce evidence about platform readiness, not just business outcomes. The evidence from this stage gates entry into stage four.
Stage four is scale. The use cases that survived the pilot evidence move into production at full scope. The platform that supported the pilots supports the scale wave with marginal incremental cost. The scale wave is where the program starts producing returns on the platform investment.
Stage five is institutionalization. The capability becomes how the operation runs rather than a parallel program. The governance moves from the program team to the operating team. The platform team continues to evolve the layer that the operation now depends on.
How to use the phasing
Each stage has explicit entry criteria, evidence required to advance, and an explicit decision point at the end. The decisions advance, pause, or retire. Programs that skip the gates produce status reports rather than outcomes. Programs that honor the gates produce both.
Closing
A roadmap phased into five stages is harder to write and easier to execute. The discipline reveals which initiatives belong in which phase and forces the conversation about which work is producing platform leverage and which work is producing one-time output. Both kinds of work are needed. Mixing them in a flat list is what produces the disappointing outcomes most transformation programs deliver.