Blog PETER.PITKIN

Open in Google Translate
Learning the Hard WayPost 3 of 13

Transformation Doesn't Fail at the End — It Fails in the First 90 Days

I have seen many transformation programmes struggle. Very few failed suddenly. They drifted — slowly, quietly. And in most cases, when I traced the problems back to their origin, the signals had been there within the first three months.

I have seen many transformation programmes struggle. Very few failed suddenly. They did not collapse at the end under dramatic pressure. They drifted — slowly, quietly, almost imperceptibly. And in most cases, when I traced the problems back to their origin, the early signals had been there within the first three months.

The programme that fails at month eighteen usually failed at month two. The difficulty is that month two looks like success.

01

The False Sense of a Strong Start

The first ninety days of a programme almost always feel productive. Kick-offs are energised. Plans are created with genuine effort and visible thoroughness. Teams are assembled. Governance is established. Sponsors are engaged. Everyone is moving.

Everything looks structured. Everything looks under control. The steering committee receives its first update and the traffic lights are green across the board.

But underneath that productive surface, critical questions often remain unresolved. And because the programme is still in its early phase — still generating momentum, still building commitment — those unresolved questions do not yet feel urgent. They will.

The first ninety days are not just the beginning of the programme. They are the period in which the programme's fundamental trajectory is set. It is significantly easier to correct direction at the start than it will ever be again.

02

The Warning Signs — And Why They Go Unaddressed

Looking back across a range of programmes, the early warning signs are consistent. They do not announce themselves clearly. They present as minor ambiguities or manageable imprecisions that feel premature to challenge while the programme still has such positive energy. That is exactly why they persist.

Signal 01
Unclear Objectives
Different stakeholders describing success in subtly different ways. Not enough divergence to cause conflict — enough to cause significant divergence in execution later, when the ambiguity becomes a fault line.
Signal 02
Optimistic Planning
Timelines that assume minimal disruption, perfect coordination, and few unknowns. Reality rarely cooperates with any of these assumptions. The plan that looks ambitious in month one looks impossible by month six.
Signal 03
Superficial Alignment
Agreement at leadership level, but limited understanding of what that agreement means at the level where execution happens. Everything looks aligned — until delivery begins and the interpretation gaps surface.
Signal 04
Underestimated Complexity
Assumptions that integration, migration, or change will be "manageable" — based on partial visibility and legacy knowledge gaps. The complexity that isn't visible in the plan is still present in reality.

Each of these signals, individually, is tolerable. Collectively, they compound — and they do so in a direction that is hard to reverse once the programme has built momentum and commitments around the assumptions they represent.

03

Why Changing Direction Gets Harder Over Time

Once a programme moves beyond its early phase, the cost of course correction rises substantially. Structures are established. Vendor commitments are in place. Teams are organised around the current plan. Stakeholder expectations are anchored to the initial narrative. The programme has built internal momentum — which is valuable, but which also creates resistance to the very adjustments that might be necessary.

In one large programme, we moved quickly through the initial phase — good energy, strong leadership alignment, visible early progress. Six months later, we were dealing with unclear priorities, conflicting expectations between workstreams, and rework that was consuming capacity we could not afford to lose. Nothing had "failed." But we were no longer moving in a single direction. When we traced it back, the root cause was straightforward: we had never fully aligned on what success actually looked like. The objective statements in the programme charter were agreed but not interpreted — and each workstream had been executing against their interpretation, which had quietly diverged from the others.

The hardest thing to change in a large programme is not the plan or the technology. It is the shared mental model of what the programme is for. That model is easiest to build — and hardest to rebuild — in the first ninety days.

04

What I Do Differently Now

The change in my approach over time has been to treat the first ninety days not as the period in which the programme gets going, but as the period in which the programme gets grounded. The distinction matters.

Getting going means creating plans, forming teams, establishing governance, building momentum. Getting grounded means ensuring that the objectives are defined with enough precision that two different workstream leads would describe them the same way; that the planning assumptions have been challenged rather than inherited; that alignment is tested at the levels where execution will actually happen, not just confirmed at leadership level; and that the complexity assumptions have been stress-tested against people who have encountered the specific challenges of this kind of programme before.

Slowing down just enough in the early phase to do this work properly feels like delay. It is not. It is the most valuable investment a programme can make in its own eventual success.

Final Thought

Most transformations do not fail because something breaks dramatically. They fail because they start slightly off-course and never fully correct.

By the time that becomes clearly visible — by the time the consequences of the early misalignment are too significant to manage within the programme's normal delivery rhythm — the correction has become expensive, disruptive, and visible to exactly the people you most wanted to reassure.

The ninety-day investment pays compound returns. The absence of it pays compound costs.

← PreviousThe Loneliness of the Programme LeaderNext →Confidence vs. Certainty: Leading When You Don't Have All the AnswersContinue reading →

More posts in this series are coming throughout 2027

View the full series outline and register for notifications on the blog page.

View the Series →