UR
Contextual Interviews
A practical research method for understanding behaviour in the environment where it naturally happens.
How to use contextual interviews to observe real behaviour, constraints, and decision-making in the setting where work actually happens.
What it is
Contextual interviews are 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 in 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 where it naturally happens.
They combine interviewing with glossaryObservationObservation is a research method where user behaviour is watched and analysed without interference.Open glossary term, allowing you to see tasks, decisions, and glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term as they occur in real situations.
This makes them a more grounded glossaryVersionA version is a specific iteration of software or a product at a point in time.Open glossary term of guideUser InterviewsDirect conversations with users to understand behaviours, needs and motivations.Open guide. Instead of relying on memory or explanation, you see glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term first-hand.
The goal is to understand how 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 shapes glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term, including tools, 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, pressures, and workarounds.
The value of contextual interviews is that they let you see behaviour in context, not just hear someone describe it afterwards.
When to use it
Use this method when 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 plays a big role in how a task is completed.
It is most useful when:
It is less useful when:
Contextual interviews are often used alongside field studies and usability testing to build a complete picture.
Key takeaway
Use contextual interviews when behaviour is shaped by the setting, the tools, or the pressures around the task.
How to run it
Set up properly
Be clear on what you are trying to understand, which 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 matters, and who you need to see. The environment is the method. An interview about work done elsewhere is just an interview.
Arrange access properly. Contextual work needs permission from more people than a lab glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term, and being rushed out halfway is the usual failure.
Run the method
A contextual interview anchors every question to something you have just watched happen. It is the difference between what somebody remembers doing and what they did.
- Observe first and ask afterwards. Questions asked before you have seen anything shape what the person then shows you.
- Let people carry out tasks the way they normally would, including the shortcuts they might apologise for.
- Ask in the moment, tied to what you have just seen. "Why did you copy that into a spreadsheet?" gets you further than any prepared question.
- Avoid interrupting at critical points. Note the question and return to it once the pressure has passed.
- Focus on the actions in front of you rather than general opinion. The moment somebody starts describing what they usually do, you are back to recall.
Stay close to real glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term. The value of being there is that you can ask about things the person would never have thought to mention.
Capture and make sense of it
The value comes from grounding glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term in observed glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term. 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:
- What people actually did, separated from what they said about it
- Workarounds and improvisations, which are unmet needs made visible
- Environmental factors: interruptions, tools, other people, glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term
- Where your assumptions and the observed reality diverged
Use this to inform design decisions with evidence rather than recollection. Contextual findings survive challenge better than anything self-reported.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If it feels like a standard interview, you are probably missing the value of 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.
What you get from it
Done properly, this method gives you:
Key takeaway
It grounds your decisions in reality, not assumptions.
Get in touch
If this sounds like something you need, we can help you understand how your users actually behave in the real world.
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 are contextual interviews in UX?
Contextual interviews are a qualitative research method where users are observed and interviewed in their real environment while performing tasks.
When should you use contextual interviews?
Use them when the environment, tools, or real-world conditions significantly affect behaviour.
What is the difference between contextual interviews and user interviews?
User interviews rely on recall and explanation, while contextual interviews involve observing real behaviour in context.
How long does a contextual interview take?
Typically between 60 and 120 minutes, depending on the complexity of the task and environment.
Are contextual interviews the same as field studies?
They are closely related. Contextual interviews combine observation with questioning, while field studies may focus more broadly on observation alone.
Quick take
If you want to understand what people actually do in the real world, not what they say they do, run contextual interviews.
Related Services
