NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 3 — The Universal Seven-Step MethodologyLesson 2 of 4
Video lesson

Diagnose: Identify, Theorise, Test

BeginnerVideo lesson
9 min readBeginner

Where you are: Module 3 — The Universal Seven-Step Methodology · Lesson 3.2 · Based on Chapter 3 (§3.1–3.3) of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Gather the facts of a fault and turn them into a clear problem statement (Step 1).
  • Produce a ranked list of probable causes, simplest and most likely first (Step 2).
  • Design one small, safe test for a theory and act correctly on its result (Step 3).
  • Recognise when the diagnostic loop must end in escalation.

Watch: Diagnose: Identify, Theorise, Test

The video follows a fictional laptop that will not charge after its owner moves to a new desk. You will see the facts gathered, a problem statement written, four causes ranked and three of them tested in turn until one is confirmed. Keep these questions in mind:

  • Why is the battery theory never tested?
  • Which action in Step 1 protects the user's work, and why does it come first?
  • What would make a test "poor" even if it happened to give the right answer?

Step 1: Identify the problem

Step 1 is about gathering information before forming any opinion. The book asks you to establish:

  • what exactly is happening, and what should happen instead;
  • when it started;
  • who is affected;
  • what changed.

To answer these, use every source available: question the user, read error messages and logs, and try to reproduce the fault, which means making it happen on purpose so you can observe it.

Step 1 also contains a safety rule that is easy to overlook: back up data before going further if there is any risk to it. A laptop with a nearly flat battery, a disk making unusual noises, or an application that keeps crashing while a document is open are all situations where the first job is to secure the user's work.

The output of Step 1 is a clear problem statement: a specific, factual description of the problem that guides the rest of the diagnosis. Module 4 is devoted entirely to this step, including the 5W1H questions and the book's problem statement template.

Protect first, investigate second. If data is at risk, save or back it up before you test anything. If you suspect failing storage, stop unnecessary use of the device and escalate — every extra operation can make recovery harder.

Step 2: Establish a theory of probable cause

A theory of probable cause is a possible explanation that you intend to test. Step 2 asks for several of them, in order:

  • List the possible causes, the most likely and simplest first. The output is a ranked list, not a single guess.
  • Question the obvious. Is it plugged in, switched on, connected, logged in and up to date? These questions feel too simple, which is exactly why they are skipped — and why simple causes go undiscovered for hours.
  • Consider multiple approaches. You might work from the physical layer upwards (power, cables, hardware first) or from the application downwards (start with the program the user sees). Module 6 develops these as the bottom-up and top-down techniques.
  • Research the symptoms and error messages in vendor documentation and knowledge bases.

How do you rank? Two questions help. How likely is this cause, given the facts from Step 1? And how simple and cheap is it to check? A cause that is both likely and simple goes to the top. A cause that is possible but expensive or risky to check waits until the simple ones are ruled out. This is the Module 2 principle "start simple" put to work.

Avoid anchoring. If the user says "I think it's the battery", record it as one theory among several. Fixing on the first piece of information you receive is the anchoring bias described in Module 2.

Step 3: Test the theory to determine the cause

A test is a question you ask the system, not a repair. The book's instruction is precise: carry out one small, safe test that proves or disproves the theory. Then act on the result:

ResultWhat you do next
Theory confirmedMove on to Step 4 and plan the fix
Theory rejectedReturn to Step 2 and test the next most likely cause
All theories exhausted, or the problem is beyond your skill, access or authorityEscalate (Module 13)

What makes a good test

  • Small and safe. It should not put data, people or equipment at risk. Plugging a lamp into a power strip tests the strip; rewiring a socket is dangerous work for a qualified electrician, not a test.
  • One variable. It changes or checks one thing. If you swap the charger and the battery, a positive result cannot tell you which one mattered.
  • A trusted reference. When you substitute a part, it must be known-good — confirmed to work. A charger of unknown condition from a drawer proves nothing either way.
  • A clear expected result. Before you run it, say what you expect to see if the theory is true. Then the result is unambiguous.

Worked example

(Fictional scenario.) Omar's laptop shows 9% battery and "Not charging" although the charger is plugged in, and the charge light is off.

Step 1 — Identify. It started at 08:15 today and happens every time the charger is connected. Colleagues' laptops charge normally. Omar moved to desk 14 this morning. Because the battery is nearly flat, the technician's first action is to have Omar save and close his open work. Problem statement: since 08:15, Omar's laptop has not charged at desk 14.

Step 2 — Theory. Ranked list:

  1. The power strip at desk 14 is switched off — the simplest cause, made likely by the move.
  2. The charger cable is not fully seated in the laptop — it was unplugged during the move.
  3. The charger has failed — a common fault, and easy to check by swapping.
  4. The battery has failed — possible, but the least simple explanation.

Step 3 — Test, looping back as needed.

  • Theory 1: plug a desk lamp into the same strip. The lamp lights. Rejected.
  • Theory 2: unplug and firmly reseat the connector. Still no charge light. Rejected.
  • Theory 3: connect a known-good charger of the same model. The charge light comes on. Confirmed.

The fourth theory was never needed: testing in ranked order found the cause in three small steps without opening anything or buying parts. Steps 4 to 7 — planning the replacement, implementing it, verifying with Omar and documenting it — follow in Lesson 3.3.

Try it

Paper exercise. A user reports: "My wireless mouse stopped working after lunch. The keyboard is fine." For this scenario:

  1. Write three Step 1 questions you would ask before forming any theory.
  2. Write a ranked list of at least four probable causes, simplest and most likely first, and give a one-line reason for each position.
  3. For each theory, describe one small, safe test and say what result would confirm it and what would reject it.
  4. State the point at which you would stop and escalate.

Completion criteria: your list begins with simple, obvious causes (for example batteries or the receiver); each test changes or checks only one thing; any substituted part is described as known-good; your escalation point names skill, access, authority or exhausted theories.

Knowledge check

What is the output of Step 1, Identify the problem?

Which theory should normally be tested first?

Your theory is that a monitor cable is faulty. Which is the best test?

You have tested every theory on your list and none is confirmed. What should you do?

Why is a nearly flat battery relevant to Step 1 in the charging example?

Answers explained

  1. B — Step 1 ends with a clear problem statement. A is Step 2's output, C comes from Step 3 and D from Step 4.
  2. C — the book says to list the most likely and simplest causes first. Interest (A) and user certainty (B) are not ranking criteria, and slow checks (D) come later.
  3. D — it is small, safe, changes one thing and uses a known-good reference. A changes three things at once; B and C are fixes or delays, not tests.
  4. A — when theories are exhausted, Step 3 says escalate. B applies an unconfirmed fix, C wastes time, and D abandons a real fault.
  5. B — Step 1 says to back up or protect data if there is any risk. A low charge does not prove the battery has failed (A), nor does it say anything about the charger (D), and a problem statement is still needed (C).

Key takeaways

  • Step 1 gathers facts from the user, messages, logs and reproduction, protects data, and ends with a clear problem statement.
  • Step 2 produces a ranked list of causes, simplest and most likely first, after questioning the obvious.
  • Step 3 tests one theory at a time with one small, safe test that changes one variable.
  • A rejected theory sends you back to Step 2; exhausted theories or limits of skill, access or authority mean escalation.
  • No fix is applied until a theory is confirmed.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §3.1–3.3; cross-references to §2.2 (principles) and §2.5 (biases).