NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 4 — Identifying and Defining the ProblemLesson 4 of 4
6 min readBeginner

Where you are: Module 4 — Identifying and Defining the Problem · Checkpoint and Lab · Based on Chapter 4 of Dr. Tahseen Al Doori's Troubleshooting Essentials.

Recap

Module 4 expanded Step 1 of the method. The 5W1H questions — What, When, Where, Who, Which (which changes happened just before) and How — structure information gathering. Users are the primary source, so listen, avoid jargon, ask open questions before closed ones, and ask them to demonstrate the problem. Collect five kinds of evidence: exact error messages, physical symptoms, logs and history, scope, and recent changes. A fault you can reproduce — same steps, device and account — is quick to test; an intermittent fault needs an occurrence log until a pattern appears. A baseline of normal behaviour makes abnormal behaviour visible. Finally, combine everything into a specific, factual, testable problem statement before attempting any fix.

Knowledge check

Which list gives the author's 5W1H questions?

A user insists the fault is 'definitely the Wi-Fi'. What is the best response?

A projector fails only in Room 4, and only some afternoons. Which technique fits best?

What does a baseline allow you to do?

Which statement follows the book's template most closely?

Answers explained

  1. B — the author uses Which (which changes happened just before), not Why. C and D replace real questions with invented ones.
  2. A — the user's theory is information, not the diagnosis (avoiding anchoring). B is an untested fix, C damages trust, and D puts a guess in the problem statement.
  3. D — intermittent faults need an occurrence log so a pattern can emerge. A guesses, B skips open questions, and C stops gathering evidence too early.
  4. C — a baseline records normal behaviour for comparison. Rollback (A), escalation (B) and reproduction (D) are different techniques.
  5. A — it gives when, who, what, how and which, all factual. B and C contain guessed causes or fixes; D is vague.

Lab: Rewrite the report

Goal

Turn vague reports into professional problem statements by gathering facts with 5W1H, separating evidence from guesses, and applying the book's template.

Safe setup

This is a paper or role-play exercise: no device is changed. Work with a partner if you can (one plays the user, one the technician), or alone using the written material below. If you role-play, the "user" invents details freely — but never uses or asks for a real password or real personal data.

Steps

Part A — Interview transcript (fictional scenario)

Read this transcript between a technician (T) and a user, Daniel (D):

Example prompt

T: What were you doing when it happened? D: Trying to open the sales report from the shared drive, like every Thursday. It's just broken. T: What did you see on the screen? D: A box saying Windows cannot access the share, with some code. I closed it. T: When did this start? D: This morning, about nine. Last Thursday it was fine. T: Does it happen every time? D: Every time I try, yes. T: Can your colleagues open the report? D: Priya can, from her desk. I'm the only one complaining. T: Has anything changed on your laptop recently? D: IT installed updates last night, and I've been working from the meeting room since yesterday. T: Could you show me? D: (The same message appears: "Windows cannot access \\SALES01\Reports — Error code: 0x80070035 — The network path was not found.")

  1. Fill in a 5W1H table from the transcript. Mark any row where the transcript gives two possible answers.
  2. List every piece of evidence in the transcript under the five headings: exact error message, physical symptoms, logs and history, scope, recent changes. Write "not yet collected" where nothing is available, and note one piece of evidence you would collect next.
  3. Underline the user's own theory or opinion ("It's just broken") and explain in one sentence why it does not belong in the problem statement.
  4. Write the problem statement using the book's template.

Part B — Rewrite three reports

For each vague report below, invent reasonable details (label them fictional), complete a 5W1H table, and write a full problem statement:

  1. "The internet is broken."
  2. "My phone keeps doing that thing again."
  3. "The projector in the lecture theatre hates my laptop."

Part C — Intermittent fault

Report 2 above happens only now and then. Design a one-week occurrence log for it: the columns you would use, and three example entries that would help reveal a pattern.

What to record

  • Part A: the 5W1H table, the evidence list (with "not yet collected" entries), the one-sentence explanation, and the problem statement.
  • Part B: three 5W1H tables and three problem statements.
  • Part C: the occurrence log design with three entries.

Completion criteria

  • Every 5W1H table has all six rows filled, including Which.
  • Every problem statement fills each slot of the template, contains no guessed cause or fix, and is no more than two short sentences (the template's follow-on sentences may be combined).
  • Part A's statement uses the exact error message, and notes that two recent changes (updates and a new location) are candidates for the Which slot.
  • Part C's log includes date, time, activity and conditions.
  • If working in pairs, each partner reviews the other's statements against the "specific, factual, testable" test and suggests one improvement.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 4 (§4.1–4.6, Figure 4.1, Problem Statement Template, Key Takeaway, Chapter Summary and Review Questions).