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.
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
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 glossaryEnvironmentA specific setup where software runs, such as development, staging, or production.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 glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term shapes glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term, including tools, glossaryEnvironmentA specific setup where software runs, such as development, staging, or production.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 glossaryEnvironmentA specific setup where software runs, such as development, staging, or production.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.
Before you start, be clear on what you are trying to understand, what glossaryEnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term or glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term matters, and who you need to observe.
Make sure you can access the real setting where the glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term happens. This is critical to the method.
Run the method.
A contextual interview is part glossaryObservationObservation is a research method where user behaviour is watched and analysed without interference.Open glossary term, part conversation.
Observe first, then ask questions. Let users carry out tasks naturally. Ask questions in the moment, linked to what you see. Avoid interrupting key moments unless necessary. Focus on real actions, not general opinions.
Good questions: What are you doing here. Why did you choose that. What would you normally do next. What makes this difficult.
Avoid pulling people out of the glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term or turning it into a standard interview.
Capture and make sense of it.
The value comes from connecting glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term to glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term.
Look across glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term to identify environmental glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term, repeated glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term, workarounds and adaptations, and differences between users or settings.
This is often supported by methods like guideAffinity MappingGrouping qualitative observations and ideas to reveal patterns, themes, and actionable insights.Open guide to structure findings.
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 glossaryContextThe surrounding conditions that shape behaviour and decisions.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 glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term 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 glossaryQualitative ResearchQualitative research explores user behaviours, motivations, and experiences through non-numerical data.Open glossary term method where users are observed and interviewed in their real glossaryEnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term while performing tasks.
When should you use contextual interviews?
Use them when the glossaryEnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term, tools, or real-world conditions significantly affect glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term.
What is the difference between contextual interviews and user interviews?
guideUser InterviewsDirect conversations with users to understand behaviours, needs and motivations.Open guide rely on recall and explanation, while contextual interviews involve observing real glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term in glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term.
How long does a contextual interview take?
Typically between 60 and 120 minutes, depending on the complexity of the task and glossaryEnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term.
Are contextual interviews the same as field studies?
They are closely related. Contextual interviews combine glossaryObservationObservation is a research method where user behaviour is watched and analysed without interference.Open glossary term with questioning, while guideField StudiesObserving user behaviour in real-world environments to understand how context shapes actions.Open guide may focus more broadly on observation alone.