Every business has one. The problem that gets fixed and then comes back. The invoice error you sorted in March that reappeared in May.
The delivery went out late again, despite everyone’s conversation last time. The customer complaint that sounds suspiciously like the one from two months ago.
Each time it happens, someone puts out the fire, and everyone moves on. Six weeks later, there it is again. Same problem, different day, usually a different person getting the blame.
And somehow it always ends up on your desk, because you are the only one who knows how to sort it.
If that sounds familiar, this article was written for you. Recurring problems are not bad luck, and they are almost never a people problem.
They are a signal. Once you understand what they are telling you, they become the easiest problems in your business to fix permanently.
The fix that never holds
When a problem appears, the natural response is to fix what is in front of you. An order went out wrong, so you correct the order. An invoice had the wrong amount, so you reissued it.
A client did not get their report on time, so you apologise and send it.
That is the right thing to do in the moment, because the customer needs the fix. Here is the trap, though. Fixing the instance of the problem feels like fixing the problem.
It is not. You have treated the symptom and left the cause completely untouched.
Think of it as taking a painkiller for a toothache. The pain goes away, the tooth is still rotten, and the pain will come back at a worse time.
The cost of leaving it alone is higher than it feels. An error that takes two hours to sort and shows up twice a month quietly burns around 50 hours a year.
Price those hours at what your time is actually worth, then add the reprinted orders, the refunds, and the goodwill spent apologising to the same customer twice.
One small recurring problem can easily cost a business four figures a year. Most owners never add up that sum because each individual fire feels too small to measure.
Over 34 years working inside major operations, I saw this pattern everywhere, at every scale.
Big organisations with entire quality departments still fell into it.
The team was busy, the fix was quick, and nobody had time to ask the harder question. Why did this happen in the first place?
It is not your people, it is your process
When the same problem keeps recurring, most businesses eventually settle on one of two conclusions. Either someone is not paying attention, or someone needs more training.
Occasionally that is true. Usually it is not.
Here is a simple test. If the problem happens regardless of who is doing the work, it is not a people problem.
If the invoice error happens when Sarah does the invoicing and when Tom covers for her, the problem is not Sarah or Tom. It is the invoicing process.
This distinction matters enormously, and not just for accuracy. When people get blamed for process problems, two things happen.
First, the problem never gets fixed, because the actual cause was never touched. Second, people start hiding problems, because raising one means wearing the blame for it.
Now you have the original fault plus a team that keeps quiet about the next one. That is a far more expensive position to be in.
Businesses that fix recurring problems permanently all share one habit. When something goes wrong, they ask what about the process allowed this to happen, not who did it.
The difference between a symptom and a root cause
A symptom is what you can see. A root cause is what keeps producing it. Problems recur because businesses fix symptoms and leave root causes in place.
Here is what that looks like in practice. A small e-commerce business kept sending orders to old addresses. The visible problem, the symptom, was wrong deliveries.
Each time, the fix was to resend the order to the correct address and absorb the cost. Frustrating, expensive, and recurring.
The root cause turned out to be something nobody had looked at.
Customer address updates arrived by email, by phone, and through the website contact form, but no step in the order process checked for pending updates before dispatch. Updates sat in an inbox while orders went out.
The process practically guaranteed the problem would keep happening.
Once that was visible, the fix was simple.
Address changes were consolidated in one place, and the dispatch step included a check against them. The problem did not reduce. It stopped.
Notice what happened there. Nobody worked harder, nobody got retrained, and nobody got blamed. One small change at the actual point of failure turned a recurring problem into a solved one.
Ask why five times
There is a tool for getting from symptom to root cause, and it is probably the simplest improvement tool ever created. It originated at Toyota decades ago and has spread across almost every industry since. It is called Five Whys.
Before you roll your eyes at anything with a Toyota heritage, hear me out.
This is not corporate methodology. There is no software, no certification, no consultant, and no budget. If your business has a pen and twenty minutes, it has everything the tool requires.
The big companies did not earn results from this because they were big. They earned them because the tool works.
It runs exactly the way it sounds. You start with the problem and ask why it happened. You take that answer and ask why again, and again, with each answer becoming the subject of the next question.
By the fifth “why,” you have usually moved past the surface explanation and reached the underlying cause. That is the thing which, once fixed, stops the problem coming back.
A worked example
Here is how it plays out in a service business:
The problem. A client’s monthly report went out three days late.
- Why? The data needed for the report was not ready in time.
- Why? The person who compiles the data was waiting on figures from a colleague.
- Why? The colleague did not know the figures were due, because nobody had told them the deadline.
- Why? There is no set schedule for submitting monthly figures.
- Why? The reporting process was never actually written down. It grew up informally and lives in people’s heads.
Look at where that chain ended. It did not end with a person. It ended with a missing process, no documented schedule, and no defined handover.
Stop at the first “why,” and you would chase the data faster this month, only to be late again next month. The fifth why hands you something you can permanently fix.
Write the schedule down, agree the submission date, done.
Two rules that make it work
Never end on a person. If your chain of whys ends at “because John forgot,” you have not finished. Ask why the process depends on John remembering.
A process that fails when one person forgets is fragile, and fragile processes are fixable. People forgetting is not.
Always end with an action. A root cause without a fix attached is just an interesting observation. Every Five Whys session should finish with a specific change, a named owner, and a date.
Otherwise, you have diagnosed the illness and skipped the treatment.
The backwards check
There is a simple way to verify you have found the real cause. Read the chain backward using the word “therefore.” The reporting process was never documented; therefore, there was no set schedule for figures.
The colleague did not know the deadline; therefore, the data was late, and therefore the report was late. If the chain reads logically in reverse, your analysis is solid.
If a link feels like a jump, that is exactly where you need to dig further.
It works in any business, physical or digital
This is not a manufacturing tool awkwardly stretched to fit other businesses. Root cause thinking applies anywhere work happens.
In a workshop, a warehouse, or a trades firm, recurring problems look like jobs going out incomplete, materials running short mid-job, or the same machine fault reappearing. In an agency, a consultancy, or an online store, they look like missed deadlines, briefs that keep getting misunderstood, and handovers where information falls through the cracks.
The surface problems differ. The underlying pattern is identical: a process with a weak point nobody has examined, producing the same failure on repeat.
Try it this week
You might be thinking you have not got time to breathe, let alone fix processes. That is exactly why this exercise earns its place. Twenty minutes spent once beats two hours spent every month, forever. This is not a project. It is one sitting, with a pen.
Here is the exercise, start to finish.
- Pick the most annoying recurring problem in your business right now. The one that makes you sigh because you know you have sorted it before.
- Write the problem at the top of a blank page.
- Ask why it happened, and write the answer underneath.
- Ask why again about that answer, and keep going until you hit something structural. A missing step, an unclear handover, an undocumented process, or information living in one person’s head.
- Check yourself. When your answer is a process gap rather than a person’s name, you have arrived.
- Decide on one specific change, assign an owner, and set a date.
Most people doing this for the first time are surprised by two things. They reach the real cause far faster than expected, and it seems obvious once written down.
That is normal. Root causes are rarely hidden because they are complicated. They are hidden because nobody ever went looking.
Find out where to start
If recurring problems are costing your business time and money, the smartest first move is to identify your biggest constraints.
The free Bottleneck Finder Assessment walks you through a short set of questions and highlights where your business is losing time, money, and momentum.
It takes a couple of minutes, and it tells you exactly which problem deserves your first Five Whys.
Richard Darby is the founder of Better Flow Systems and holds a Lean Six Sigma Black Belt. After 34 years of operational improvement work inside major global organisations including GE, British Airways, and The Nielsen Company, he now helps small and medium-sized businesses find bottlenecks and cut waste, without the jargon or the consultant fees.
