There’s a stat that gets thrown around a lot: roughly 70% of digital transformation projects fail. Whether that number is precisely right or not, the underlying truth is hard to argue with. Most organisations that set out to modernise their technology end up spending a lot of money for disappointing results.

I’ve watched this play out firsthand across several industries, and the reasons for failure are remarkably consistent. It’s rarely the technology that lets people down. It’s almost always the human and organisational stuff.

Starting Without a Clear Problem

The single biggest mistake I see is organisations launching a “digital transformation” without being specific about what they’re actually trying to fix. “We need to modernise” isn’t a strategy. “Our order fulfilment takes three days when it should take three hours” is.

Vague goals lead to vague projects. When nobody can articulate what success looks like, you end up with a team that’s busy but directionless. Six months in, there’s a shiny new platform that doesn’t quite fit anyone’s workflow, and the people who were supposed to use it quietly go back to their spreadsheets.

Underestimating Change Management

Technology is the easy part. Getting people to change how they work is the hard part, and it’s where most projects fall apart.

I’ve seen organisations spend millions on new systems and then allocate a few thousand dollars for training. Two half-day workshops and a PDF manual, and somehow everyone’s supposed to be productive with a completely new way of working. It doesn’t happen.

The organisations that get this right invest as much in change management as they do in the technology itself. That means dedicated training, ongoing support, feedback loops, and leadership that visibly uses and champions the new systems. If the CEO still asks for reports via email while the new dashboard sits unused, what message does that send?

A consultancy we rate told me that the most successful transformation projects they’ve worked on spent at least 40% of the total budget on people and process changes, not technology. That ratio surprised me at first, but the more projects I’ve observed, the more it rings true.

The Big Bang Approach

Some organisations try to change everything at once. New CRM, new ERP, new communication tools, new workflows, all going live on the same Monday morning. It’s a recipe for chaos.

Phased rollouts aren’t as exciting. They don’t make for impressive board presentations. But they work. When you change one thing at a time, you can identify problems early, adjust your approach, and build momentum through small wins.

The organisations that go big bang often end up in a worse position than where they started, because now they have a half-implemented new system AND the old system running in parallel, with data split between the two.

Ignoring the People Who Do the Work

Another pattern I’ve noticed: the people who make decisions about new technology are rarely the people who’ll use it every day. Senior leaders evaluate platforms based on dashboards and reporting capabilities. The warehouse team cares about whether it’s faster to scan a barcode with the new system than the old one.

If you don’t involve end users early and often, you’ll build something that looks great in a demo and falls apart in practice. The best projects I’ve seen include frontline staff in the evaluation process, the pilot phase, and the feedback loop.

Vendor Over-Reliance

It’s tempting to hand everything over to a vendor or systems integrator and trust them to deliver. But nobody understands your business better than your own people. Vendors understand their product. They don’t always understand your workflows, your culture, or your constraints.

The best outcomes come from genuine partnerships where internal teams and external experts work together. Internal teams bring domain knowledge. External teams bring technical expertise and implementation experience. When that balance is right, things tend to go well.

What Success Actually Looks Like

The transformation projects that succeed share a few traits:

• Specific, measurable goals tied to real business outcomes
• Executive sponsorship that goes beyond signing a cheque
• Phased implementation with clear milestones
• Heavy investment in training and change management
• Continuous feedback from the people actually using the systems

None of this is revolutionary advice. It’s not complicated. But it requires patience, discipline, and a willingness to do the unglamorous work of helping real people adapt to new ways of working.

The organisations that treat digital transformation as a technology project will keep failing. The ones that treat it as a people project, supported by technology, have a much better shot.