Contextual Inquiry

Contextual inquiry is a field research method in which a researcher visits a user in their actual work or use environment — an office, a kitchen, a warehouse, a hospital ward — observes them performing real tasks with real tools, and asks questions about what they see as the work unfolds, rather than relying on the user's retrospective account of how they work in a scheduled interview away from their context. The method is built on the recognition that users cannot fully articulate their own workflows, habits, and workarounds in the abstract — but those workflows, habits, and workarounds become visible and discussable in the moment they occur, in the environment where they are embedded.

The method was developed by Karen Holtzblatt and Hugh Beyer at Digital Equipment Corporation in the late 1980s and formalised in their 1997 book Contextual Design. What makes it specifically valuable for product teams is the tacit knowledge problem: users consistently describe an idealised or simplified version of their workflow when interviewed away from their context, but observation in context reveals the actual workflow — including the spreadsheet they maintain alongside the product to compensate for a missing feature, the Slack message they send to a colleague before every time they use a specific function, and the seven-step manual workaround they have built to handle the edge case the product does not cover.

Contextual inquiry works by eliminating the distance between what users do and what they report. In a standard interview, users answer questions about their work from memory, which produces a reconstructed, idealised account. In contextual inquiry, the researcher is present in the environment while the work is happening — seeing the actual screens, tools, Post-it notes, physical documents, and colleague interactions that constitute the real workflow. Every question is anchored to a specific observed event: "I noticed you opened a second spreadsheet just then — can you tell me what that is for?"

When IDEO was commissioned to redesign hospital food service delivery systems for a large healthcare provider, the team began with contextual inquiry rather than stakeholder interviews. They spent days in hospital kitchens and on wards observing the complete food delivery workflow — from meal preparation through tray assembly, delivery, patient interaction, and tray collection. What they observed in context was impossible to elicit in an interview: dietary aides were memorising patient preferences not from the electronic patient records system (which was the official system of record) but from handwritten notes they kept in their pockets, because the official system was too slow to access at the point of need.

The insight that emerged from observation — that the real information system for dietary preferences was a pocket notebook, not the electronic record — changed the design scope entirely. A product team working from stakeholder interviews would have focused on improving the electronic records interface. Contextual inquiry revealed that the problem was not the interface but the access model: dietary aides needed information at the point of delivery, not at a desktop terminal. The design response — a printed card attached to each tray with the patient's name, dietary restrictions, and current preferences — was derived entirely from observing the actual workflow rather than the intended one.

Contextual inquiry is the most immersive field research method in the UX toolkit. Its closest relatives are methods that share its commitment to observing real behaviour in real context, differing primarily in duration, structure, and the balance between observation and intervention.

The most important pairing is contextual inquiry with Affinity Mapping. Contextual inquiry generates raw observational data that is rich but unstructured. Affinity mapping transforms that data into the cross-session patterns that are actionable for design. Without affinity mapping, contextual inquiry findings exist as a collection of field notes and anecdotes. Without contextual inquiry, affinity mapping has no observational raw material of sufficient depth to surface the tacit-knowledge patterns that make the method uniquely valuable.