Skip to content
UX Atlas
Plate RES·012 · Research methodGrid G2 · Rev. 2026-08-14

Contextual Inquiry

Watching people work in their own environment, which surfaces the context that interviews miss.

Research methodEstablished researchAdvanced

Definition

Contextual inquiry combines observation and interview in the user's actual working environment. The researcher watches real work and asks about it as it happens, rather than relying on recall.

Established research. Originates in published research and has been replicated. The effect is real. Its size in your product still needs measuring.

On this plate
  1. 1Definition
  2. 2What it reveals that other methods do not
  3. 3The master and apprentice stance
  4. 4In practice
  5. 5Commonly confused with
  6. 6Local chart
  7. 7Sources
  8. 8Continue from here

Reach for this when

  • Designing for a domain you do not know.
  • Enterprise and specialist tools.
  • Understanding why adoption fails in the field.
  • The product will be used in an environment nobody on the team has sat in.

Common mistakes

  • Interrupting the work you came to observe.
  • Observing only the ideal case.
  • Visiting one site and generalising.
  • Turning the visit into a demonstration of your product.

What it reveals that other methods do not

  • The whole workflow, including the parts outside your product.
  • Physical and social context: interruptions, shared screens, second monitors, printed reference material.
  • Workarounds people no longer notice they are performing.
  • The real frequency and duration of tasks, as opposed to the reported ones.
  • Constraints such as poor connectivity, shared devices, gloves, noise or supervision.

The master and apprentice stance

  1. 1

    Agree the frame at the start

    You are there to be taught the work. Say so, because most people expect either an interview or an inspection.

  2. 2

    Watch first, interrupt second

    Let a task run to its end before asking about it. Questions mid-task change the task.

  3. 3

    Ask about the thing in front of you

    Why that spreadsheet, why that order, why the second screen. Concrete artefacts produce concrete answers.

  4. 4

    Interpret out loud

    So you do this because the system will not let you do that. Being corrected in the room is worth more than being wrong in the write-up.

  5. 5

    Photograph the environment, with permission

    The desk, the notes, the second monitor. Conditions you did not think to record are the ones that explain the behaviour later.

In practice

  1. i.

    The interruption nobody reports

    What only observation catches

    The task took eleven minutes in the interview version and forty in reality, because it was interrupted four times. No participant had mentioned interruptions, because interruptions are not what anyone thinks of as part of the work.

Commonly confused with

Close neighbours that get substituted for each other. The difference is stated first, then the condition that picks one over the other.

vs.

User Interviews

Research method

A guided conversation about experiences, context and motivation.

Key difference

An interview is a conversation about the work. Contextual inquiry happens in the place the work is done, watching it as it goes. The difference is observation: one collects what people can recall and articulate, the other collects what actually happens.

Use Contextual Inquiry when

  • The workarounds, tools and interruptions matter.
  • People cannot accurately describe what they do, which is usual.
  • You can get into the environment where the work happens.

Use User Interviews when

  • The work cannot be observed, or is spread across weeks.
  • You need history, reasoning and how people describe their world.
  • Access is limited to an hour on a call.

Learn about User Interviews

Local chart

RES·012 · Region IV · Grid G2

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

Mental ModelsMOD·001 · PRINCIPLES BEHIND THISInterview GuideTPL·002 · OFTEN USED WITHJourney MapTPL·004 · OFTEN USED WITHUser InterviewsRES·003 · COMMONLY CONFUSED WITHPutting a Data Table on a PhoneCASE·005 · PRACTICAL EXAMPLEGenerative ResearchTERM·021 · SHORT DEFINITIONService DesignTERM·017 · SHORT DEFINITIONDiary StudiesRES·013 · RELATED CONCEPTResearch SynthesisRES·014 · RELATED CONCEPTDiscoveryFLOW·004 · RELATED CONCEPT

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

    Contextual Design

    H. Beyer and K. Holtzblatt, Morgan Kaufmann, 1997

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

A DashboardA Data TableA Mobile AppAn Enterprise Workflow

Principles behind this

The reasoning this solution is an application of.

Often used with

These usually appear in the same screen or the same decision.

Practical example

A worked decision where this was the deciding factor.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.