Marcus Andrey Study
Ler em português Library

Framework · Enterprise UX · 3 min read

Contextual inquiry

Observe and interview users while they do their real work, in their real place, so you see the workarounds (Excel sheets, sticky notes) that interviews and demos never show.

CContext

Go where the work happens and watch real tasks with real data.

Typically: 1–2 hours at their desk
PPartnership

Act as an apprentice. The user is the expert in their work.

"Show me how you do this."
IInterpretation

Say back what you think you saw and let them correct you.

"So you keep this sheet because…?"
FFocus

Choose one or two tasks to understand, not everything at once.

Typically: how a booking is corrected
The four principles of contextual inquiry from Beyer and Holtzblatt: context, partnership, interpretation and focus.

Use it when

  • You start on an internal tool you have never used, and you need to understand how operators really work with it.
  • Users say the tool is "fine", but support tickets, training time or errors say otherwise.
  • You are about to redesign a dense, expert screen and need to know which habits and shortcuts you must not break.

How to use it

  1. Agree access early. Users' time is operational and costly. Ask their manager for permission, explain the purpose, and in some countries involve the works council (employee representatives). Output: an agreed date, place and consent.
  2. Plan a focus, not a script. Choose one or two tasks or questions you want to understand, such as "how a booking is corrected". Keep a short list of prompts, not a questionnaire. Output: a one-line focus and 5 to 8 prompts.
  3. Shadow real work with real data. Sit with the user for 1 to 2 hours while they do their normal tasks with real data, not demo data. Act as an apprentice: watch, and ask them to explain what they are doing and why. Output: raw notes with times, steps and quotes.
  4. Ask about the workarounds. Every time you see something outside the tool (a spreadsheet, a printed list, a sticky note, a second screen), ask what it is for and when they started using it. Output: a list of workarounds with the reason for each.
  5. Check your interpretation with them. Before you leave, say back what you think you saw ("So you keep this sheet because the tool can't show…?") and let them correct you. Output: confirmed or corrected insights.
  6. Write a one-page insight memo. Within a day, write the top findings, the workarounds and one or two design implications. Group findings across sessions with affinity mapping. Output: a one-page memo per session.

Worked example

An internal operations platform with 6 product teams. A designer shadows a booking operator for two hours on a Monday morning.

What she saw What she asked Insight
The operator copies order numbers from the tool into an Excel sheet. "What is this sheet for?" The tool can't show all orders waiting for a customer reply. The sheet is the real to-do list.
A sticky note with three customs codes on the monitor. "When do you use these?" The code search is too slow, so he memorised the most common codes.
He uses the keyboard for everything, never the mouse. "What happens if this button moves?" A new layout would break his speed. Change incrementally.

Her memo led to one design decision: a saved "waiting for reply" filter in the order table, which replaced the Excel sheet.

Watch out for

  • Demo data. Fake data hides real problems: long names, missing fields, odd edge cases. Use the real work, with the right consent.
  • Interviewing in a meeting room. Away from the screen, people describe the ideal process, not the real one. Go to where the work happens.
  • Skipping the manager. Taking operators away from work without permission damages trust and access. Agree it first.
  • Notes that nobody reads. Raw notes don't change decisions. Write the one-page memo while it is fresh.

Template

Copy this into your research notes for each session.

Contextual inquiry session

Date:            Place:            Role observed:
Consent / manager approval:
Focus (one line):

Time   What they did          What they said           Workaround seen
       ...                    ...                      ...

Workarounds (what, why, since when):
1.
2.

Interpretations checked with the user:
Top 3 insights:
Design implications:
Source
Beyer & Holtzblatt

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close