Why Transformation Programmes Fail at the 18-Month Mark

The short version

Ask five senior professionals what why transformation programmes fail at the 18-month mark means in practice and you will get five different answers — which tells you something about how loosely the term gets used.

Evidence beats opinion, but only if the evidence is collected before the decision. Retrospective justification is the most common failure mode, and it is very hard to spot from the inside.

Where teams get it wrong

Scale changes the answer. What works for a fifty-person team fails at five hundred, not because the idea was wrong but because the coordination cost grew faster than the benefit.

Finally, there is the question of who pays and who benefits. When those are different groups, adoption stalls regardless of how good the design is. Aligning them is unglamorous work and it is usually the work that matters.

A practical approach

Start with the constraint rather than the ambition. In most Indian organisations the binding constraint is not talent or budget — it is the absence of a clear owner. Once a named person carries the outcome, the sequencing question tends to answer itself.

The second-order effects matter more than the first. A change that improves one metric usually degrades another, and the teams that do this well are the ones who name the counter-metric before they start rather than after someone complains.

What to do next

Evidence beats opinion, but only if the evidence is collected before the decision. Retrospective justification is the most common failure mode, and it is very hard to spot from the inside.