methodatlas
RunsheetUX Research

Contextual Inquiry

ComplexityMedium
Time1-3 Wochen
Participants4-12 Beobachtungen
FormatWorkshop + async
MaturityCanonical
01

Prerequisite

What needs to be finished first

Complete firstPersonas

At least one rough persona or user-segment profile is available so participant selection is goal-oriented.

Without: Without persona anchors, teams recruit by availability, and observations are not generalizable to the target audience.
Complete firstResearch questionnot in catalog

A concrete research question focused on activity, context, or workaround is defined and aligned with the product team.

Without: Without a precise question, the researcher observes everything and nothing at the same time, and synthesis becomes difficult.
02

Preparation

What needs to be ready before start

Materials

Notebook or tablet with an observation template; recorder (audio or video) with consent; camera for artifact photos; travel setup for on-site visits (power, business cards); structured field notes template.

People / roles

One primary researcher (lead interviewer and observer); optional note-taking partner; the user performing work in their real context; and one organization representative for safety-critical devices or rooms if required.

Pre-read

Written consent; explanation of the Master-Apprentice model (user is the master, researcher is the apprentice); briefing on time window, duration, and recording; expectation that normal work should continue with no demonstration.

Time needed

90-180 min per inquiry plus 60 min follow-up

Setup

Meet at the participant's actual workplace, not in a meeting room. Researcher sits beside or slightly behind the person, not opposite. Place recording device visibly. Start with a 5-minute setup: explain the model, confirm consent, and clarify when interruptions are acceptable.

03

Core question

The one question this method answers

How does the participant carry out their work in the real context, which workarounds, artifacts, and implicit assumptions shape the process, and which of these observations are design-relevant?

04

Flow

Marker: Minute

StepDurationActionHint
10-10 min
10 minIntroduction on the workstation: introductions, consent confirmation, explanation of the Master-Apprentice model. Briefly brief the task the person is anyway completing today.If the person prepared a special task for the study, the method is contaminated. Repeat the instruction: normal work in normal sequence.
210-90 min
80 minObserve and ask clarifying questions: participant works, researcher observes, asks questions in the flow ("What are you doing now?", "Why this way?"). Document artifacts, screens, and workarounds.If the researcher speaks more than the participant, the balance is off. Rule of thumb: 20% researcher, 80% participant. Hold silence and let the participant continue explaining.
390-110 min
20 minReview with the participant: walk through observed steps together, validate interpretations, and clarify open questions. The participant confirms or corrects what the researcher understood.Skipping this phase moves interpretation to a later solo effort. Recapping with the participant saves hours during synthesis and avoids misinterpretation.
4110-120 min
10 minClose: thank the participant, define next step (feedback loop), and provide contact details for follow-up questions. Stop the recording and say goodbye.Do not evaluate in front of the participant. Impressions are not yet synthesized; premature conclusions can frustrate or upset them.
5120-180 min
60 minImmediately after the session, do structured follow-up: complete field notes, skim the recording, form initial theme clusters, sort photos, and note open questions for the next inquiry.If synthesis takes place later than 24 hours, impressions blur. Invest at least 30 minutes the same day; do full synthesis within 48 hours.
05

Artifact

What comes out at the end

Form

Structured field notes per inquiry with context, observed steps, verbatim quotes, artifact photos, workaround observations, open questions, and first interpretations. For study-level synthesis, aggregate a shared affinity wall from 4-6 inquiries.

Versioning / ownership

One file per inquiry with date, role, and pseudonym in the header. Pseudonymize personally identifiable data. Keep aggregated synthesis linked to individual inquiries to preserve traceability.

Tool alternatives
  • Notion or Confluence page per inquiry with embedded photos
  • Dovetail or Condens for tagging and thematic grouping
  • Miro board with sticky notes for affinity diagramming
  • Markdown in the repo under research/inquiries/<date>-<role>.md

contextual-inquiry-working-template.md

Compact working template for Contextual Inquiry with context, input, output artifacts, and next step.

Contextual Inquiry Working Template

Goal

Observes and interviews users while they are doing real work in their actual context of use.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Field Notes:
  • Workflow Insights:
  • Pain Points:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

06

Example output

Concrete filled scenario, fictional example

contextual-inquiry-beispiel.md

Concrete filled scenario, fictional example

Contextual Inquiry — Sabine, solo tax advisor, 02.05.2026

Context: Home office, Monday morning, task "month-end close for client Mr. Müller".

Observed steps

  1. Sabine opens three tools in parallel: DATEV (tax software), Excel workbook (her own checklist), Outlook (client mail folder).
  2. She first scans Outlook for documents, then manually drags documents into a DATEV folder.
  3. For each document she checks date, VAT code, and posting text against DATEV suggestions.
  4. For unclear documents she writes to the client directly via WhatsApp from her phone.

Workarounds and quotes

  • Own Excel checklist because "DATEV does not tell me what I missed."
  • WhatsApp instead of client portal: "It answers in 5 minutes, the portal in 5 days."
  • Duplicate data entry: client master data in DATEV and Excel.

Interpretation

The Excel checklist is not a learning aid, but completeness control. Product implication: implement a completeness indicator in the tool itself rather than in training documentation.

07

Pitfalls

Recognize symptoms and steer against them

Trap

Researcher as expert instead of apprentice

Symptom

Researcher explains, suggests, and compares with other users. The participant listens instead of working.

What to do

Keep the Master-Apprentice model explicit. Pause after 30 seconds of your own talking. Ask questions rather than giving statements. Keep observations for synthesis and do not share them during the inquiry.

Trap

Showcase setting

Symptom

The participant prepared a special task for the study; the workspace looks organized and unusually structured.

What to do

Reinforce beforehand that normal work is expected. If it is still staged, ask about the real workflow from the past week and reconstruct examples before observing.

Trap

Abstract questions instead of concrete observation

Symptom

The researcher asks, "What would you like?" or "How do you normally do this?" instead of seeing concrete actions in context.

What to do

Anchor questions in what is happening now: "What are you doing right now?", "Why this step?". Move hypothesis questions to the end, not into the observation flow.

Trap

Notes without quotes

Symptom

Field notes only contain summaries like "Sabine found the tool cumbersome," with no verbatim quotes.

What to do

Capture at least 10 verbatim quotes per inquiry, with timestamps and quotation marks. Quotes are the evidence base for synthesis and protect against confirmation bias.

Trap

Sessions too short

Symptom

In a 60-minute slot the participant reaches the main task by 30 minutes and the researcher only observes the surface.

What to do

Schedule at least 90 minutes, ideally 2 hours. If the participant finishes early, ask for follow-up tasks or explore edge cases and exceptions.

Trap

Delayed follow-up

Symptom

The recording is analyzed two weeks later, with field notes containing gaps and faded recall.

What to do

Block 30-60 minutes immediately for follow-up. Use the recording only as backup, prioritizing your own notes. Book the follow-up slot before the inquiry.

08

Stop criteria

Done signals checkable in under a minute

The participant cannot be observed in their real work context, only a conference-room setup is possible.
Consent is not explicit or legal conditions are unclear (sensitive data, patients, minors without authorization).
The participant's task today is atypical (illness, edge case), so observation does not reflect representative practice.
Time window is under 60 minutes, so the full flow including debrief is not possible.
The research question is not defined and the researcher observes generically without a synthesis path.
An organization representative interferes with the work, and the participant behaves performatively or self-censors.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.