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.

16 August 20256 min read

Quick take

If you want to understand how work actually gets done, step into the environment and learn while it is happening.

What it is

Contextual inquiry is a qualitative UX method used to understand by observing and questioning users in their real working .

It is a structured form of in- , combining with active questioning while the user performs real tasks.

Unlike standard interviews, it follows a master-apprentice . 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, , 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 , , and in context.

It is most useful when:

Tasks are complex and involve multiple steps or systems
Users rely on habits, shortcuts, or tacit knowledge
The environment plays a significant role in how work is done
You need to understand real workflows, not idealised ones
There is a gap between documented processes and actual behaviour

It is less useful when:

The task is simple or low complexity
You only need high-level understanding
Access to the real environment is not possible
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.

Before you start, be clear on what tasks or you want to understand, which is relevant, and who you need to observe.

Make sure you have access to real users performing real work. This is essential.

Run the method.

Contextual inquiry is interactive but grounded in .

Observe users performing real tasks. Ask questions in , based on what you see. Treat the user as the expert and let them . Follow the of the task rather than forcing structure. Probe for reasoning behind actions and decisions.

Good questions: What are you doing here. Why did you choose that. What would you normally do next. What makes this difficult.

Avoid turning it into a traditional interview or interrupting critical moments.

Capture and make sense of it.

The value comes from connecting to and .

Look across to identify and sequences, repeated and patterns, workarounds and inefficiencies, and gaps between expected and actual processes.

Structure so they reflect how work is actually done.

What to look for

Focus on:

Real workflows
How tasks actually unfold step by step
Tacit knowledge
Things users do without thinking or explaining
Workarounds
Adaptations that reveal system limitations
Decision points
Where users make choices or change direction
Context
Tools, systems, environment, and pressures shaping behaviour

Where it goes wrong

Most issues come from:

If it feels like a standard interview, you are missing the depth.

losing the master-apprentice mindset
asking too many abstract questions
interrupting the natural flow of work
focusing only on what is said, not what is done
trying to control or structure the session too tightly

What you get from it

Done properly, this method gives you:

a deep understanding of real workflows
insight into how work actually gets done
visibility of inefficiencies and gaps
clear direction for improving systems and experiences

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 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 method where users are observed and questioned in their real while performing tasks.

When should you use contextual inquiry?

Use it when you need to understand complex , , and in detail.

What is the difference between contextual inquiry and contextual interviews?

Contextual inquiry is more structured and follows a master-apprentice , while 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 .

Why is contextual inquiry important?

It reveals real , tacit knowledge, and issues that are often missed in other methods.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20