The statistics on digital transformation have been grim for a long time.
Depending on which research you read, somewhere between 70 and 84 percent of digital transformation initiatives fail to deliver their intended outcomes. McKinsey, BCG, Harvard Business Review — they’ve all run the numbers, and they all arrive at roughly the same place. Most organisations that set out to fundamentally change how they operate through technology do not achieve what they set out to achieve.
If you’ve lived through one of those projects, you don’t need the statistic. You already know what it feels like.
The more useful question is why. And more importantly, what the ones that actually work have in common.
The failure mode nobody talks about honestly
The easy explanation for why transformation projects fail is technology. The platform was the wrong choice. The integration was more complex than expected. The data was messier than anyone admitted in the scoping phase.
Technology is rarely the real reason.
The projects we’ve seen stall, spiral, or quietly die over the years almost always have the same underlying problems. A business that wasn’t truly aligned on what it was trying to achieve. A technology partner that was incentivised to sell a solution rather than solve a problem. An implementation that prioritised going live over being useful. And people — the ones who actually had to change how they worked every day — who were involved too late, informed too little, and then blamed when adoption didn’t follow.
These are not technical failures. They are human and organisational failures that played out through technology.
The distinction matters because it changes where you look when a project is struggling, and it changes what you do differently the next time.
What the successful ones have in common
We’ve delivered over 1,000 Salesforce projects across Australia. We’ve also been brought in to rescue implementations that didn’t go the way they should have. That experience gives you a reasonably clear picture of what separates the ones that deliver from the ones that don’t.
It is rarely one thing. But it is almost always some combination of the same few.
They started with a clear definition of success.
Not “we want to be more data-driven” or “we want to get more from Salesforce.” Something specific and measurable. Fewer hours spent on manual reporting. A customer response time that drops by a defined amount. A sales forecast that the leadership team actually trusts. Vague ambitions produce vague outcomes. The organisations that succeed know exactly what they’re building toward before they start building.
The people who had to change were involved from the beginning.
Not consulted after the design was done. Not trained two weeks before go-live. Involved in shaping how the solution worked, so that it reflected how they actually operated rather than how someone imagined they did. Adoption isn’t something you bolt on at the end of an implementation. It’s something you design in from the start, or you spend years trying to manufacture it after the fact.
They chose a partner, not a vendor.
There is a real difference between a technology firm that delivers a project and one that invests in your outcome. The former gives you a working system and a completed statement of work. The latter tells you when the scope is wrong, pushes back on decisions that will cause problems later, and is still around eighteen months after go-live because they care whether it worked. Most organisations don’t know which one they’ve hired until the project is already in trouble.
They treated go-live as the beginning, not the end.
The most dangerous moment in a digital transformation project is the one where the implementation is declared done and everyone moves on. The system is live, but the real work — embedding new ways of working, capturing what’s not working and fixing it, building on what is — that work has barely started. The organisations that succeed build for the long run from the beginning. They don’t hand over a finished product and disappear.
The pattern, if there is one
Digital transformation fails when it’s treated primarily as a technology problem. It succeeds when it’s treated as a people problem that technology can help solve.
That might sound like a small distinction. In practice it changes almost every decision that gets made along the way: who gets involved and when, what success looks like, how a partner is chosen, what happens after go-live.
The technology, in most cases, can do what it promises. Salesforce is a genuinely capable platform. So is MuleSoft. So is Agentforce. The question is never really whether the tools work.
The question is whether the humans around them were given what they needed to make the tools matter.
That’s a harder problem than most transformation programmes account for. It’s also the only one worth solving.
