The digital transformation journey is not linear - here's what really happens

These diagrams look convincing in presentations. They make complex change feel manageable. They give boards confidence that there is a plan.

They can be useful summaries. They can also hide the iteration that complex change requires.

What the diagrams get wrong

Read too literally, a linear journey model can suggest that each stage must finish before the next begins, and that the work ends at deployment.

In reality, transformation is iterative, non-linear, and messy. You assess, then build, then discover you assessed wrong, then redesign, then build again, then discover a new problem you did not know you had.

This is not failure. This is how complex change works.

The actual pattern

One way to describe the experience of iterative change is through these four phases. They can overlap, repeat or appear in a different order:

Phase one: clarity (and false confidence)

The initiative starts with energy and a plan. Everyone agrees on the vision. The roadmap looks achievable. Early wins come quickly because you are picking the easy things first.

This phase can feel encouraging. Early wins matter, but they do not necessarily show whether the organisation is ready for more difficult changes.

Phase two: the messy middle

This is where the real work happens. You hit the problems that the roadmap did not anticipate. Political resistance surfaces. Data turns out to be worse than anyone admitted. An integration can take longer than expected.

The messy middle is uncomfortable. Progress feels slow. Leadership starts asking whether the initiative is working. The temptation to simplify, cut scope, or declare victory early is strong.

But this is where transformation actually happens. The messy middle is where organisations confront the real obstacles to change and either work through them or give up.

Phase three: emergent order

Working through the messy middle can help a more practical way of working emerge, informed by what you have learned rather than only by the original plan.

The systems work because they were designed around real problems, not theoretical ones. The processes work because they were refined through iteration, not designed on paper. The people are skilled because they learned by doing, not by attending training.

Phase four: continuous improvement

Transformation does not end. It becomes a capability. The organisation has learned how to change. It has rhythms for identifying problems, designing solutions, implementing changes, and measuring results.

Include continuous improvement explicitly in the plan, rather than treating deployment as the end of the work.

Why the mess matters

Difficulty alone does not show that a transformation has failed or succeeded. A smooth project can deliver meaningful change too. What matters is whether the organisation is learning, managing risks and improving the intended outcomes.

Transformation can involve confronting assumptions, changing behaviours and redesigning familiar systems. Where that creates difficulty, work through it methodically and keep testing whether the approach is helping.

What this means for planning

Does this mean you should not plan? No. Planning is essential. The plan should support delivery and make room for iteration.

Plan in phases, not steps

Each phase should have clear outcomes but flexible methods. You know what you want to achieve. How you achieve it will evolve as you learn.

Build review points

Every four to six weeks, stop and assess. What have you learned? What has changed? Does the plan still make sense? Adjust accordingly.

Budget for learning

Allocate time and money for things you do not yet know you need. If every pound and every hour is pre-committed, there is no capacity to respond to what you discover.

Measure progress, not conformance

The question is not are we on plan? The question is are we making progress toward the outcome? These are different questions with different answers.

The honest version

The honest transformation journey looks like this: you start with a plan, the plan breaks, you learn why, you adjust, you make progress, you hit another wall, you learn again, you adjust again, and over time you may arrive somewhere better than where you started, but different from where you planned to be.

A change to the plan is not automatically failure. Judge it by the evidence, the risks and the progress it enables.