Common Mistakes and Cognitive Biases
Where you are: Module 2 — The Troubleshooting Mindset · Lesson 2.3 · Based on Chapter 2 (§2.4–2.5) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Recognise the six common troubleshooting mistakes described in the book and state the better practice for each.
- Define confirmation bias, anchoring, availability bias and sunk-cost thinking, and give an example of each.
- Choose a practical guard against each bias, and explain how treating ideas as theories protects against all four.
Watch: Common Mistakes and Cognitive Biases
The video examines a fictional email ticket that stayed open for three hours because a technician reinstalled an application twice while the real cause, an expired password, was written on the screen. It names the mistakes and biases at work at each moment and shows the theory-and-test loop that would have caught them. Keep these questions in mind:
- Where exactly did anchoring begin?
- Which piece of evidence was ignored, and why was it easy to ignore?
- What would a time limit have changed?
Six common mistakes
The book lists six mistakes that slow diagnosis or make problems worse. Each has a better practice.
| Mistake | Why it hurts | Better practice |
|---|---|---|
| Jumping to a fix | The wrong thing may be fixed, or a new fault created | Define the problem first (Module 4) |
| Ignoring error messages | The cause is often written on the screen | Record the exact text and code; search it |
| Changing many things at once | Cause and effect are lost | One change, then test |
| Assuming "it can't be that" | Simple causes are the most common | Check the basics anyway (Module 5) |
| Not asking what changed | Most faults follow a recent change | Ask specifically about recent changes |
| Working without notes | Attempts are repeated; others start from zero | Log every step and result |
Notice how closely these mirror the seven principles from Lesson 2.1. Each mistake is, in effect, a principle forgotten under pressure: jumping to a fix forgets curiosity; ignoring messages forgets observation; many changes forgets one-change-at-a-time; "it can't be that" forgets start simple; working without notes forgets write it down.
About error messages. When you record an error, copy it word for word, including any code (for example a number or a short code shown with the message), or take a screenshot or photograph. Search for the exact text in the vendor's documentation or knowledge base. Paraphrased errors ("something about the network") are much harder to research.
Cognitive biases
Mistakes are things we do. Behind many of them sit cognitive biases: predictable patterns in how human beings think that lead to wrong conclusions. The book is clear that even experienced technicians fall into them, and that awareness of these biases is the first defence against them.
Confirmation bias
Noticing only the evidence that supports the first theory and ignoring evidence against it.
Anchoring
Fixing on the first piece of information received, such as a user's own diagnosis.
Availability bias
Assuming the cause is whatever caused the last similar problem.
Sunk-cost thinking
Continuing with a failing approach because much time has already been invested in it.
Guards against each bias
| Bias | Practical guard |
|---|---|
| Confirmation bias | Look actively for evidence that would prove your theory wrong. Ask: "If I'm mistaken, what would I expect to see?" |
| Anchoring | Treat the user's diagnosis, or the first clue, as one theory among several. Write down at least two other possibilities. |
| Availability bias | Let this fault's evidence decide. "Last time it was X" is a reason to test X, not to assume it. |
| Sunk-cost thinking | Agree a time limit before you start. When it passes, step back, rethink or escalate. The book lists an expired time limit as a reason to escalate (Module 13). |
The deepest defence is the habit from principle 2: treat every idea as a theory to be tested, never as the answer. A theory that must survive a test cannot quietly become a belief. In Module 3 you will see this as the loop between Step 2 (establish a theory) and Step 3 (test the theory), which repeats until a cause is confirmed or the problem is escalated.
Treat every idea as a theory to be tested, and guard against the biases that make the first idea feel like the right one.
Worked example
(Fictional scenario.) A user calls the help desk at 09:00: "The email app is broken." The ticket stays open until noon.
| Time | What happened | Mistake or bias |
|---|---|---|
| 09:00 | The technician accepts "the app is broken" as fact. | Anchoring; jumping to a fix |
| 09:20 | "Last week's email fault was the app too." The app is reinstalled. | Availability bias |
| 10:15 | A message on screen says "Your password has expired"; the technician looks past it and reinstalls again. | Confirmation bias; ignoring error messages |
| 11:30 | "I've spent two hours on this; one more reinstall should do it." | Sunk-cost thinking |
| 11:55 | A colleague reads the screen. The password is reset through the organisation's approved process, and email works. | — |
How the theory-and-test habit would have helped:
- Theory 1: the email app is corrupt. Test: try webmail with the same account. Webmail also refuses to sign in, so the app cannot be the whole explanation. Rejected.
- Theory 2: the password has expired. Test: read the message and check the account status. Confirmed, in about five minutes.
Passwords and accounts. Never ask a user to tell you their password, and never share passwords during troubleshooting. Expired or locked accounts are handled through the organisation's approved reset process or by an administrator, using tools that do not expose credentials.
Try it
Bias spotting. For each short scenario below (fictional), name the bias or mistake and write the guard you would apply. Then write one scenario of your own for any bias.
- A user says, "It's definitely the Wi-Fi." The technician spends forty minutes on the router before checking that the laptop is in airplane mode.
- After fixing three printer jams caused by the wrong paper this week, a technician assumes a fourth jam is the paper too, and does not open the printer's error screen.
- A technician is convinced a driver is faulty. When a test on a second computer with the same driver works perfectly, they decide the test "doesn't count".
- A student has spent all evening reinstalling a program and refuses to try a different approach "after all this effort".
- A message box reads "Disk full", and the technician closes it to "get on with fixing it".
You have finished when all five scenarios have a named bias or mistake and a concrete guard, and your own scenario clearly shows one bias that a classmate could identify.
Knowledge check
A technician keeps noticing only the clues that support the first theory and dismisses the rest. Which bias is this?
A user opens with their own diagnosis, and the technician never considers anything else. Which bias is most clearly at work?
What is the better practice for the mistake of ignoring error messages?
Which guard is most effective against sunk-cost thinking?
Which statement best explains how treating every idea as a theory protects against all four biases?
Answers explained
- c — Filtering evidence to fit the first theory is confirmation bias. Anchoring is fixing on the first information received; availability is relying on the last similar case; sunk cost is persisting because of time invested.
- a — Fixing on the first information received, here the user's own diagnosis, is anchoring. Nothing suggests reliance on a previous case (B) or on time invested (C).
- b — The book's better practice is to record the exact text and code and search it. Restarting and reinstalling skip the evidence, and the user's interpretation is not a substitute for the exact message.
- d — A pre-agreed limit breaks the "too much invested to stop" trap and leads to rethinking or escalation. The other options feed the bias or another one.
- a — Requiring a test is what stops a first idea becoming a belief. Experience does not make theories correct (B), and notes and user conversations remain essential (C, D).
Key takeaways
- Six common mistakes: jumping to a fix, ignoring error messages, changing many things at once, assuming "it can't be that", not asking what changed, and working without notes.
- Each mistake has a better practice, and each mirrors a principle forgotten under pressure.
- Four cognitive biases can mislead anyone: confirmation bias, anchoring, availability bias and sunk-cost thinking. Awareness is the first defence.
- Treat every idea as a theory until a test confirms it, and set a time limit so effort already spent never decides what you do next.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §2.4–2.5; evidence collection from §4.3; escalation time limit from §13.1; security reminder from §10.4
