
Module 12 Checkpoint and Lab: Five Whys on a Battery
Where you are: Module 12 — Root Cause Analysis and Prevention · Checkpoint · Based on Chapter 12 of Dr. Tahseen Al Doori's Troubleshooting Essentials.
Recap
Module 12 moved from solving a problem to stopping it coming back. A symptom is what you see, a workaround keeps people working, a fix corrects the immediate fault, and a root cause is why the fault happens. The 5 Whys follows a single chain of cause, usually about five questions deep, to a cause that can be corrected; the fishbone diagram groups many possible causes under people, process, technology, network, environment and measurement, so the likeliest can be tested. The book's eight preventive measures, from verified backups to change management, make root-cause fixes permanent.
Knowledge check
A fix that addresses only the symptom has one predictable consequence. What is it?
In a 5 Whys analysis, when should you stop asking why?
A team suspects that slow customer orders have causes in staff training, procedures, software and the warehouse temperature. Which tool fits best?
Which pair is correct according to the book's preventive measures table?
A shop's till freezes every afternoon and staff restart it each time. The restart works. What is the best description of the situation?
Answers explained
- A. The book states that a fix addressing only the symptom will need repeating. It does not always make things worse, require escalation, or remove the root cause.
- C. "Five" is a guide: stop at the deepest cause that can be corrected. A fixed count, blame or the first working fix are not the test.
- B. Several contributing factors across categories call for a fishbone diagram; the 5 Whys suits a single chain. Half-split and the connectivity test isolate faults along a path.
- D. The book pairs standard configurations with faults caused by inconsistent settings. Labels prevent slow diagnosis and accidental disconnection; change management prevents faults from unplanned changes; training prevents repeated user errors.
- C. A repeated restart is a workaround; the freezing is the symptom, and the cause (for example a memory leak or overheating, as Chapter 5 suggests) must still be found.
Lab: Five Whys on a Battery
Goal: apply the 5 Whys to the book's review problem, "A laptop battery runs out by midday", reach an actionable root cause, and propose a corrective action and a preventive measure.
Safe setup: this is a paper and observation exercise. You may use a laptop you are allowed to use to gather evidence, but change nothing except, at the end, a setting you agree with its owner. Do not open the laptop or remove its battery.
Safety: if the laptop's case is bulging, the keyboard or touchpad is lifting, or the battery is unusually hot or smells, stop. A swollen battery is a safety escalation (book Chapter 13), not a root cause exercise. Switch off at the source if it is safe to do so and hand it to someone qualified.
Steps:
- Write the problem statement (Chapter 4 template), for example: "Since [when], [who]'s laptop battery runs from full to empty by about midday on a normal working day. The most recent change was [which]."
- Gather evidence before asking why. Possible sources: the battery-use list in the operating system, the screen brightness, which apps run all day, whether the laptop was charged fully overnight, the battery's age, and any recent changes (Chapter 2: "What changed?").
- Ask the first why about the problem statement and answer it with evidence, not a guess.
- Keep asking why about each answer, usually about five times, until you reach a cause that can be corrected and whose correction would stop the problem returning.
- Check for branches. If one why has two genuine answers (for example, an app draining power and a worn battery), note both. If several factors appear, sketch a short fishbone diagram with the book's six categories.
- Write the corrective action for the root cause, and choose one preventive measure from the book's table that would stop it recurring for other users.
Example chain (fictional, to show the format only; your evidence decides your chain): Why does the battery run out by midday? A video-calling app uses a lot of power all morning. Why? It runs in the background from startup, even when no call is active. Why? It was set to start automatically and keep running when it was installed last month. Why was that not changed? The laptop setup guide does not cover background app settings. Corrective action: change the app's background setting and add background-app checks to the setup guide (preventive measure: user training and clear guides, or standard configurations).
Beyond the book (2026 note): On Windows 11 (version 24H2 or later), Microsoft's battery guidance shows which apps may be using more battery in the background under Settings > System > Power & battery > Battery usage, in the Battery usage per app list, and energy saver is turned on from Settings > System > Power & battery. Source: Microsoft Support, "Battery saving tips for Windows" (link below). Other operating systems have equivalent battery-use views; check the vendor's documentation.
What to record: the problem statement; each why with its answer and the evidence for it; any branches; the root cause; the corrective action; the preventive measure and why you chose it; and what you would check over the next week to verify that the battery now lasts.
Completion criteria: a complete chain of at least three whys, each answer supported by evidence or clearly marked as a theory to test; a root cause that can be acted on; a corrective action; one preventive measure from the book's table, justified; and a verification check.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 12 (§12.1–12.4, Key Takeaway, Review Questions 2 and 3); §2.3; §4.6; §5.6; §13.1
- Microsoft Support — Battery saving tips for Windows
