Most technology problems are ownership, process, or decision-making problems in a different place.
Technology exposes these conditions. It does not create them, and replacing the platform does not resolve them.
Before asking which system to use, it is worth asking who owns it, what it is for, and what happens when it goes wrong.
There is a conversation that recurs across organisations of every size and type.
We spent six figures on a CRM and nothing changed. The reporting still is not trusted. Everyone keeps their own spreadsheet. The sales pipeline never matches reality.
The instinct is to look at the technology. Different platform, better configuration, more training. Sometimes a full re-implementation.
The problems usually return. Sometimes faster than before.
What the evidence looks like
The symptoms are consistent enough to be recognisable. A platform is in place. People are using it. But something is not working.
Data is duplicated across systems. The official reports do not reflect what people actually know. Client records are incomplete because nobody agreed what should go in them. The pipeline figure in the system and the pipeline figure discussed in meetings are different numbers. Teams have quietly rebuilt the process in spreadsheets alongside the platform, because the platform does not fit how the work actually runs.
None of these are technology problems. They are the visible surface of something else.
Worth knowing
Gartner has consistently found that CRM failure rates sit between 47 and 63 percent, with adoption and data quality cited as primary causes far more often than technical performance. The technology rarely fails on its own terms.
As with websites, the same logic applies to any digital investment: a new platform built on the same unclear foundations will, within a short time, look much like the one it replaced. A website is not a strategy for the same reason a CRM is not a process.
Notes from Not On Mondays
If this is useful, we write more like it
Short notes on delivery, operations and the systems that help organisations move with less friction.
Why the same problems keep returning
Technology tends to become the place where organisational uncertainty accumulates.
When ownership is unclear, it shows up as fields nobody agrees on and records nobody maintains. When decisions are not being made, it shows up as workflows nobody has signed off on and reports that no one acts on. When process has not been defined, it shows up as duplicate data, manual workarounds, and teams solving the same problem in three different ways simultaneously.
Installing a better platform into these conditions does not resolve them. It inherits them. And because the new system is unfamiliar, the workarounds multiply faster than before.
Technology exposes organisational problems. It rarely creates them.
The organisations that get the most from their systems are not always the ones who chose the best platform. They are the ones who sorted out ownership, process, and decision-making before, or alongside, the technology investment. Having the right operating layer in place is what makes the difference.
The right question
Before the next platform decision, or the next re-implementation, three questions tend to surface the real problem quickly.
Who owns this, and what does that ownership actually include?
What does good look like, and has everyone agreed on that?
What happens when something goes wrong, and who decides?
If these questions do not have clear answers, the technology decision is probably the second conversation, not the first.
This matters beyond CRM and reporting. It applies to why users do not contact you, why the website rebuild did not improve enquiries, why new systems promise visibility and do not deliver it. The common thread is rarely the technology itself.
You may not have a technology problem. You may have a clarity problem.
Related
A website is not a strategy
A new website may improve appearances. It rarely fixes the underlying causes of why the old one was not working.