Symptoms, Workarounds, Fixes and Root Causes
Where you are: Module 12 — Root Cause Analysis and Prevention · Lesson 12.1 · Based on Chapter 12 (§12.1) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Define and distinguish a symptom, a workaround, a fix and a root cause.
- Classify actions in a real ticket using the four terms.
- Explain why a fix that addresses only the symptom will need repeating.
- Judge whether an investigation has reached a root cause that can be acted on.
Watch: Symptoms, Workarounds, Fixes and Root Causes
The video uses the book's server example: a server that keeps stopping, a restart every morning, and a clean-up that frees disk space. It shows each action at a different depth and asks which one stops the problem coming back. Keep these questions in mind:
- Is a workaround a failure, or does it have a proper place?
- What is the difference between a fix and a root-cause fix?
- How do you know when to stop digging?
Four words that sound alike
Every troubleshooter has had the experience: a problem is "solved", the ticket is closed, and a week later the same problem is back. Usually the problem was never solved; only its effect was removed. Chapter 12 gives four precise terms that prevent this confusion. Here they are with the book's own example, a server that stops responding.
| Term | Meaning | Book's example |
|---|---|---|
| Symptom | What is observed going wrong | The server stops responding |
| Workaround | A temporary way to keep working | Restarting the server each morning |
| Fix | Correction of the immediate fault | Deleting old files to free disk space |
| Root cause | The underlying reason the fault occurs | Log files grow without limit because log rotation was never configured |
Log files are records that programs write about what they are doing. Log rotation is the routine of closing a log after a time or size limit, starting a new one and deleting the oldest, so that logs never fill the disk.
Read the table from top to bottom and you go deeper with each row:
- The symptom is where every investigation starts. It is real, but it is an effect, not a cause.
- The workaround keeps people working. Restarting the server each morning gets the business through the day, but nothing about the fault has changed.
- The fix corrects the immediate fault. Deleting old files frees disk space and the server runs again, until the logs fill the disk once more.
- The root cause explains why the fault happens at all. Configure log rotation and the disk stops filling.
The book puts it in one sentence: a fix that addresses only the symptom will need repeating. Root cause analysis finds the deepest cause that can be acted on, so the problem does not return.
Workarounds have a place
A workaround is not a mistake. When a business service is down, keeping people working is often the right first move, and the cost of downtime from Chapter 1 (lost sales, idle staff, missed deadlines) may make it urgent. The danger is forgetting that it is temporary.
You met this idea in Module 5: a restart treats the symptom rather than the cause, and if the same problem needs repeated restarts, the troubleshooter must keep looking for the underlying cause, such as a memory leak, a failing driver or an overheating component. The book's key takeaway for Chapter 5 says it plainly: if a quick win has to be repeated, it is a workaround, not a fix.
Good practice with workarounds:
- Label it. Record in the ticket that the action is a workaround.
- Keep the ticket, or a follow-up task, open until the root cause is found.
- Tell the user that the problem may return and that work is continuing (Chapter 13, setting realistic expectations).
When have you reached the root cause?
"Root cause" does not mean "the first cause in history". You could keep asking why for ever. The book's phrase gives the stopping rule: the deepest cause that can be acted on. Three practical questions help you judge it:
- Can someone act on it? "Disks are finite" is true but useless. "Log rotation was not configured" is something an administrator can change.
- Would acting on it stop recurrence? Configuring log rotation stops the disk filling with logs; deleting files does not.
- Does acting on it protect other systems too? In the book's full analysis (next lesson), the deepest answer is that log rotation was not part of the server setup checklist. Fixing the checklist protects every future server, not just this one.
Notice that the strongest root causes are often about process, not people or parts: a missing checklist step, an unclear procedure or a missing standard. This matches the book's problem categories in Chapter 1, where "user and process" problems are caused by training gaps and unclear procedures. Treat a root cause as something to improve, not someone to blame.
Worked example
(fictional scenario) A shared reception PC freezes most afternoons. For two weeks, staff have restarted it whenever it freezes.
- Symptom: the PC freezes in the afternoon.
- Workaround: restarting it each time. It works, which is why nobody investigated.
- Investigation: Task Manager (Chapter 7) shows the memory used by the booking application climbing steadily through the day until the PC runs out of memory. The vendor's release notes for a newer version list a memory fault.
- Fix: update the booking application. The freezes stop.
- Root cause: the PC had been left out of the office's update schedule when it was moved to reception, so it never received the corrected version.
- Root-cause action: add the PC to the update schedule and add "join the update schedule" to the checklist for moving or setting up machines.
Without the root-cause action, the next application fault would have repeated the whole story.
Try it
For each item below, decide whether it is a symptom, a workaround, a fix or a root cause. Then write one sentence explaining your choice.
- "Users print to the second-floor printer instead, while the first-floor printer is out of action."
- "The office Wi-Fi drops several times a day."
- "The access point was installed beside the kitchen wall, where a microwave interferes." (adapted from the book's Case Study 3)
- "A full disk is cleared by deleting old downloads."
- "During lunchtime, staff move to the next room, where the Wi-Fi is reliable."
Completion criteria: five classifications with reasons. Suggested answers: 1 workaround, 2 symptom, 3 root cause, 4 fix, 5 workaround. For item 3, also ask one more "why?": why was the access point placed there? If the answer is a process gap (for example, no site check before installing access points), that deeper cause may be the better one to act on.
Knowledge check
A server stops responding. Restarting it each morning keeps it running. What is the restart?
Deleting old files frees disk space and the server runs again, but the disk fills up a month later. Why did the problem return?
Which statement best describes a root cause in the book's sense?
A laptop needs a restart every day to stay usable. According to the book, what should the troubleshooter do?
Answers explained
- B. A restart is a temporary way to keep working; the book's own example of a workaround. It is not the symptom (the server stopping), a fix (freeing space) or the root cause (no log rotation).
- A. Deleting files corrects the immediate fault, but nothing stops logs growing, so the disk fills again. The order of deletion is irrelevant, workarounds are not always harmful, and the symptom was correct.
- C. The book defines root cause analysis as finding the deepest cause that can be acted on. History, the user's belief and cost are not the test.
- D. Chapter 5 says repeated restarts mean a workaround, and the underlying cause, such as a memory leak, a failing driver or overheating, must still be found. Closing the ticket, replacing hardware blindly or disabling restarts skips the investigation.
Key takeaways
- A symptom is what you see; a workaround keeps people working; a fix corrects the immediate fault; a root cause is why the fault happens.
- A fix that addresses only the symptom will need repeating.
- Workarounds are legitimate, but label them, keep the ticket open and tell the user.
- Stop digging at the deepest cause that can be acted on; the best ones often fix a process and protect future systems.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §12.1–12.2 and Key Takeaway, Chapter 12; §1.3–1.4; §5.6 and Key Takeaway, Chapter 5; §7.1; §13.4; Chapter 14 Case Study 3
