UR
Contextual Inquiry
A practical in-context research method for understanding real workflows, tacit knowledge, and how work is actually done.
How to use contextual inquiry to uncover real workflows, decision-making, and inefficiencies in the environment where work happens.
What it is
Contextual inquiry is a qualitative UX serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service method used to understand glossaryUser BehaviourUser behaviour refers to how users interact with a product, including actions, patterns, and decision-making processes.Open glossary term by observing and questioning users in their real working glossaryEnvironmentAn environment is a specific configured setup where software runs, such as development, staging, or production, each with its own data and settings. Keeping them consistent is what makes behaviour in one predict behaviour in another.Open glossary term.
It is a structured form of in-glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service, combining glossaryObservationObservation is a research method where user behaviour is watched and analysed without interference.Open glossary term with active questioning while the user performs real tasks.
Unlike standard interviews, it follows a master-apprentice glossaryModelA model is a system or representation used to process data and generate outputs, often trained to perform specific tasks.Open glossary term. The user is the expert in their work, and you are there to learn from them as they go.
The goal is to uncover how tasks are really performed, including tacit knowledge, shortcuts, glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term, and workarounds that are often invisible in other methods.
Contextual inquiry works best when you treat the user as the expert and learn from how the work actually unfolds.
When to use it
Use this method when you need to deeply understand glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term, glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term, and glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term in context.
It is most useful when:
It is less useful when:
Contextual inquiry is often used alongside field studies and user interviews to build a complete understanding.
Key takeaway
Use contextual inquiry when you need depth, real workflow detail, and visibility into how work really happens.
How to run it
Set up properly
Be clear on the tasks or glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term you want to understand, the glossaryEnvironmentAn environment is a specific configured setup where software runs, such as development, staging, or production, each with its own data and settings. Keeping them consistent is what makes behaviour in one predict behaviour in another.Open glossary term that matters, and who performs them. Contextual inquiry is deep and slow, so a tight scope is what makes it affordable.
Set up the relationship explicitly at the start: they are teaching you their work, and you are learning it.
Run the method
Contextual inquiry is field serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service with a specific stance, the master and apprentice glossaryModelA model is a system or representation used to process data and generate outputs, often trained to perform specific tasks.Open glossary term. The person doing the work is the expert, and your job is to be taught.
- Observe people performing real tasks with real glossaryDataData is raw, uninterpreted information collected and stored so it can be analysed, processed, or used to inform decisions. On its own it carries no meaning; context and interpretation are what make it useful.Open glossary term, not a demonstration prepared for you.
- Ask questions in glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term, driven by what is happening rather than by your guide.
- Treat the person as the expert and let them glossaryLeadA lead is a potential customer who has shown interest in a product or service, typically by providing contact information or engaging with content.Open glossary term. Correcting them, even gently, ends the dynamic the method depends on.
- Follow the flow of the work rather than imposing structure. Where they jump between tools or double back is the finding.
- Probe for reasoning behind actions and decisions, especially the ones that look inefficient. There is usually a reason and it is usually a constraint.
Stay in the apprentice role. The moment you start explaining how the glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term is meant to work, you stop learning how it is actually used.
Capture and make sense of it
The value comes from understanding work as it is done. After the glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term, document:
- The real glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term, including steps absent from any documentation
- The reasoning behind decisions that looked irrational from outside
- Tools, workarounds and informal glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term people rely on
- Breakdowns where the current glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term obstructs the work
Use this to design for the work rather than for the glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term diagram. The two diverge more than most organisations realise.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If it feels like a standard interview, you are missing the depth.
What you get from it
Done properly, this method gives you:
Key takeaway
It reveals what other methods often miss.
Get in touch
If this sounds like something you need, we can help you understand how work really happens and where things break down.
No guesswork. No assumptions. Just clear insight you can act on.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is contextual inquiry in UX?
Contextual inquiry is a research method where users are observed and questioned in their real environment while performing tasks.
When should you use contextual inquiry?
Use it when you need to understand complex workflows, behaviours, and environments in detail.
What is the difference between contextual inquiry and contextual interviews?
Contextual inquiry is more structured and follows a master-apprentice model, while contextual interviews are generally lighter and more flexible.
How long does a contextual inquiry session take?
Typically between 1 and 2 hours, depending on the complexity of the task and environment.
Why is contextual inquiry important?
It reveals real behaviour, tacit knowledge, and workflow issues that are often missed in other research methods.
Quick take
If you want to understand how work actually gets done, step into the environment and learn while it is happening.
Related Services
