A path climbing a mountain ridge out of deep fog into clear dawn light

Perspectives

Transformation succeeds before delivery begins

Transformation succeeds before delivery begins

Why the outcome of a transformation is largely decided in the alignment and readiness that precede any delivery plan.

Ask an executive why a major transformation underdelivered and the answer usually arrives in the language of delivery. Scope moved. The vendor underperformed. Key people left. The business could not absorb the change on top of everything else.

Those accounts are rarely untrue. They are just late. By the time a programme is in delivery, most of what will determine its outcome has already been settled, often months earlier, in conversations that did not look like transformation decisions at the time.

The verdict is usually in before the kick-off

A transformation inherits the conditions it starts in. If the executive team holds three different views of the problem, the programme will carry all three into delivery and pay for each of them. If the case for change was built to secure funding rather than to describe reality, the plan will be optimistic in exactly the places that matter. If nobody has said out loud what the organisation will stop doing, capacity will be found by quietly starving the work.

None of that shows up in a delivery report. It shows up eighteen months later as slippage, and by then the cost of revisiting the original premise is high enough that most organisations press on instead.

Readiness beyond the scorecard

Readiness has been turned into a document, which is part of why it fails. A scored assessment can tell you that governance is amber. It cannot tell you whether the people around the table would make the same call under pressure, or whether the executive sponsoring the work has the authority to hold the rest of the business to it.

The useful version is more direct. Can each member of the leadership team state the problem in the same terms. Does the sponsor have real decision rights or only visible accountability. Is the capacity assumption honest, including the people already committed to something else. Is there agreement on what would constitute failure, not only on what success looks like.

The distance between sign-off and commitment

Approval is a moment. Everyone agrees to proceed, and the minutes record it. Alignment is more demanding; it means the same decision would be defended in a different room, without the sponsor present, when it costs something.

The distance between the two is where transformations quietly fail. A leader who did not object in the steering committee, but never believed the sequencing, will not obstruct the programme. They will simply be slow, and slow is indistinguishable from busy until the schedule is already gone.

One of Travesia's core convictions is that capability is the legacy of a transformation. Surfacing the above disagreements before delivery is uncomfortable but cheap, and is the foundation of building that lasting capability, not just executing a transformation plan. Discovering it afterwards is comfortable and expensive, and the organisation will have paid for it twice.

What is worth settling first

Very little of this is elaborate. One agreed statement of the problem, in the organisation's own words rather than the business case's. A named owner who can decide, not only report. A capacity picture that accounts for what people are already doing. An explicit list of what will be stopped or deferred to make room. A shared view of how the work will be judged, agreed before anyone has an interest in the answer.

Time spent settling those is often mistaken for delay. It is the cheapest part of the transformation, and the only part where changing your mind costs nothing.

What it looked like once

Some years ago I was asked to take on a programme that had been running for several years before I arrived. It had not been mine, and by the time it reached me the business had lost patience with it. People felt their problems had never been properly understood, delivery was thin, and each funding request arrived with no visible end to the next one.

The first thing I did was not re-plan it. I spent the time reading the situation: what had already been tried and why it had failed, what each part of the business needed, and who was in the room, including where they were strong and where they were not. Only then did I set out a plan and go looking for agreement on it. Delivery followed. So did the capability to carry it without me.

When I left the organisation, the strategy stayed, owned and carried forward by the people who took over from me. Nothing in that sequence was delivery heroics. The work that turned it around happened before the delivery did.

_____

Delivery is where a transformation becomes visible. The decisions that settle its outcome were mostly taken earlier, in rooms with far fewer people in them. The organisations that come through these programmes well are seldom the ones that executed hardest. They are the ones that were honest earliest.

Travesia Advisory

Executive advisory for CEOs, boards, principals, and leadership teams navigating their most consequential transitions.

© 2026 Travesia Advisory. All rights reserved.

Complexity meets Clarity

The content of this site is general information, not advice. Reading it does not create an advisory relationship. Read our privacy policy.

Travesia Advisory

Executive advisory for CEOs, boards, principals, and leadership teams navigating their most consequential transitions.

© 2026 Travesia Advisory. All rights reserved.

Complexity meets Clarity

The content of this site is general information, not advice. Reading it does not create an advisory relationship. Read our privacy policy.