NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 12 — Root Cause Analysis and PreventionLesson 2 of 4
Video lesson

The 5 Whys and the Fishbone Diagram

BeginnerVideo lesson
9 min readBeginner

Where you are: Module 12 — Root Cause Analysis and Prevention · Lesson 12.2 · Based on Chapter 12 (§12.2–12.3, Figure 12.1) of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Apply the 5 Whys to trace a single chain of cause to an actionable root.
  • Explain how stopping at different "whys" changes whether a problem recurs.
  • Construct a fishbone (Ishikawa) diagram using the book's six categories.
  • Choose between the 5 Whys and a fishbone diagram for a given problem.

Watch: The 5 Whys and the Fishbone Diagram

The video animates the book's 5 Whys example (a server stopped by a full disk) one question at a time, then shows what happens if you stop early. It then builds the book's Figure 12.1, a fishbone diagram for a slow website, bone by bone. Keep these questions in mind:

  • At which "why" does the answer stop being about this server and start being about every server?
  • When is a single chain of whys not enough?
  • What happens after the fishbone is drawn?

The 5 Whys

The 5 Whys is the simplest root cause technique there is. In the book's words, you ask "Why?" repeatedly, usually about five times, until the answer is a cause that can be corrected. Each question is about the previous answer, so the questions form a chain from the symptom down to the root.

Here is the book's example, continuing the server story from Lesson 12.1:

  1. Why did the server stop? The disk was full.
  2. Why was the disk full? Log files had grown very large.
  3. Why had they grown so large? Old logs were never deleted.
  4. Why were they never deleted? Log rotation was not configured.
  5. Why was it not configured? It is not part of the server setup checklist.

Corrective action (book): configure log rotation on all servers and add it to the setup checklist. The book notes that the fix now prevents recurrence on every future server.

"Five" is a guide, not a rule. Stop when the answer is a cause someone can correct and correcting it would stop the problem returning. Sometimes that takes three whys; sometimes six.

Treating the symptom versus preventing recurrence

The power of the technique shows when you ask what would happen if you stopped early.

Stop atAction takenWhat happens next
Why 1: the disk was fullDelete old files to free spaceThe server runs, then the disk fills again
Why 4: rotation not configuredConfigure log rotation on this serverThis server is safe; other servers can still fail the same way
Why 5: not on the setup checklistConfigure rotation everywhere and update the checklistEvery current and future server is protected

Stopping at Why 1 treats the symptom: it is the fix from Lesson 12.1, and it will need repeating. Stopping at Why 4 solves this server's problem. Only Why 5 changes the process that produced the fault, which is why the book's corrective action has two parts.

A few habits keep a 5 Whys honest:

  • Base each answer on evidence, such as a log entry, a configuration file or a measurement, not on a guess. An answer you cannot support is a theory to test (Step 3 of the method).
  • Ask about the system, not the person. "Why did the administrator forget?" leads to blame; "Why was it not on the checklist?" leads to a fix.
  • Watch for branches. If a "why" has two genuine answers, you no longer have a single chain. That is the signal to use a fishbone diagram.

The fishbone (Ishikawa) diagram

When a problem may have several contributing causes, the book recommends a fishbone diagram, also called an Ishikawa diagram: a cause-and-effect diagram that groups possible causes by category. Its shape gives it the name:

  • The problem is written at the head of the fish.
  • A spine runs from the tail to the head.
  • The bones branching off the spine are categories. The book's categories are people, process, technology, network, environment and measurement.
  • The team brainstorms causes under each category, and then tests the most likely ones.

The book's Figure 12.1 draws a fishbone for the problem "Website slow for customers":

CategoryPossible causes in Figure 12.1
PeopleUntrained staff; large uploads
ProcessNo caching policy; backups at peak
TechnologyOld server; unoptimised database
NetworkNo CDN; ISP congestion
EnvironmentPower dips; server room heat
MeasurementWrong metric; no monitoring

A few terms: caching keeps copies of frequently requested content so that it can be served faster; a CDN (content delivery network) is a set of servers in different locations that serve a website's content from near the user; the ISP is the internet service provider.

Every item on the diagram is a possible cause, not a finding. The diagram's job is to make sure nothing obvious is missed, and to turn a vague complaint into a list of testable theories. That list then feeds the Step 2 and Step 3 loop of the seven-step method: rank the theories, test the most likely first, reject or confirm, and move on.

The measurement bone deserves a moment. "Wrong metric" and "no monitoring" mean the problem might not be measured correctly at all: perhaps the team watches server load while customers suffer from slow page loads. Before chasing a cause, make sure you are measuring the symptom that users actually experience.

Choosing the technique

The book's key takeaway gives the rule: use the 5 Whys for single chains of cause and the fishbone diagram when many factors may contribute. In practice they work together. A fishbone can identify the most likely cause (say, backups running at peak time), and a 5 Whys on that cause can then find its root (why were backups scheduled at peak? because nobody reviewed the schedule when trading hours changed).

Worked example

(fictional scenario, continuing Figure 12.1) The team behind the slow website ranks two theories from its fishbone. Theory 1, the old server: during slow periods the server's processor and memory are well within normal limits, so the theory is rejected. Theory 2, backups at peak: the slow periods match the nightly backup window exactly, which had been moved into customers' busiest hours. The theory is confirmed. A 5 Whys on Theory 2 finds that the backup schedule was never reviewed after the business started serving customers in another time zone. The corrective action is to move the backups and add a schedule review to the change process.

Try it

Draw a fishbone diagram on paper (or in any drawing tool) for the book's review problem: "Students cannot submit coursework online."

  1. Write the problem at the head.
  2. Draw the six bones: people, process, technology, network, environment, measurement.
  3. Add at least two possible causes under each category (for example, under people: students unaware of the file-size limit).
  4. Circle the two causes you would test first and write one test for each.

Completion criteria: a diagram with all six categories, at least twelve causes, and two ranked causes each with a concrete test.

Knowledge check

In the book's 5 Whys example, what is the answer to the fifth why?

Why does the book's corrective action include updating the setup checklist?

Which of these is one of the book's fishbone categories?

A problem seems to have several contributing causes across staff, equipment and procedures. Which technique does the book recommend?

Answers explained

  1. C. The chain runs: disk full, logs large, logs never deleted, rotation not configured, not on the setup checklist. The other options are the first, fourth and third answers.
  2. A. Adding rotation to the checklist protects every future server, which is what prevents recurrence. It does not free space immediately, it is not about speed, and the earlier answers were correct; they just were not deep enough.
  3. B. The book's six categories are people, process, technology, network, environment and measurement. The others are not in the book's list.
  4. D. The book uses the 5 Whys for a single chain and the fishbone when many factors may contribute. Half-split isolates a fault in a chain of components, and a factory reset is a phone repair step.

Key takeaways

  • The 5 Whys asks "why?" about each answer, usually about five times, until it reaches a cause that can be corrected.
  • Stopping early treats the symptom; the deepest actionable why prevents recurrence, often by fixing a process.
  • A fishbone diagram puts the problem at the head and groups possible causes under people, process, technology, network, environment and measurement; the most likely are then tested.
  • Use the 5 Whys for a single chain and the fishbone when many factors may contribute; they work well together.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §12.2–12.3, Figure 12.1, Key Takeaway and Review Question 3, Chapter 12; §3.2–3.3