Preventive Measures That Stop Recurrence
Where you are: Module 12 — Root Cause Analysis and Prevention · Lesson 12.3 · Based on Chapter 12 (§12.4) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Name the book's eight preventive measures and what each one prevents.
- Match a recurring problem to the preventive measure that removes its root cause.
- Justify a small set of preventive measures for a given organisation.
- Explain how documentation and prevention close the troubleshooting loop.
Watch: Preventive Measures That Stop Recurrence
The video starts with a small office's repeat tickets from the last quarter and asks which ones could have been prevented. It then walks through the book's eight preventive measures, matches each ticket to a measure, and shows how documentation, root cause analysis and prevention form a loop. Keep these questions in mind:
- Which measure stops a problem being noticed late, rather than stopping it happening?
- Why does the book say verified backups rather than just backups?
- Who needs to agree before a preventive measure is put in place?
Where prevention fits in the method
Prevention is not an extra stage added after the seven steps. It is already inside them. Step 6, verify full system functionality, includes implementing preventive measures where appropriate so that the problem does not return. Step 7, document, is how recurring problems are noticed in the first place. And the root cause analysis of Lessons 12.1 and 12.2 tells you what to prevent.
The book's key takeaway for Chapter 12 sums up the three levels: a workaround keeps people working; a fix removes the fault; a root-cause fix stops it coming back. Preventive measures are how root-cause fixes are made permanent.
The eight preventive measures
The book lists eight measures and what each one prevents.
| Measure | Prevents |
|---|---|
| Scheduled, tested updates | Security incidents and known bugs |
| Regular, verified backups | Permanent data loss |
| Monitoring and alerts | Unnoticed failures such as full disks or offline services |
| Standard configurations | Faults caused by inconsistent settings |
| Change management | Faults introduced by unplanned changes |
| Labelled cables and documented networks | Slow diagnosis and accidental disconnection |
| User training and clear guides | Repeated user errors |
| Clean, cool, protected equipment | Heat, dust and power-related failures |
Some of the wording rewards a closer look.
- Scheduled, tested updates. Chapter 10 showed that updates fix security problems and bugs but occasionally introduce new faults. Scheduled means they happen reliably; tested means a problem update is caught before it reaches everyone. The book is also clear that a system must never be left permanently unpatched as a workaround.
- Regular, verified backups. A backup that has never been restored, even as a test, may be incomplete or unreadable. Verification is what turns a backup into protection. This connects directly to the factory-reset rule in Lesson 11.2 and the failing-storage rule in Chapter 8: back up first.
- Monitoring and alerts. Monitoring does not stop a disk filling up; it makes sure someone knows before the server stops. In the book's server example, an alert on disk space would have turned an outage into a routine task.
- Standard configurations. When devices share a standard setup, faults caused by one odd setting disappear, and the comparison technique from Chapter 6 becomes much more powerful because there is a known-good reference.
- Change management. Change management is a controlled process for planning, approving and recording changes. Since Chapter 2 taught that most faults follow a recent change, controlling changes prevents faults and makes the "What changed?" question easy to answer.
- Labelled cables and documented networks. These speed up diagnosis and stop someone unplugging the wrong cable.
- User training and clear guides. The book's Chapter 3 worked example ended this way: a note added to the password-change guide reminded users to update their email clients.
- Clean, cool, protected equipment. Chapter 8 showed that heat causes slowness, shutdowns and component failure, often because dust blocks the vents; Chapter 1 lists heat, dust, moisture and power quality as environmental causes of faults.
Choosing measures
No organisation can do everything at once. A sensible choice links each measure to evidence:
- Which recurring problem or root cause does it remove? Start from your problem log (Chapter 13 and Appendix B), not from a wish list.
- What does it cost compared with the downtime it prevents? Chapter 1 described downtime as lost sales, idle staff, missed deadlines and damaged reputation.
- Who must approve it? Step 4 of the method requires approval where a change affects others or costs money.
- How will you know it works? Decide in advance what you will check, for example "no disk-full incidents for three months".
The book's Case Study 1 in Chapter 14 is a good model: after a power cut took the office offline, the team logged the incident and bought a small UPS (an uninterruptible power supply, a battery unit that keeps equipment running through short power cuts) for the modem and router. The measure matched the cause exactly.
The prevention loop
Documentation reveals the pattern, root cause analysis explains it, a preventive measure removes it, and monitoring confirms that it has gone. Then the cycle continues with the next pattern. This is how, in the book's words, individual effort becomes shared knowledge.
Worked example
(fictional scenario) A small accountancy office reviews its problem log for the last quarter and finds four repeat problems:
| Repeat problem | Root cause found | Preventive measure chosen |
|---|---|---|
| File server disk full, twice | Nobody watches free space | Monitoring and alerts at a set threshold |
| A spreadsheet lost; the backup could not be restored | Backups were never tested | Regular, verified backups, with a monthly restore test |
| Wrong cable unplugged during a desk move | Cables unlabelled | Labelled cables and a simple network diagram |
| Two laptops overheating | Used on soft surfaces; vents dusty | User guide on laptop use, and cleaning on a schedule |
The office manager approves the low-cost measures straight away and schedules the backup testing with the IT contractor. Three months later the log shows no repeats of the first three problems.
Try it
Answer the book's review question: choose three preventive measures for a small office and justify each.
- Describe a small office in two or three sentences (real or fictional).
- Choose three of the eight measures.
- For each, write: the problem it prevents in that office, what it would cost roughly in time or money, who would need to approve it, and how you would check that it works.
Completion criteria: three measures, each with all four points, and each linked to a specific problem in your office description.
Knowledge check
Which preventive measure most directly prevents faults introduced by unplanned changes?
Why does the book specify regular, verified backups?
A server's disk keeps filling up without anyone noticing until it stops. Which measure ensures the problem is noticed in time?
In which step of the seven-step method does the book place implementing preventive measures?
Answers explained
- C. The book pairs change management with faults introduced by unplanned changes. Training prevents user errors, monitoring catches unnoticed failures, and labels prevent accidental disconnection.
- A. Verification proves that a backup can actually be restored. It does not make backups faster, replace updates, or relate to deleting data.
- B. Monitoring and alerts prevent unnoticed failures such as full disks. Standard configurations, equipment care and training address different causes.
- D. The book's Step 6 includes implementing preventive measures where appropriate. Steps 2, 4 and 5 deal with theories, planning and applying the fix.
Key takeaways
- The book's eight measures: tested updates, verified backups, monitoring, standard configurations, change management, labelled and documented networks, user training, and clean, cool, protected equipment.
- Each measure targets a specific cause; choose measures from evidence in your problem log.
- Prevention sits inside the method: Step 6 adds preventive measures and Step 7's documentation reveals what needs preventing.
- Document, spot the pattern, find the root cause, prevent it, monitor: that loop is how an organisation learns.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §12.4, Key Takeaway and Review Question 4, Chapter 12; §1.4; §2.3; §3.4, §3.6–3.7 and worked example; §6.3; §8.4–8.5; §10.3; §13.5; Chapter 14 Case Study 1
