The 5W1H Questions and Interviewing Users
Where you are: Module 4 — Identifying and Defining the Problem · Lesson 4.1 · Based on Chapter 4 (introduction, Figure 4.1, §4.1–4.2) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- State the six 5W1H questions — What, When, Where, Who, Which, How — and the purpose of each.
- Use 5W1H to turn a vague report into organised facts.
- Explain why open questions are asked before closed questions, and give examples of each.
- Use a user's demonstration of a problem as a source of evidence.
Watch: The 5W1H Questions and Interviewing Users
The video introduces the six questions with the book's printer example, then follows a short, fictional interview with Lena, a receptionist whose booking screen will not load. Keep these questions in mind:
- Why does the author's sixth question begin with Which rather than Why?
- Which detail did the technician learn only by watching Lena, not by listening to her?
- How do the interview answers map onto the six questions?
A problem well defined is half solved
The book opens Chapter 4 with a contrast. "It doesn't work" cannot be fixed, because nobody knows what "it" is or what "work" means. A report that names the application, the device, the symptom, when it started and what still works "almost fixes itself". Module 4 expands Step 1, Identify the problem, into a set of practical techniques, and the first of them is a structured set of questions.
The 5W1H questions
5W1H stands for What, When, Where, Who, Which and How: six questions that together define a problem. In the book's Figure 4.1 they sit around a single centre — the problem statement — because every answer feeds that one sentence.
| Question | Ask | The book's example answer (a printer) |
|---|---|---|
| What | What exactly happens? What should happen instead? | The printer produces blank pages instead of invoices |
| When | When did it start? Always or sometimes? | Since Monday, on every print job |
| Where | Which device, room, site, network or application? | Only the second-floor printer |
| Who | Who is affected: one person, a team, everyone? | Every user of that printer |
| Which | Which changes happened just before? | The toner cartridge was replaced on Monday |
| How | How is it triggered? Can it be repeated? | Printing any page produces a blank sheet |
Read the example answers together and the problem almost explains itself: a fault that began on the day of a cartridge change, affects everyone using one printer, and happens on every page points strongly towards the new cartridge. Yet no theory has been formed yet — the questions have simply organised the facts.
What each question does
- What needs both halves: the symptom and the expected behaviour. "Blank pages" is only meaningful next to "invoices should print".
- When separates permanent faults from intermittent ones, and gives a start time to compare with changes and logs.
- Where fixes the location: one device, one room, one application.
- Who sets the scope. One person suggests their device, account or settings; everyone suggests shared equipment or services.
- Which asks for the changes that happened just before. It connects directly to Module 2's most powerful question, "What changed?"
- How establishes the trigger and whether the fault can be repeated, which Lesson 4.2 develops as reproduction.
The author's sixth W is Which — which changes happened just before? Keep it. It keeps you gathering facts about recent changes, the most common trigger of new faults, instead of jumping to "why" before the evidence is in.
Questioning the user
Users are the primary source of information, but the book notes two complications: they describe problems in their own words, and they may already have a theory. A user who says "the Wi-Fi is broken" may be describing a website that is down. Record their theory as one possibility; do not adopt it as the diagnosis (the anchoring bias from Module 2).
The book's guidance for the conversation:
- Listen carefully. Let the user finish before you start diagnosing.
- Avoid technical jargon. A user who does not understand a question will guess at the answer.
- Ask open questions first, then closed questions.
- Ask the user to demonstrate the problem where possible.
Open and closed questions
An open question invites a full answer in the user's own words. A closed question can be answered with yes, no or a single fact.
| Type | Example | What it gives you |
|---|---|---|
| Open | "What were you doing when it happened?" | The story and its context |
| Open | "What did you see on the screen?" | Details you did not think to ask about |
| Closed | "Did you see an error message?" | A definite yes or no |
| Closed | "Has this happened before today?" | A specific fact to record |
Why open first? Closed questions steer. If your first question is "Did you restart it?", you have already pointed the conversation at one theory, and the user may stop telling you things that do not fit it. Open questions let the user describe the whole situation; closed questions then pin down the facts you still need.
Watching beats listening
Asking the user to demonstrate the problem is one of the most productive moves in Step 1. Watching it happen often reveals details the user would never think to mention: a warning icon, an unusual sequence of clicks, a different account, an error that flashes and disappears.
Never ask a user to tell you their password, even to "save time" while they demonstrate. If a login is part of the problem, let the user type it themselves, or use your organisation's approved reset process.
Worked example
(Fictional scenario.) Lena, a receptionist, reports: "The booking screen won't load."
The interview.
- Open: "What were you doing when it happened?" — "Opening the booking system, as I do every morning."
- Open: "What did you see on the screen?" — "A message about not being able to reach the site."
- Closed: "Has it ever worked at this desk?" — "No."
- Closed: "Was anything moved or changed recently?" — "My PC was moved to this desk yesterday afternoon."
- Request: "Could you show me what happens?"
The demonstration. Lena opens the booking page: the browser shows "This site can't be reached". The technician also notices that the network icon shows no connection at all — something Lena had not mentioned. She tries a second browser, with the same result.
Organised with 5W1H.
| Question | Answer |
|---|---|
| What | The booking page shows "This site can't be reached" instead of the booking system |
| When | Since 08:00 today, on every attempt |
| Where | The reception PC, at its new desk |
| Who | Lena only; colleagues' PCs work normally |
| Which | The PC was moved to a new desk yesterday |
| How | Opening the page in any browser |
No theory has been tested yet, but the search area has shrunk dramatically. In Lesson 4.3 you will turn this table into a formal problem statement.
Try it
Role-play or paper exercise. Working with a partner (or writing both parts yourself), take this vague report: "My laptop is being weird."
- Write three open questions you would ask first.
- Invent plausible user answers.
- Write three closed questions that pin down the remaining facts.
- Describe what you would ask the user to demonstrate.
- Fill in a 5W1H table from the answers.
Completion criteria: your first three questions are genuinely open (they cannot be answered yes or no); every row of the 5W1H table is filled, including Which; at no point does your script ask for a password; you have not written a theory or a fix.
Knowledge check
In the author's 5W1H, what does the question Which ask?
Which of these is an open question?
Why should open questions come before closed questions?
A fault affects every user of one shared printer. Which 5W1H answer tells you this?
During a demonstration, the technician notices a warning icon the user never mentioned. What does this illustrate?
Answers explained
- B — the author's Which asks which changes happened just before. A, C and D are not part of 5W1H, and D jumps to fixes.
- A — it invites a full answer. B, C and D can each be answered yes or no, so they are closed.
- D — open questions let the user describe everything before closed questions narrow the conversation. Closed questions are allowed and useful (C), just second; speed and politeness (A, B) are not the reason.
- C — Who sets the scope: one person, a team or everyone. What, When and How describe the symptom, timing and trigger.
- B — this is exactly why the book recommends demonstrations. It does not imply deliberate hiding (A), it does not replace questions (C), and a warning icon is evidence, not proof of cause (D).
Key takeaways
- 5W1H — What, When, Where, Who, Which, How — structures information gathering and feeds a single problem statement.
- The author's sixth question is Which: which changes happened just before?
- Users are the primary source, but describe problems in their own words and may already have a theory.
- Listen, avoid jargon, ask open questions before closed ones, and never ask for a password.
- Ask the user to demonstrate: watching often reveals what nobody thought to say.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 4 introduction, Figure 4.1, §4.1–4.2; cross-references to §2.3, §2.5 and §10.4 (security reminder).
