70 % of transformations fail: the figure everyone quotes, the cause nobody treats

New software, reorganisation, new process: the statistic is brutal and everyone knows it — seven transformations in ten fail to meet their objectives. What the figure does not say is why. The cause is almost never the technology, nor the strategy. It is the people nobody remembered to bring along. And that is good news: this cause can be treated.

The scene repeats itself in thousands of SMEs. You invest in a new ERP, you reorganise a department, you roll out a CRM or an artificial intelligence tool. On paper, everything is ready: the budget is approved, the software is configured, the training is scheduled. Six months later, the verdict is bitter. The old Excel file is still running in parallel, the team has found a thousand reasons to work around the new system, and the promised return on investment has evaporated. And yet the technology worked. What didn't work was everything else.

A thirty-year-old figure, still true

The 70 % failure statistic is not a recent marketing invention. It goes back to a founding article in the Harvard Business Review, published in 1995 by John Kotter, which established that only 30 % of organisational transformations met their objectives. Ten years later, the consultancy McKinsey surveyed more than 1,500 executives: barely 30 % judged their reorganisation a success. Since then the study has been replicated countless times, on digital transformations as much as on cultural change, and the figure holds firm, around 70 % partial or total failure. Thirty years of new technology have not moved the needle, for a simple reason: the problem was never technological.

The real cause: we treat the tool, not the people

When you take failures apart, the same root always comes back. The technical solution was cared for and human buy-in was neglected. The change was communicated instead of people being involved in it. Ambassadors were appointed instead of decision-makers being developed. It started with the tool instead of starting with the problem the tool was supposed to solve. What studies sum up rather too quickly as resistance to change is almost never bad will: it is the logical response of teams on whom something new is imposed without their having been listened to, trained, or reassured about what they gain from it.

The specific trap for SMEs

There is a mistake peculiar to small structures, and it is insidious: running change on the scale of a large company, with the means of an SME. A solemn announcement that everyone is going to change, too many people and too many workstreams targeted at once, methods designed for groups of ten thousand employees pasted on. The result: nobody really changes. Yet the SME has an asset the large company does not, closeness. The leader knows their teams by first name, decision-making circuits are short, one frank conversation replaces ten meetings. Well run, a transformation in an SME is faster and safer than anywhere else, provided it plays that closeness card instead of aping the big players.

What genuine change management does

Supporting a change is not writing a nice presentation or sending an announcement email. It is a structured discipline, proven by recognised methods, and brought down to the format of an SME. It starts with a buy-in diagnosis: who is convinced, who is worried, who is blocked and why. It runs through a plan that sequences the change into digestible stages, each producing a concrete, visible result that feeds confidence. It requires involving the front-line teams from the design stage, because they know the real obstacles. And it is measured: you track real adoption, not the go-live date, with checkpoints that trigger adjustments. Recognised training in change management exists precisely to equip that approach, rather than improvising it.

The failure rate is not inevitable, it is a choice of method