How to Find the Root Cause of a Problem at Work
To find the root cause of a problem, do not stop at the first thing that went wrong. Ask why it happened, then ask why again, until you reach a cause that you can change and that would stop the problem coming back. Then check that cause with a simple test before you spend time fixing it. If your team keeps fixing the same problem every week, you are fixing symptoms.
Why symptoms keep returning
A symptom is what you see. A cause is why it is there. If a pipe leaks and you wipe the floor each morning, the floor is clean, and the pipe is still leaking.
At work it looks like this: an order is wrong, so someone corrects it. Next week another order is wrong, and someone corrects that. Everyone is busy and everyone is helpful, and nothing improves. Fixing the visible problem feels productive, so it is easy to stop there.
A good sign that you are looking at a symptom is the word "again". If you say "this happened again", look for the cause.
The five whys, used carefully
The five whys is a simple method: state the problem, ask "why did this happen?", then ask "why?" about the answer. Repeat until you reach something your team can actually change. Five is a guide, not a rule. Sometimes three is enough, sometimes seven.
Use it carefully.
- Stay with facts. Each answer should be something you can check, not a guess. "Because Tom is careless" is not an answer. It is an opinion and it stops the thinking.
- Look at the process, not the person. If a person made a mistake, ask why the process allowed it.
- Follow more than one path. Often a problem has two causes. If one answer branches, follow both.
- Stop at something you can act on. "Because people make mistakes" cannot be fixed. "Because the form has no required field for the address" can.
Map contributing causes
Problems at work rarely have one cause. A cause map shows all the factors on one page and helps the team see them together.
Take a sheet of paper. Write the problem on the right. Draw lines to the left for the main areas that may contribute. Common areas are people (training, workload), process (steps, checks), information (forms, data) and equipment or software. Under each area, write the possible causes the team can think of.
You are not looking for blame. You are looking for the points where a change would have the most effect. Mark the two or three causes that you think matter most and that you can influence.
Test the hypothesis before fixing
A cause you found by thinking is a hypothesis. Before you change a process, check it against reality.
Ask: "If this is the cause, what else should be true?" Then look.
- If the cause is a confusing form, you should see the same mistake on many forms, not just one.
- If the cause is the end-of-day rush, the errors should cluster in the last hour.
- If the cause is a missing training step, the errors should come mostly from people who joined in the last month.
Pull a small sample, perhaps ten or twenty cases, and look. If the pattern is there, you have good evidence. If not, go back to the map.
Example: the invoices that keep going out wrong
Say a small company sends about forty invoices a week and, every week, three or four have the wrong customer address. Each time, Lucia in accounts corrects it and sends it again. Customers complain, and payment is delayed.
The team asks why.
- Why are the addresses wrong? Because the address on the invoice is not the customer's current address.
- Why? Because the invoice takes the address from the customer record, and the record is old.
- Why is the record old? Because when customers send a change of address, the sales team writes it in an email or in their own notes, and does not update the record.
- Why not? Because updating the record is done in a different system, and nobody is told it is their job.
- Why does it not appear in anyone's job? Because there is no step in the order process that says "check the customer record".
The root cause is a missing step and an unclear owner, not careless people.
Before they act, they test it. Lucia lists the last fifteen wrong invoices. Twelve are for customers whose address changed in the previous six months. The pattern fits.
The fix is small: add one step to the order checklist, "Is the address on the customer record the same as on the order?", and give it to the person who takes the order. After a month, Lucia counts the wrong invoices again. If the count has dropped, the cause was right. If it has not, the team goes back to the map.
When this does not work
- You cannot get facts. If nobody recorded what happened, start recording. Even a short note with date, what went wrong and what was done gives you something to look at in a month.
- The root cause is outside your control. Sometimes the cause is a supplier or a company policy. Fix the part you control, and report the rest to your manager with your evidence.
- The problem is rare. For a one-time event, a long analysis may cost more than the event. Fix it, note it, and look deeper only if it happens again.
- Safety, legal or regulated incidents. Follow your employer's formal investigation procedure and the rules of the body that regulates your industry. This article is not a replacement for them.
When you have found a cause, you still need to choose what to do. See how to make a decision at work when you are unsure. Numbers can help you see the pattern, as in how to read a dashboard at work. For the wider set of skills, read our guide to critical thinking at work.
Learn this in five minutes
The Root Cause Analysis track has five five-minute lessons: why symptoms keep returning, using the five whys carefully, mapping causes and contributing factors, testing root-cause hypotheses, and preventing problems from recurring. Each one uses a short work case, so you can practise before you try it with your team.