Protocol
Build the sequence before asking for the cause
Why is easier to invent than what happened next.
Before you use it
- Use when
- People jump directly from an outcome to a confident explanation and the intermediate events are unclear.
Keep this limit in mind
- A timeline alone does not establish causality; it only constrains the stories that remain plausible.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
First reconstruct trigger, steps, handoffs, decisions and the first unexpected state. Only then ask what may explain the divergence. A sequence gives causal claims something to attach to and exposes missing intervals.
Steps
- The timeline separates observed steps from later explanations and marks at least one unknown when evidence is missing.
An example
Before asking why an upload failed, reconstruct which file, validation result, user action, background job and error appeared in order.
Check your result
The timeline separates observed steps from later explanations and marks at least one unknown when evidence is missing.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingBuild the sequence before asking for the cause
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaAsk for the last real example before asking for the usual process
Evidence and sources
GOV.UK interview guidance recommends open, neutral questions, asking for real stories and examples, listening carefully, and using follow-ups when meaning is unclear.
Neutral wording reduces one source of bias but does not make interview evidence objective or representative by itself.
Using in-depth interviews · Do the interview
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.