
Module 3 Checkpoint and Lab: Seven Steps with a Partner
Where you are: Module 3 — The Universal Seven-Step Methodology · Checkpoint and Lab · Based on Chapter 3 of Dr. Tahseen Al Doori's Troubleshooting Essentials, including the Chapter 3 lab exercise.
Recap
Every problem is solved with the same seven steps: identify the problem, establish a theory of probable cause, test the theory, establish a plan of action, implement the solution or escalate, verify full system functionality, and document findings, actions and outcomes. Steps 1–3 diagnose; Steps 4–7 resolve and capture what was learned. Steps 2 and 3 loop until a theory is confirmed or the problem is escalated, and no fix is applied before then. A plan protects data and always includes a way to undo the change. Verification repeats the failing action, checks related functions and ends with the user's confirmation. Documentation turns one fix into shared knowledge.
Knowledge check
Which step's key question is 'How will it be fixed safely?'
What ends the loop between Step 2 and Step 3?
A technician confirms a faulty network cable and immediately swaps it, without recording anything. Which step was skipped before the change?
A printer driver update fixes the printing fault. Which action best completes Step 6?
Why does Step 7 matter after a fault has already been fixed?
Answers explained
- D — "How will it be fixed safely?" is Step 4's key question, answered with steps, a backup and a rollback plan. Step 2 asks what could cause this, Step 5 whether the plan was applied carefully, Step 6 whether everything works now.
- A — Figure 3.1 shows only two exits: confirmation (to Step 4) or escalation. Patience, a fixed number of tests and a restart do not end the loop.
- B — the cause was confirmed (Steps 1–3 done), but the change was made with no plan: no recorded settings, no rollback, no consideration of impact.
- C — Step 6 repeats the original action, checks related functions and gets the user's confirmation. A and D skip verification; B makes extra unplanned changes.
- B — these are the three purposes the book gives for documentation. It never replaces verification (C), and it is not limited to costly faults (A).
Lab: Seven steps with a partner
This lab adapts the book's Chapter 3 lab exercise. One person creates a small, harmless fault; the other diagnoses it using all seven steps and records each step on the problem log.
Goal
Apply the complete seven-step method to a real (deliberately introduced) fault, including at least one pass around the Step 2 ↔ Step 3 loop, and record the work on the problem log template.
Safe setup
- Use a training device, a spare device, or your own device only for a fault that is non-critical and instantly reversible.
- Allowed faults: disconnect one non-critical cable (for example a mouse, speaker or second monitor cable) or disable one setting (for example Wi-Fi, Bluetooth, mute, or the selected audio output).
- Not allowed: anything involving mains wiring or opening equipment, deleting files, uninstalling software, changing administrator, security or account settings, firmware, or passwords. Never share or ask for a password.
- The person who creates the fault writes it down privately before the lab starts, together with how to reverse it, and checks at the end that the device is fully restored.
Working alone or online? Ask a friend or family member to introduce the fault on their own device while you guide them by phone or video call, or ask your instructor for a written fault scenario and complete the log as a simulation.
Roles
- Fault setter: introduces one fault, acts as the user, answers questions honestly but only what is asked, and confirms (or does not confirm) the fix in Step 6.
- Troubleshooter: follows the seven steps in order and records every step on the problem log. Then swap roles and repeat with a different fault.
Steps
- Fault setter: privately record the fault and its reversal, then introduce it while the troubleshooter is out of sight.
- Identify: the troubleshooter questions the "user", observes the symptom, tries to reproduce it, checks whether any data is at risk, and writes a one-sentence problem statement.
- Theory: write a ranked list of at least three probable causes, simplest and most likely first.
- Test: test the theories one at a time, recording each test and its result. Return to Step 2 after each rejected theory. If no theory is confirmed within 15 minutes, escalate to your instructor with your notes.
- Plan: before changing anything, write what will change, what could go wrong, how it will be undone, and whether any data needs protecting.
- Implement: make the single planned change.
- Verify: repeat the action that failed, check one related function, and ask the fault setter to confirm.
- Document: complete the problem log. The fault setter then compares the log with their private note and checks the device is fully restored.
What to record: problem log (book Appendix B)
| Field | Entry |
|---|---|
| Reference number | |
| Date and time reported | |
| Reported by / contact | |
| Device, system and location | |
| Problem statement | |
| Exact error message | |
| Recent changes | |
| Theories tested and results | |
| Root cause | |
| Solution applied | |
| Verified by (user) and date | |
| Preventive measures | |
| Time spent / escalated to |
Completion criteria
- Every field of the problem log is completed (write "none" where a field genuinely does not apply).
- The problem statement is specific and was written before any theory was tested.
- At least one theory was rejected and the log shows the return to Step 2 — or, if your first theory was confirmed, you explain in one sentence why it was ranked first.
- A plan with a rollback was written before the change was made.
- The fault setter confirmed the fix, and the device was restored to its original state.
- Both partners completed the troubleshooter role with different faults.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 3 (§3.1–3.8, Figure 3.1, Key Takeaway, Lab Exercise, Chapter Summary) and Appendix B (Problem Log Template).
