You’ve fixed this before. You know you have. You sat down, sorted it out, told the team what to do differently, and moved on. Then three weeks later, there it is again. Same problem, different Tuesday.
It’s not bad luck. It’s not your staff being useless. And honestly, it’s not even that the fix didn’t work. The fix worked fine. The problem is that you fixed the wrong thing.
You’re Solving the Symptom, Not the Cause
Most small business owners are excellent problem-solvers. That’s usually how they built the business in the first place. But that same instinct, the one that says “sort it fast and move on”, is exactly what keeps the cycle going.
When a customer order goes out late, the instinct is to chase the job, apologise to the client, and make sure it goes out today. Problem solved. Except it isn’t. Because nothing about that fix prevents the same order from going out late next month.
The real question isn’t “how do we get this out the door today?” It’s “why wasn’t it processed on time in the first place?”
Those are very different questions. And only one of them ends the cycle.
The One Question That Changes Everything
There’s a simple technique that’s been used in manufacturing and operations for decades. You ask “why” repeatedly until you hit something you can actually fix.
Not patch. Fix.
Here’s how it works on a real example:
Problem: Invoices are going out late.
- Why are invoices going out late? Staff are tied up with other tasks when billing time comes around.
- Why are they tied up? They spend time chasing missing job details before they can raise the invoice.
- Why are they chasing details? There’s no standard process for capturing that information when the job is booked.
That’s the real problem. Not busy staff. Not bad attitude. A missing intake process.
Fix that, and the late invoices stop. Not because you reminded everyone to try harder, but because the gap that caused the problem no longer exists.
The key is not stopping at the first answer. Most people ask why once, hear “staff are busy”, and either accept it or go and have a word with the team.
Neither of those fixes anything. You need to keep going until you reach something structural, a missing process, an unclear responsibility, a gap in information flow. That’s where the permanent fix lives.
Where This Breaks Down in Most Businesses
The 5 Whys works well on process problems with a clear chain of cause and effect.
It works less well when the problem is genuinely complex or when five different people would give five different answers to the same question.
If that happens, it usually means the problem isn’t one thing.
It’s a cluster of things that have built up over time. In that case, pick the most frequent version of the problem and run the process on that specific instance, not the general pattern. Specificity is what makes this useful.
The Problems You’re Probably Living With Right Now
These are the recurring ones. The ones that come back no matter how many times you sort them out.
| Recurring Problem | What It Looks Like | Likely Root Cause |
|---|---|---|
| Late quotes | Clients waiting days for a price | No standard process for capturing job requirements upfront |
| Billing errors | Wrong amounts, missing items, disputes | Manual data entry with no verification step |
| Project delays | Jobs running over time or budget | Unclear handovers between team members or stages |
| Customer complaints | Same issues raised repeatedly | Expectations set inconsistently at the point of sale |
| Staff frustration | Team asking the same questions over and over | No documented process for them to refer to |
If two or more of those feel familiar, you are not dealing with a people problem. You are dealing with a systems problem. The people are just the ones who end up carrying it.
How to Break the Cycle for Good
Once you’ve found the real cause, the fix has to become the new normal. This is where most attempts fall apart. The owner finds the root cause, sorts it out personally, and then drifts back to firefighting. Six weeks later, the same problem surfaces because the fix only lived in one person’s head.
Here’s the sequence that actually sticks:
- Define the specific problem. Not “we have communication issues.” Something like “job sheets are missing three key pieces of information before work starts.”
- Run the 5 Whys on that specific problem. Keep going until you hit a process gap, a missing responsibility, or an information breakdown.
- Decide on the structural fix. A checklist, a standard form, a clear handover step. Something that exists outside of memory.
- Put it where the work happens. Not in a folder nobody opens. On the wall, in the job management system, at the point in the workflow where it needs to be used.
- Check it’s working after two weeks. Not to micromanage. To catch anything the fix missed before the problem has a chance to come back.
The goal isn’t a perfect system. The goal is a problem that stops coming back.
The Shift That Changes How You Run the Business
Right now, your value to the business is probably tied up in your ability to spot problems and fix them fast. That feels like a strength. Over time, it becomes the ceiling.
When you’re the one who holds everything together, the business can only grow as far as your personal capacity. Every recurring problem you permanently fix is a piece of that load you never have to carry again. That’s not a small thing.
That’s how you eventually build something that runs without you standing in the middle of it every day.
The Bottleneck Buster Method is built on exactly this: finding the real cause, fixing it structurally, and moving on rather than going round the same loop again. Not because the problems are small, but because your time is worth more than solving the same one twice.
