Contextual inquiry: why watching someone work beats asking them about it

Contextual inquiry means watching people do their real work and asking as they go. Use it for complex processes, run it in four parts and avoid the common traps.

Instant Expert EditorialPublished Updated 6 min read

Contextual inquiry is the best way to learn how complex work really gets done: you watch someone do their real work, where they do it, and ask questions as they go. Nielsen Norman Group describes it as a type of ethnographic field study that combines in-depth observation and interviews with a small number of users to understand their work practices and behavior (Nielsen Norman Group). Karen Holtzblatt developed the technique, and it is the core of Contextual Design, the method Holtzblatt and Hugh Beyer set out in their book of the same name (Elsevier).

Asked from memory, people give a tidy summary. While working, they show you the workarounds the summary leaves out, and explain each one as it happens.

Use it for complex work, early

NN/g says contextual inquiry suits complex systems, detailed processes and the work of expert users, and that teams usually do it early, while deciding what to build. Its insurance software example: specialists who entered vehicle data all said in interviews that they pasted it from a spreadsheet. Watched at work, they were also looking up missing details in a second system and clicking save after every entry, even though the software saved automatically.

Skip it for simple screens, such as a signup form, where a usability test is faster. When people can't be interrupted, as with doctors seeing patients, NN/g suggests silent direct observation with questions afterward.

If your question is...Consider
How does this work actually get done, step by step?Contextual inquiry
Can people complete this task with our design?Usability testing
Why did people choose, switch or stop?In-depth interviews
How common is this behavior?A survey or product data

Act like an apprentice, guided by four principles

The participant is the master craftsperson and you are the apprentice, learning by watching and asking. NN/g summarizes four principles, in plain terms:

  • Context. Go where the work happens, not to a conference room.
  • Partnership. The participant helps steer the session; you don't control every topic.
  • Interpretation. Say what you think is happening and let them correct you.
  • Focus. Know what you're there to learn, so you know what to watch for.

GOV.UK's service manual adds that a familiar setting helps people remember details and shows behavior a lab can't, though some people are uncomfortable having researchers at work (GOV.UK).

A made-up example: the paper list on the monitor

Here is a made-up example. A startup is building scheduling software for companies that maintain heating, cooling and electrical systems in office buildings. In interviews, dispatchers described the job simply: a request comes in, they check who is free and assign it.

The team sits with two dispatchers for a morning each. They watch one dispatcher take a call about a broken air-conditioning unit, and then:

  • Check a paper list taped to the monitor showing which technicians are certified for that building's equipment
  • Text a technician to ask whether the right part is in the van
  • Call the building manager back to confirm access, because the request didn't say who would let the technician in
  • Re-enter the job into the billing system by hand

None of these steps came up in the interviews. (The paper list has probably outlived two scheduling systems already.) The list and the parts check suggest the real scheduling problem is matching skills and parts to each job, which is harder than finding someone who is free.

Run each session in four parts

NN/g describes this structure:

  1. Primer. Explain what you hope to learn and that they should correct your interpretations, discuss confidentiality and get permission for any recording. Ask for a quick summary of the work ahead.
  2. Transition. Say clearly that you'll now watch them work as usual and interrupt when something needs explaining. Ask them to flag moments when an interruption would be a bad idea.
  3. Contextual interview. Watch, then stop to ask when they do something you don't understand, or to check an interpretation: "So the paper list is where you check certifications, not the scheduling system?"
  4. Wrap-up. Summarize what you learned and let them correct you.

Sessions run from an hour or two to several days, depending on how much work you need to see.

Before you go:

  • Ask the participant's employer for permission to visit, and agree in advance what you may photograph or record.
  • If the work involves customer or confidential information, agree on what you will leave out of your notes. How to ask for recording consent covers that conversation.
  • Follow GOV.UK's advice: don't go alone to a location away from your office, and tell your team where you are.
  • Note what people do as well as what they say; how to take interview notes suggests a format.

If you can't visit, a screen share still shows the steps on their computer, minus the paper lists, phone calls and chats at the next desk.

Watch for the four ways a session goes wrong

NN/g lists four common risks:

  • The participant slips into interview mode and starts summarizing instead of working. If it happens, remind them you want to see the work done as usual.
  • The session becomes a list of complaints about current software. Redirect them to the work.
  • You bring your own assumptions and see what you expected. Treat every observation as equally important until you've compared sessions.
  • You change their behavior by asking about it. Ask open questions, and save most interpretations for the wrap-up.

Pool what you saw while it is fresh

Meet with everyone who observed soon after. Beyer and Holtzblatt's book includes structured interpretation sessions and an affinity diagram for consolidating what many participants showed you, and NN/g also suggests affinity mapping to find themes. Affinity mapping walks through that step. In the facilities example, the team would put the two dispatchers' steps side by side and mark which workarounds both used.

Your next step

Write down the one process you most need to understand and the job title of the person who does it every day. Ask two or three of those people to let you watch for an hour or two while they work, and list beforehand what you'll look for.

If you don't know anyone who does the work, start with a short call: have them walk you through the process, then ask about a longer observed session. Instant Expert can send that first invitation to people who match a description you write, such as "dispatchers at commercial facilities maintenance companies." Use the call to hear the steps and agree on an observed session; a described shift leaves out the workarounds you would see in person, so don't treat it as the observation. You set what each person receives, our fee is added on top, and you're charged only when someone books. Say in your note that you may ask about watching them work later, so the follow-up request doesn't surprise them. The operations professionals in facilities management directory page is one place to start.

The four parts of a contextual inquiry session

  1. 1

    Primer

    Introduce yourself, explain the goal, cover confidentiality and recording, and ask for a quick summary of the work.

  2. 2

    Transition

    Say you'll now watch them work as usual and interrupt when something needs explaining.

  3. 3

    Contextual interview

    Watch, then pause to ask about steps you don't understand or to check an interpretation.

  4. 4

    Wrap-up

    Summarize what you saw and let the participant correct or add to it.

An explicit transition keeps the participant working instead of summarizing, and the wrap-up is where they correct your interpretations.