FutureSkilz.
Practise · 05

Skill Shot · Problem solving · foundational

Find the cause, not just the symptom

By the end you can: trace a repeating problem, step by step, from what you can see to a cause you can fix, using five checkable whys.

About 5 minutes with AryaPrerequisite: Describe a problem with facts: who, what, where, when and how big (the 5W2H step in the Problem Solving kit)Draft: awaiting human review

Arya · AI teacher

Arya is waiting.

Scene 1 of 7 · 0:00 to 0:32

A fix that treats the symptom lasts only two days

The packing line: one customer, late for three weeks

Key points

  • Three weeks of late orders
  • The talking-to worked for two days
  • Why does the problem keep coming back?

Illustrative case, written for this lesson

The packing line

  • One customer's orders leave a day late
  • Late for three weeks
  • Fix tried: remind the packers to hurry
  • Result: better for two days, then late again

TakeawayWhen a problem returns after a fix, the fix was aimed at the symptom.

Arya says (captions)

Namaste. I am Arya, your AI teacher for this Skill Shot. Picture a small packing line. For three weeks, the orders for one customer have left a day late. The team has already tried the obvious fix: remind everyone to pack faster. It worked for two days, then the orders were late again. Here is the question for today: why does a problem you thought you had fixed keep coming back?

Arya is an AI teacher and her voice is synthetic. This Skill Shot was designed by FutureSkilz Learning Design. The case is made up for teaching and is not any expert's experience. It is a draft and has not yet been reviewed by a person.

Ask Arya

Stuck, or want it said another way?

Arya is an AI. She answers only from this lesson, gives hints and not answers, and asks you to try it in your own words. Please do not share personal details.

Sign in and your questions are kept with your profile; as a visitor, nothing you ask is saved.

Check yourself

Three quick questions

1. A manager says, 'The root cause is that the packer was careless.' What is the best response?

2. Why were the labels late? Which answer is best?

3. When is the five whys, on its own, not enough?

Take it to work

Pick one problem from the last month that came back after a fix. On one card, write the problem as a factual sentence and your chain of whys. Mark which answers you have checked. Propose one action aimed at the deepest cause, and share it with your team lead.

Try it, then ask Arya

Your practice note

Write a few sentences on how you would use this on a real problem from your work: what happened, what you did, and what you expect. Arya will read it against what this Skill Shot teaches. Please leave out names and personal details.

0 words · about 12 or more gives a useful reading

How useful was this Skill Shot?

One tap. Your rating tells us what to improve.

Remember

  • Ask why until you reach a cause the process lets you change.
  • Every answer must be a fact you can check, and must explain the one before it.
  • Treat a person-level answer such as 'human error' as the start of the next question, not the end.

Watch out for

  • Stopping at a person ('careless', 'forgot') instead of asking what in the process allowed it.
  • Jumping to a solution before the cause is checked.
  • Answering with opinions or guesses instead of facts that can be checked.
  • Following only one chain when the problem has more than one cause.
  • Treating 'five' as a rule: stop when you reach a cause you can fix, not when you have counted five.

Limits: Works best on problems with a fairly direct chain of causes. Complex problems with several interacting causes need data and other tools alongside it.

Where this fits

Skill set
Solve a problem that keeps coming back
Capability module
Problem solving at work
Learning path
New joiner readiness › Operations (and any function)

After 'Describe a problem with facts'. Before 'Choose the problem to solve first' and 'Plan and test a fix'.

Next

Full transcript and sources

1. A fix that treats the symptom lasts only two days · 32s

Namaste. I am Arya, your AI teacher for this Skill Shot. Picture a small packing line. For three weeks, the orders for one customer have left a day late. The team has already tried the obvious fix: remind everyone to pack faster. It worked for two days, then the orders were late again. Here is the question for today: why does a problem you thought you had fixed keep coming back?

2. By the end you can trace a repeating problem to a cause you can fix · 28s

By the end of this Skill Shot, you will be able to take a problem that keeps coming back and trace it, step by step, from what you can see to a cause you can actually fix. You will use a simple method called the five whys. It helps any time a fix does not last: late orders, repeat defects, missed handovers, rework.

3. The symptom is what you see; the root cause is what makes it happen · 49s

Start with a leaking tap. You can keep wiping the floor, which treats the symptom. Or you can change the washer, which removes the cause. A symptom is what you notice. A root cause is the reason that, once you remove it, the problem stops coming back. The five whys is the habit of asking why did that happen, again and again, and answering each time with something you can check. Two rules matter. Each answer must be a fact you can check. And each answer must explain the one before it. The number five is a guide, not a law. Sometimes three whys are enough, sometimes you need seven.

4. Five checkable whys take you from the symptom to the cause · 51s

Here is the method. First, write the problem as one factual sentence. Second, ask why, and answer with a fact. Third, check that answer: look at the records, count, or ask the person who does the work. Fourth, repeat until you reach a cause the process lets you change. Fifth, test it: if we removed this cause, would the problem stop? Watch for four common errors. Stopping at a person, like careless or forgot. Jumping to a solution too early. Answering with opinions. And following only one chain when there may be several. If an answer is we do not know, that is not the end. It tells you what to go and find out.

5. On the packing line, the fifth why finds a missing handover step, not a slow packer · 77s

Now let us go back to the packing line. Why were the orders late? Because they were not packed before the truck came, as the packers were waiting for labels. Why were the labels late? Because label printing starts only after the final quantity is confirmed in the system. Why was the quantity confirmed late? Because the last batch of the day is booked into stock the next morning. Why the next morning? Because the stores clerk's shift ends before the last batch finishes. And why does nobody book it before leaving? Because there is no end-of-shift handover step. That is a cause the process lets us change. So the action is simple: add a five-minute handover, and book the last batch before the shift ends. Notice what we did not do. We did not blame the packers, or the clerk. We fixed the process. One caveat: in real work you would check each answer against the records before acting. In this story, I am telling you the checks passed, so treat it as an illustration.

6. Your turn: choose the next question on a new problem · 25s

Your turn. A new problem: delivery notes keep showing the wrong quantities. The first answer on the board is: the picker counted wrong. What is the best next why? Take a few seconds to think, then choose.

7. This week, run five whys on one problem that keeps coming back · 55s

Let us pull it together. Ask why until you reach a cause the process lets you change. Make every answer a fact you can check. And when the answer is a person, such as human error, treat it as the start of the next question, not the end. Here is your task at work. Pick one problem from the last month that came back after a fix. On one card, write the problem as a factual sentence and your chain of whys. Mark which answers you have checked. Then propose one action aimed at the deepest cause, and share it with your team lead. Next, you can try the five whys tool on a real problem of your own. Well done, and thank you for learning with me.

Sources

  • S1 · Illustrative cases (the packing line and the delivery notes), written for this lesson by FutureSkilz Learning Design. Not from any expert's experience or any real company.
  • S2 · The five whys as a root-cause method, as taught in the FutureSkilz Problem Solving kit (5 Whys tool). Method steps, errors and limits follow common problem-solving practice and carry no figures or outcomes.
  • S3 · FutureSkilz Skill Shot instructional design skill, version 1.0.0 (structure, challenge and transfer task).

Attribution: FutureSkilz Learning Design (illustrative case; not drawn from any expert's experience). Version 0.1.0.