Contextual inquiry
A method in which people are observed and asked questions while they carry out their tasks in their own setting, like an apprentice beside a master.
What it’s for
Discovering how things are really done, including the details no one would mention in an interview.
Key elements
Context
Go where the person works and watch them work.
Partnership
The person is the expert; the researcher learns as an apprentice.
Interpretation
Check your understanding with the person as you go.
Focus
Go with a clear purpose and test your assumptions.
An example
Two ways to understand how staff at a bank branch work.
In their context, people show tricks and problems they take for granted and would never mention.
How it’s done
You accompany the person while they do their real work.
You ask in the moment, without interrupting too much.
You interpret with them what you have observed.
Applications in design
When to use it
To understand a job or a task as it is really done, where it happens.
Avoid
Turning it into a sit-down interview far from where everything happens: ask the person to show you how they do it, as if you were going to learn their job.
Don’t fall for it
Notice the papers, notes and shortcuts they have created: they reveal what the system doesn’t solve.
Connections
Authors and works
- 1988
John Whiteside, John Bennett and Karen Holtzblatt
Described the method in an account of their usability engineering work.
- 1998
Hugh Beyer and Karen Holtzblatt
Systematized it, with its four principles, in Contextual Design.
Sources
Original sources
- Whiteside, J., Bennett, J., & Holtzblatt, K. (1988). Usability engineering: Our experience and evolution. In M. Helander (Ed.), Handbook of human-computer interaction. North-Holland.
- Beyer, H., & Holtzblatt, K. (1998). Contextual design: Defining customer-centered systems. Morgan Kaufmann.
Last reviewed: