Your Business isn’t Broken, but is It Working as Well as You Think?
Dave Stubberfield is a thought leader in the world of business transformation. He is the founder of Carter Consultancy, enabling organisations to become more profitable by having delighted customers and happier people. Co-author of the book Supercharging the Customer Experience.
When I start working with organisations, there’s a question I often ask during the discovery process. “What isn’t working?” It sounds like a straightforward question, but the answer is often surprisingly difficult to find. This is because, in many cases, nothing is obviously broken. Customers are still buying, orders are still being processed, projects are being delivered, and colleagues are busy. Revenue might be growing, and the leadership team is dealing with the usual challenges, but there isn’t necessarily a major crisis demanding attention.

So, if the business is working, why change anything? The problem is that “working” and “working well” are two very different things. Sometimes, success can hide inefficiency remarkably well.
Businesses evolve, but processes don’t always evolve with them
Nobody deliberately designs inefficient ways of working. They evolve over time. A process that made perfect sense when there were 15 employees can still be operating when there are 50, 100, or 500 people in the organisation.
The spreadsheet someone created as a temporary solution three years ago becomes business-critical. An approval stage gets added because something once went wrong, but nobody ever removes it. A weekly meeting is introduced to resolve a particular issue. The issue disappears, but the meeting remains firmly in everyone’s diary. One system doesn’t quite speak to another, so somebody manually transfers the information between them. Another department needs slightly different information, so they create their own tracker.
Individually, none of these things feels particularly significant, but they accumulate. Five minutes here, ten minutes there. An extra email, another spreadsheet, another approval, another meeting, another manual check.
Multiply that across dozens or hundreds of people, thousands of transactions, and an entire year, and suddenly those seemingly insignificant inefficiencies become significant.
The difficulty is that we become used to them. Eventually, they stop being seen as problems and simply become, “That’s how we do things here.”
The danger of “good enough”
One of the biggest barriers to improvement isn't necessarily poor performance. It's what is deemed acceptable performance.
When something is obviously failing, it gets attention. A customer complains. A deadline is missed. A system goes down. Costs increase dramatically. A major problem lands on somebody's desk.
Something has to happen. But what about the things that aren't failing? What about the process that takes six steps when it could take three? The report that takes somebody half a day every week to produce manually? The customer query that meets the agreed response time but passes through four different people before it gets resolved? The manager who spends Friday afternoon pulling information from different spreadsheets just to understand what happened that week? The employee who has created their own workaround because the official process doesn't quite work?
None of these necessarily causes a crisis, but collectively, they create friction, and friction is expensive. Not just financially, but in terms of time, capacity, energy, employee engagement, and, eventually, customer experience.
Your best people might be hiding your biggest problems
There is another reason inefficiency can be difficult to see. Good people are incredibly good at compensating for bad processes.
They remember the things the system doesn't. They create their own spreadsheets. They know which person in another department can actually get something done, and they chase the approval nobody else remembered. They also manually check the information because they don't completely trust the system. They stay late to make sure the customer gets what they were promised.
They know the workaround, and because they know the workaround, the process appears to work. I've seen this repeatedly in organisations. What looks like a functioning process from a leadership perspective can look very different when you sit alongside the people actually doing the work.
This should prompt an uncomfortable question. If your best people disappeared tomorrow, would your processes still work?
If the answer is no, you may not have a robust process. You may simply have brilliant people holding it together. That creates operational risk, but it also creates an employee experience problem. We shouldn't be relying on people to continually overcome organisational friction simply to do their jobs well.
Stop looking for failure, start looking for friction
Perhaps we need to change the question. Instead of asking, “What's broken?”, ask, “Where are we making things harder than they need to be?”
That changes the conversation. Look at your customers. Where do they have to chase you? Where do they repeat information they've already provided? Where are they waiting unnecessarily? Which parts of their journey have been designed around what's convenient for your organisation rather than what's easy for them?
Look at your people. What frustrates them every week? What repetitive activities consume their time? Where have they developed workarounds? What stops them from spending more time on the work that actually adds value?
Look at your processes. Where are the handoffs? The bottlenecks? The duplication? The rework? Where are approvals happening because they've always happened rather than because they're genuinely needed?
Look at your technology. How many spreadsheets are compensating for gaps between systems? How often is information entered more than once? How much activity still relies on somebody copying and pasting information from one place to another?
Look at your managers. How much of their time is spent trying to understand what's happening rather than deciding what to do about it?
Those are very different questions from asking whether the business is performing, and they often reveal very different answers.
Your KPIs might not tell you something is wrong
Measurement is essential, but we need to be careful about what our measures are actually telling us. A key performance indicator (KPI) can tell you that an outcome happened, but it doesn't necessarily tell you how difficult it was to achieve.
Imagine a customer query is resolved within the agreed service level agreement (SLA), and the KPI is green. But what if that query passed through three departments, generated 12 emails, and required four people to resolve it? The customer received their answer on time, so technically, the process worked. But was it efficient?
A project might be delivered on schedule, again with a green KPI. But what if the team had to work additional hours for the final three weeks because of avoidable rework? Again, the outcome was achieved, but at what cost?
Revenue might be growing while operational complexity is quietly eroding margin. Customer satisfaction might look healthy while employees are working incredibly hard behind the scenes to protect it. This is why organisations need to understand not only whether the outcome happened, but how effectively it was achieved.
Sometimes, the green dashboard is hiding a lot of amber underneath it.
Technology isn't always the first answer
When organisations recognise these inefficiencies, there is understandably a temptation to reach for technology. A new platform, automation, or, more recently, artificial intelligence (AI).
Technology absolutely can transform the way organisations operate, but there is an important step that needs to come first. Understand the process.
If a process contains unnecessary steps, duplication, unclear ownership, or poor decision-making, automating it doesn't necessarily solve the problem. You will ultimately automate the inefficiency.
The sequence should be relatively simple. Understand. Simplify. Improve. Digitise or automate. Measure. Technology should enable better ways of working, not compensate for the fact that we haven't challenged the existing ones.
Improvement doesn't have to mean a transformation programme
The word “transformation” can sometimes create a problem of its own. It sounds big, expensive, and disruptive. Something requiring a programme office, consultants, technology investment, steering committees, and an 18-month roadmap.
Sometimes that is necessary, but often it isn't where you need to start. Improvement might begin by sitting alongside someone while they do their job and mapping one process from beginning to end. It could be following one customer journey, or it may be measuring something you've never previously thought to measure.
Small changes can have significant consequences when they remove something that happens hundreds or thousands of times. The important thing is to start looking.
Try this for an hour
If you're leading an organisation, department, or team, spend an hour asking these five questions:
What do our people repeatedly complain about having to do?
Where are spreadsheets, manual processes, or workarounds keeping things running?
What do our customers regularly have to chase us for?
Where do our managers spend time gathering information rather than acting on it?
What do we still do simply because “we've always done it that way”?
Don't answer them only from the boardroom. Ask the people doing the work. The people closest to the process usually know exactly where the friction is. They've often just stopped believing anyone wants to hear about it.
Your business doesn't need to be broken
There is a tendency to wait for something to go wrong before we improve it. We wait for costs to become a problem. For customer satisfaction to fall. For employees to leave. For capacity to disappear. For margins to tighten. For growth to expose processes that can no longer cope. But improvement shouldn't only be a response to failure.
Your organisation can be successful, profitable, and growing while still being unnecessarily difficult to work in, manage, and buy from. The biggest opportunities aren't always found in the major problems everyone can see. Sometimes, they're hidden in the hundreds of small frustrations, workarounds, delays, and inefficiencies that everyone has simply stopped noticing.
So perhaps the question isn't, “Is our business working?” Perhaps it's, “Is it working as well as it could?” If you haven't asked that question for a while, the answer might surprise you.
Read more from Dave Stubberfield
Dave Stubberfield, Fractional Transformation Expert
Dave Stubberfield is an expert in the world of Customer Experience, Continuous Improvement and Change Management. His background working in corporate companies, on the receiving end and delivering transformation, has given him the tools and capability to enable change for other organisations. He is the founder and Fractional Transformation Expert for Carter Consultancy.










