Two techniques that turn a pleasant chat into evidence: the TEDW structure for eliciting specifics, and the 5 Whys for drilling past symptoms to root causes.
▸ Try the interactive toolAdvanced User Interviews build on Module 1's interview basics by adding two analytical frameworks: the TEDW question structure (Tell me, Example, Describe, Walk me through) and the 5 Whys root-cause technique. Together they transform an interview from a pleasant conversation that produces opinions into a structured session that produces evidence.
TEDW is a sequence of question types that reliably pull users from generalities down to specific, observable detail — “tell me about…” opens, then “give me an example,” “describe what happened,” “walk me through it.” The 5 Whys repeatedly asks why to drill past a stated symptom to the underlying cause. Both fight the interview's natural drift toward vague, rationalised, in-the-moment answers and toward the surface explanation that isn't the real one.
TEDW — Tell me about… / give an Example / Describe what happened / Walk me through it (general → specific)
5 Whys — ask “why?” repeatedly (about five times) to move from symptom to root cause
A basic interview gets you opinions and generalities; the advanced techniques get you specific behaviour and the real reason behind it.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Generalities, not specifics | “I usually…” answers that flatter rather than inform. | TEDW pulls users down to a specific, real episode. |
| Stopping at the symptom | The first answer is rarely the root cause. | The 5 Whys drills past the surface to the underlying driver. |
| Accepting rationalisations | Users explain behaviour with tidy after-the-fact stories. | Specific walk-throughs reveal what actually happened, not the story. |
| Unstructured drift | An aimless chat produces unusable, unsystematic notes. | TEDW gives the conversation a repeatable structure that yields evidence. |
Start broad and let the user talk. This surfaces the territory and the episodes worth drilling into, without leading.
Move from the general to one real instance: “can you give me a specific example of the last time that happened?” Specifics are evidence; generalities are opinion.
Ask them to describe what happened and walk you through it step by step. The granular replay reveals friction and workarounds the summary skipped.
When you hit a significant behaviour or frustration, ask why — and keep asking, roughly five times. Each why peels back a layer toward the root cause.
Throughout, talk little, never pitch, and let silence do the work. The advanced structure only helps if you're not contaminating the answers.
An interviewer asked why a user had abandoned a workflow and got a tidy answer: “it was too slow.” A basic interview would have stopped there and logged “speed” as the problem. Instead they applied the 5 Whys.
Why was slowness a dealbreaker? Because they did it under time pressure. Why the pressure? Because it happened right before a recurring deadline. Why then? Because the tool didn't let them prepare it in advance. The real root cause wasn't speed at all — it was the inability to do the work ahead of time, a completely different (and more solvable) problem than the surface “too slow.”
The deliverable is interview notes organised by episode, with root causes surfaced via the 5 Whys — evidence, not a transcript of opinions.
| Technique | Moves the user from… | …to |
|---|---|---|
| Tell me about | Cold start | The territory worth exploring |
| Example | Generalities | One specific real instance |
| Describe / Walk through | Summary | Granular, observable detail |
| 5 Whys | Stated symptom | Underlying root cause |
What people say in a basic interview is opinion; what these techniques extract is evidence. TEDW gets you to a specific real episode, and the 5 Whys gets you past its surface explanation to the cause you can actually act on.
The deeper point is that the first explanation a user gives is almost always a rationalisation — a tidy, after-the-fact story that feels true but isn't the real driver. “Too slow,” “too confusing,” “didn't have time” are symptoms. The 5 Whys is uncomfortable to run because it feels repetitive and slightly impertinent, but that discomfort is exactly the friction that breaks through the rationalisation to the root cause — which is usually a more specific and more solvable problem than the one first offered.
The surface explanation is rarely the root cause. Keep asking why.
“I usually…” isn't evidence. Use TEDW to get a specific episode.
The structure is wasted if your questions plant the answers. Stay neutral.
If you're filling the silence, you're not hearing the root cause. Let them talk.
This extends the foundational interview skills with TEDW and the 5 Whys.
Combine with observing users in context (Tool 06) — what they do plus why they do it.
Root causes from the 5 Whys become the raw material for synthesis (Tools 20, 21).
Disciplined questioning counters the confirmation and leading biases covered in Tool 25.
AI extends the discovery interview at the edges — preparation, transcription, and first-pass synthesis — without replacing the craft.
The judgment that stays yours: Synthesis is where insight is made or lost, and AI clustering is a starting point, not the answer — it will confidently merge things that shouldn't be merged. Read the transcripts. And never let it fabricate or 'tidy' a quote.
Think of something a user (or you) recently found frustrating about a product. Write the surface complaint, then ask “why?” five times in a row, answering honestly each time.
See where the fifth why lands — it's usually a different, more specific problem than the one you started with.
The gap between your first complaint and your fifth “why” is the gap between a symptom and a root cause — and it's exactly the gap basic interviews never close.
New to this? Start here · User Interviews →