Foundation 5 of 20 · Control
The Same Fire Twice Is Not Bad Luck.
"Why do I fix the same problem every single week?" If you are great at fixing problems fast and they keep coming back anyway, you are treating the smoke. Here is how root cause analysis finds what is actually burning.
Last Updated: 10/25/2026 · Written by Dr. Paul Borosky, DBA, MBA
The Short Answer
What Is Root Cause Analysis?
Textbook Definition
Root cause analysis is a structured method for identifying the underlying cause of a problem, rather than its symptoms, so that corrective action prevents the problem from happening again.
In Plain English
Root cause analysis means finding the real reason a problem keeps happening, instead of fixing it every time it shows up. The symptom is what you see. The cause is why it happens. Fix the cause and the symptom goes away for good.
Why It Matters
Why Do the Same Problems Keep Coming Back?
Because fixing symptoms feels productive. You are fast, you are busy, you are winning. Every week you put out the fire, feel great, and move on. And every week it starts again, because the thing underneath it never changed.
Handling problems after they happen is called reactive management. Every business needs some. But it never ends on its own. The only way out is to stop asking "how do I fix this?" and start asking "why did this happen?"
Signs you have this problem:
- You fix the same kind of problem more than once a month.
- Each problem looks different on the surface: a chair one day, a lamp the next.
- You are proud of how fast you solve things.
- Your fix is "be more careful," and it has not worked.
- Employees are praised for putting out fires, never for preventing them.
- You pay for the same mistake over and over, in time, refunds, or fines.
What It Looks Like
What It Looks Like When You Only Fight the Fire
From the Fabled Forest · Chapter 5
Dumpster Dani runs a delivery service that will haul anything, anywhere, the moment anyone asks. She has solved more problems than anyone in the forest. She has never noticed how many of them are the same problem.
In one week she got four parking tickets in four loading zones. Each time, she had brought the wrong item in first, gone back to dig through her truck for the right one, and run over the time limit. Dishes on Monday. A lamp on Wednesday. A chair, then books. She fixed every one the same day and was proud of it.
Doctor Owl turned her ticket over and asked her why. Then he asked why again. And again, until the answer was something she could actually fix. It turned out the problem had more than one cause.
Dani's story is Chapter 5 of Management and Leadership for Small Businesses, Book 1 of Dr. Paul's Fabled Forest Business School Series.
The Fix
How to Do a Root Cause Analysis in 5 Steps
No consultants, no software. Two weeks of notes and one question, asked five times.
Write down every problem you fix for two weeks.
Every refund, every redo, every "quick fix." Just a line each. You are building the evidence.
Circle the ones that show up more than once.
Look past the surface. A wrong chair and a wrong lamp are the same problem: the wrong item went out.
Ask "why did this happen?" five times.
Each answer becomes the next question. Stop when the answer is something you can change, like a missing label, a missing step, or a missing rule.
Check for a second cause.
Some problems have more than one. Ask what else would have to change for the problem to stop completely.
Fix the cause, then count.
Make the change. Count the problem for a month. If it comes back, you have not found the whole cause yet. Go back to step 3.
Dr. Paul's Insight
Where most people slip is stopping at the first answer. "The driver grabbed the wrong box" is a symptom. "The shelves have no labels" is a cause. The first answer is almost always a symptom. Across 1,000+ clients, the fixes that last are the cheap, boring ones found at the bottom of the fifth why.
Sample: A Five Whys Chain
Here is what the five whys looks like on paper for a common small business problem.
| Why 1: Why are orders late? | They leave the shop a day after they are promised. |
| Why 2: Why do they leave a day late? | Packing waits on a key supply that runs out. |
| Why 3: Why does the supply run out? | Nobody reorders it until the box is empty. |
| Why 4: Why does nobody reorder in time? | There is no reorder point, and no one owns the count. |
| Why 5: Why is there no reorder point? | It was always in the owner's head. Nobody else knew the number. |
| Root cause and fix | Set a written reorder point, assign one person to the weekly count, and track late orders for a month. |
Sample for illustration. Your five answers will be different. The method is the same.
The Shortcut That Costs More
Reward Whoever Puts Out the Most Fires?
In the book, a company called Talon and Beak keeps offering owners shortcuts. Every one is legal. Every one sounds reasonable. Every one costs more than it saves. Here is the one in Chapter 5.
Pay a bonus to whoever puts out the most fires.
Fires get put out fast. Everyone looks busy. You feel like the team is on top of things.
You are paying a bonus for the problem never going away. Nobody gets rewarded for making sure the fire never starts, so nobody does.
Reward the person who finds the cause, not the person who fights the same fire every week. That one change shifts the whole team from reacting to fixing.
Watch
Video: The Five Whys, Live
What Is Root Cause Analysis? Symptom vs. Cause Explained
Dr. Paul runs the five whys on a real-looking business problem, start to finish.
From the Book
Why Did You Grab the Wrong Box?
Chapter 5 · Root Cause Analysis
If It Fits, I'll Haul It: A Raccoon's Fire Drill
"Why did you bring the wrong thing?"
Dani frowned. "Because I grabbed the wrong box off the truck."
"Why did you grab the wrong box?"
There was a long pause. Then Dani said, in a much smaller voice, "Because I can't tell them apart. The shelves in the truck don't have labels. I just know where everything is." Another pause. "Usually."
Was that the whole cause? Find out why Dani's problem had two roots, and get the five whys scroll, in Chapter 5. Book 1 of Dr. Paul's Fabled Forest Business School Series.
Get the Book on Amazon →FAQ
Root Cause Analysis Questions
What is an example of root cause analysis?
What is the difference between a symptom and a root cause?
What is the 5 whys method?
What is reactive management?
Keep Going
Related Foundations
Root cause analysis connects to five other foundations. Find the cause, then build the system that keeps it fixed. New to a term on this page? Every one is in the small business management glossary.
Foundation 1 · Standard Operating Procedures
Most root causes turn out to be a missing step. Write it down.
Foundation 9 · Continuous Improvement
Once the cause is fixed, keep measuring so it stays fixed.
Foundation 14 · Conflict Resolution
When the problem is between people, look for the cause, not the blame.
Foundation 18 · Decision-Making
Choose the fix on purpose, and set a date to check whether it worked.
Foundation 20 · Change Management
Rolling out the fix to a crew that likes the old way.
Written by Dr. Paul Borosky, DBA, MBA, business consultant, author, and educator with 14+ years and 1,000+ clients served. Want help finding what keeps breaking in your business? Dr. Paul works with owners one-on-one.
This page is for general educational purposes only. It is not legal, financial, tax, accounting, or other professional advice. Dollar figures are illustrations. The Fabled Forest and its characters are fictional. For decisions about your own business, consult a qualified professional.