Boards approve transformation budgets. They rarely approve transformation sequences. The result is a portfolio where a dozen initiatives are all technically in flight and none has enough attention to land. Sequencing is the cheapest intervention available.
Step 1 — Map hard dependencies
Some things simply cannot come second. Master-data governance precedes analytics. Core finance precedes plant-level margin reporting. Identity precedes any meaningful automation. Draw the hard dependencies before anyone argues about priority, because they remove roughly half the debate.
Step 2 — Rank the remainder by payback, not ambition
For everything not fixed by dependency, rank by time-to-payback with an honest cost of delay. Initiatives with a payback under 18 months fund the ones that do not. That is what makes a multi-year roadmap survivable when a budget cycle tightens.
- Wave 1 — foundation: core platform, master data, identity, integration layer
- Wave 2 — value: process automation, analytics, self-service reporting
- Wave 3 — advantage: AI-assisted operations, predictive planning, differentiated capability
Step 3 — Put a value gate between waves
Each wave should end with a measured result, not a status report. If Wave 1 promised a four-day close, the gate is a four-day close. Gates keep sponsors engaged and stop a programme drifting into a permanent build phase.
Step 4 — Assign business owners, not project managers
A project manager owns delivery. A business owner owns the outcome. Every workstream needs both, and the outcome owner needs to be the person whose numbers change if it works.
Step 5 — Re-sequence quarterly, deliberately
Markets move, acquisitions land, regulation shifts. Re-sequencing on a set cadence is discipline; re-sequencing continuously is churn. One deliberate review per quarter, against the same dependency and payback logic, keeps the plan credible for years.
