The failure rate of digital transformation projects is one of the worst-kept secrets in business. Estimates vary, but most research puts it somewhere between 70 and 85 percent. For something organisations spend billions on globally every year, that is a remarkable number. And the reasons are almost never technical.
The technology is rarely the problem
When a CRM implementation collapses, or a new platform fails to get adopted, or an automation project quietly gets shelved six months after launch, the post-mortem usually points at the software. Wrong choice. Too complex. Poor integration with existing systems.
These are symptoms, not causes. The underlying problem almost always traces back to the brief that existed before a single vendor was contacted, a single demo was booked, or a single line of code was written.
Businesses know they need to change. They have a rough sense of the destination. But the thinking between those two points — what exactly needs to change, for whom, measured how, delivered by whom, and in what sequence — is rarely done with the rigour the investment deserves.
So they buy a platform. They configure it to mirror the processes they already have. And then they wonder why nothing feels any different.
Three things that kill transformation before it begins
1. The brief is built around tools, not outcomes
The most common mistake is starting with a technology decision. “We need a new CRM.” “We need to automate our reporting.” “We need a customer portal.” These are solutions presented as briefs, and they skip the most important question: what does good actually look like when this is done?
A brief built around outcomes sounds different. “We need our sales team to spend less time on admin and more time with clients.” “We need to understand which of our customers are most at risk of leaving.” “We need our operations team to stop relying on spreadsheets that only one person understands.” These briefs lead to different conversations, different choices, and significantly better results.
2. The people who will use it are not involved in designing it
Transformation projects are typically scoped by senior leaders and delivered by either internal IT teams or external consultants. The people who will actually use the new system every day are consulted late, if at all. Their feedback is taken as resistance rather than intelligence. And then everyone is surprised when adoption is poor.
The businesses that get this right involve end users early. Not to design the system by committee, but to understand the reality of how work actually gets done, which is almost always different from how leadership believes it gets done.
3. Change management is treated as an afterthought
Technology implementations routinely underinvest in the human side of change. Training gets compressed. Communication is inconsistent. Leaders champion the project in the announcement and then disappear back into their calendars. And the new system competes with the old habits that everyone already knows how to use.
A new platform without a change programme is just expensive shelfware. The organisations that see real returns treat the people side of the project with at least as much rigour as the technical side.
What to do instead
Before any vendor is engaged, before any budget is signed off, before any internal project team is assembled, spend serious time on three questions.
What specific problem are we solving, and how will we know when it is solved? What does our current process actually look like, not on paper, but in practice? And who needs to change their behaviour for this to work, and what will make them willing to do that?
The answers are rarely comfortable. They sometimes reveal that the technology is not the priority at all, that the process needs fixing before the platform does. But they are the difference between a transformation that delivers and one that becomes a case study in what not to do.
The view from the top
At Towers, we start every digital transformation engagement with an audit of the thinking before we touch the technology. It is slower at the beginning and significantly faster overall. If you are about to invest in a new system and you are not completely confident in the brief behind it, that is the conversation we should have first.