
Module 2 Checkpoint and Lab: The 'Nothing Changed' Interview
Where you are: Module 2 — The Troubleshooting Mindset · Checkpoint · Based on Chapter 2 of Dr. Tahseen Al Doori's Troubleshooting Essentials.
Recap
The right attitude solves half the problem before anything is touched: effective troubleshooters are calm, curious and methodical. The seven principles are: stay calm, be curious not certain, start simple, change one thing at a time, observe before acting, protect what matters, and write it down. "What changed?" is the most productive first question for any new problem, and when users say "nothing changed", specific questions recover the details. Change one variable at a time, or you cannot know which change fixed the fault. Avoid the six common mistakes, and guard against confirmation bias, anchoring, availability bias and sunk-cost thinking by treating every idea as a theory to be tested.
Checkpoint quiz
Which list gives the seven principles in the book's order?
A shared laptop stopped connecting to the projector on Tuesday. The user says nothing changed. Which question best applies the book's practitioner tip?
Which principle protects the user's data?
A technician has spent three hours on one theory and says one more attempt is justified because of the time already spent. Which bias is this, and what is the guard?
You change a cable and the fault remains. Following the one-change cycle, what do you do next?
Lab: The "Nothing Changed" Interview
Goal. Practise turning a vague report into specific evidence by interviewing a "user" who believes nothing changed, while applying the seven principles and avoiding the four biases.
Safe setup. A role-play for two or three people; no devices are touched or changed. If you are studying alone, play both parts in writing, or ask a friend or family member to play the user. Allow 40–60 minutes. Never use real passwords or personal data in the role-play.
Preparation (the user's role card). The person playing the user secretly chooses one hidden change from the list below, or invents a similar one, and writes it down. They must answer questions truthfully but only reveal the change if asked a question that specifically covers it. Their opening line is always: "It worked yesterday. Nothing changed. It just stopped."
- A wireless mouse stopped working after the user's child borrowed the laptop and switched on airplane mode.
- A home printer stopped printing after a power cut reset the router.
- An email app on a phone stopped syncing after the user changed their password on a computer.
- A smart TV lost its streaming app after an automatic overnight update.
- A desk phone went dead after the cleaners moved the desk and unplugged the cable.
Steps.
- Stay calm and listen (principle 1). The troubleshooter lets the user describe the problem fully, without interrupting, and notes the exact symptom in their own words.
- Observe before acting (principle 5). The troubleshooter asks what the user can see: messages, lights, sounds. Record answers word for word.
- Ask the general question once: "Did anything change before it started?" Record the answer.
- Ask at least six specific questions, including the book's four (installed or updated? moved or cleaned? power off? anyone else used it?) and at least two of your own drawn from the usual changes (passwords, location, new users).
- Name your theory, not your answer (principle 2). When a change emerges, state: "My theory is…". Then propose one single-change test that would confirm or reject it.
- Bias check. Before revealing the role card, the troubleshooter writes down which bias they were most at risk of during the interview and why.
- Reveal and debrief. The user reveals the hidden change. Swap roles and repeat with a different change.
What to record (use one sheet per round):
| Field | Entry |
|---|---|
| Symptom in the user's words | |
| Observations (messages, lights, sounds) | |
| Answer to the general question | |
| Specific questions asked and answers | |
| Question that revealed the change | |
| Theory, stated as a theory | |
| Single-change test proposed | |
| Bias most at risk, and why |
Completion criteria.
- At least two complete rounds recorded, with roles swapped.
- Each round shows at least six specific questions, and identifies which question revealed the change (or explains why none did).
- Each theory is phrased as a theory and paired with exactly one test.
- Each round includes a bias reflection naming one of the four biases.
- No passwords or personal data were requested or recorded.
Safety and privacy. This lab is a conversation, not a repair. Do not change settings on anyone's device. Never ask anyone to tell you a password; in real life, account problems are resolved through the approved reset process.
Answers explained
- b — This is the book's order. The other options contain the right principles in the wrong sequence.
- d — "Has anyone else used it?" is one of the book's specific questions and fits a shared laptop. A repeats the general question, B jumps to a fix, and C invites anchoring on the user's diagnosis.
- a — Protect what matters means backing up data and recording settings before any change. The other principles do not directly safeguard data.
- c — Persisting because of time already invested is sunk-cost thinking; a time limit with a step back or escalation is the guard. The other pairs mismatch the bias, and their "guards" would make things worse.
- a — The one-change cycle undoes an unhelpful change before the next single change. B makes several changes at once; C abandons the problem without testing other theories or escalating.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 2 (§2.1–2.5), practitioner tip and review questions; security reminder from §10.4
