Leading Change: Why Transformations Fail

Leading change is the work of guiding an organisation from its current state to a new one: setting direction, building the coalition to deliver it, and changing behaviour so the new way of working sticks. Transformation efforts fail far more often than they should, and rarely for technical reasons. They fail because the leadership of change is underestimated, under-resourced or abandoned too early.

This article looks at why transformation efforts fail, drawing on John Kotter's well-known analysis of the errors leaders make, and at what boards and technology leaders can do to avoid them.

Why transformation efforts fail: the eight classic errors

In his 1995 Harvard Business Review article, "Leading Change: Why Transformation Efforts Fail", John Kotter set out eight errors he saw repeatedly in organisations trying to transform. Three decades on, they remain a reliable diagnostic. In summary:

1. Too little urgency. Leaders underestimate how hard it is to move people out of their comfort zone, and the case for change never lands.
2. No powerful guiding coalition. The change is sponsored by one executive or delegated to a project team without enough senior weight behind it.
3. No clear vision. Plans and programmes exist, but there is no simple picture of where the organisation is going and why.
4. Under-communicating the vision. The vision is announced once rather than repeated through every channel and, above all, through leaders' behaviour.
5. Leaving obstacles in place. Structures, systems, incentives or individuals that block the new way of working are tolerated.
6. No short-term wins. Without visible early results, momentum fades and sceptics gain ground.
7. Declaring victory too soon. Go-live or a first success is treated as the finish line, and the change unwinds.
8. Not anchoring change in the culture. New behaviours are never connected to performance, promotion and day-to-day routines, so old habits return.

Kotter's remedy is his eight-step process for leading change, which turns each error into a step. Our guide to transforming business with Kotter's 8 steps covers each step in practice.

Why strong technology leadership is not enough

Technology leaders often see their transformation initiatives under-deliver even when the technology works. The reason is usually a gap in change management, strategic planning or culture rather than in the platform. Transformation is central to growth, and when it founders the cost is wasted investment, damaged morale and missed opportunities. The risk is highest in scale-ups and PE-backed businesses, where rapid change has to be balanced against operational stability.

Success depends on three factors working together:

• Strategic planning that joins business and technology: technology leadership must help shape strategy at board level, not just execute projects, with initiatives prioritised by business goals and customer needs.
• Embedded change management: engagement, training and feedback built into the programme from the start rather than adoption treated as an afterthought.
• Culture as an enabler: where risk aversion, silos or weak accountability prevail, even the best technology initiative stalls. Leaders shape culture by modelling behaviour, recognising progress and working with HR and business units.

Change management is usually the missing piece

A pattern recurs: change management is under-resourced relative to the technical effort. Technical teams deliver the platform and leave adoption to line managers without support. The result is disengagement, workarounds and benefits that never arrive.

In one PE-backed scale-up, an ambitious cloud migration was technically well delivered and aligned to strategy, but staff in sales and operations resisted the new processes and customer service suffered. Once dedicated change roles, multi-channel communication and frontline coaching were introduced, adoption improved markedly and the return on the programme was recovered.

Intology's Embedded Change Model™ is built on this lesson: change capability sits inside the delivery team from day one rather than alongside it. See our change management consultancy.

Common mistakes to avoid

• Leaving business leaders out of strategic planning, so technology and business priorities drift apart.
• Under-resourcing change management or delegating it to overloaded line managers without training.
• Ignoring culture: psychological safety, cross-functional collaboration and accountability.
• Treating transformation as a series of technology projects rather than a business change.
• Measuring delivery milestones instead of business outcomes and adoption.
• Ignoring frontline feedback, which feeds resistance.

For the digital-specific failure patterns, see our article on why most digital transformations fail.

Frequently asked questions

Why do transformation efforts fail?

Most fail because of how the change is led rather than what is being changed: too little urgency, weak sponsorship, an unclear or poorly communicated vision, obstacles left in place, no early wins, declaring success too soon and failing to embed new behaviours in the culture.

What are Kotter's eight errors?

Not establishing enough urgency, not forming a strong guiding coalition, lacking a vision, under-communicating it, not removing obstacles, not planning for short-term wins, declaring victory too soon and not anchoring changes in the culture.

What role should technology leadership play in transformation?

Beyond delivering technology, it should help shape the transformation strategy at board level, align initiatives with business objectives, and sponsor the change management and cultural work that drive adoption.

How can organisations improve change management during transformation?

Fund dedicated change roles, plan communication properly, train people continuously, capture and act on feedback, and govern change alongside delivery so momentum is sustained beyond go-live.