UR
Expert Interviews
A practical discovery method for bringing specialist knowledge, patterns, and risks into a project early.
How to use expert interviews to build understanding quickly in complex domains, uncover risks, and avoid solving the wrong problem.
What it is
Expert interviews are a glossaryQualitative ResearchQualitative research explores user behaviour, motivation, and experience through non-numerical evidence such as interviews, observation, and testing. It is designed to explain why something happens rather than to measure how often.Open glossary term method used to gather glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term from people with specialist knowledge in a specific domain, industry, or subject area.
They are used in UX serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service and glossaryProduct DiscoveryProduct discovery is the work of understanding a problem, the people who have it, and the opportunity around it before committing to a solution. It exists to reduce the risk of building something well that nobody needed.Open glossary term to quickly glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term understanding where internal knowledge is limited.
Unlike guideUser InterviewsDirect conversations with users to understand behaviours, needs and motivations.Open guide, experts are not representing typical glossaryUser BehaviourUser behaviour refers to how users interact with a product, including actions, patterns, and decision-making processes.Open glossary term. They provide 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, patterns, risks, and informed perspectives based on experience.
The goal is to accelerate understanding, reduce blind spots, and avoid solving the wrong problem.
Expert interviews help you build understanding quickly, but they should inform direction rather than stand in for users.
When to use it
Use this method when you need informed 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 rather than direct glossaryUser BehaviourUser behaviour refers to how users interact with a product, including actions, patterns, and decision-making processes.Open glossary term.
It is most useful when:
It is less useful when:
Expert interviews are often used alongside user interviews and secondary research to build a balanced view.
Key takeaway
Use expert interviews to build context quickly, especially when complexity, regulation, or specialist knowledge shapes the problem.
How to run it
Set up properly
Be clear on what you need to learn about the domain, what kind of expert can tell you, and how their expertise maps to your problem. Domain expertise and serviceUser ExperienceImprove journeys, reduce friction, and make digital products clearer, simpler, and easier to move through.Open service are different things.
Do the background reading first. Expert time is expensive and easily spent on things you could have looked up.
Run the method
Expert interviews buy speed. They compress months of domain learning into hours, which matters most in regulated, technical or specialist spaces where being wrong is costly.
- Start with their background, so you can weight what follows. An expert in the regulation is not an expert in how practitioners actually work around it.
- Explore how the domain works in practice rather than in principle. The gap between the two is usually where the design opportunity is.
- Ask about glossaryPatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.Open glossary term, risks and common failure modes. Experts are unusually good at naming what typically goes wrong.
- Probe for real examples. A concrete case is worth more than a general principle and is harder to mis-transfer.
- Challenge assumptions where you need to, politely. Experts are used to being deferred to, and deference produces a tidy but incomplete picture.
Remember that an expert is not a user. They know the domain deeply and often no longer see what a newcomer finds impossible.
Capture and make sense of it
The value comes from rapid domain understanding. After the interviews, document:
- How the domain works in practice, including the informal parts
- Risks, glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term and regulatory limits that shape what is possible
- Common failure modes worth designing against
- Questions that still need answering with actual users
Use this to get competent quickly, then test with users. Expert glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term sets the questions; it does not answer them.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
Experts provide guidance, not ground truth.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps you move faster without making avoidable mistakes.
Get in touch
If this sounds like something you need, we can help you get up to speed quickly and make informed decisions from the start.
No guesswork. No assumptions. Just clear direction you can act on.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What are expert interviews in UX?
Expert interviews are a research method used to gather insight from people with specialist knowledge in a domain relevant to a product or service.
When should you use expert interviews?
Use them when entering a new domain, dealing with complex systems, or when you need informed context quickly.
What is the difference between expert interviews and user interviews?
Expert interviews provide domain knowledge and context, while user interviews focus on real user behaviour and experiences.
How many expert interviews do you need?
Usually 3 to 6 experts are enough to identify strong patterns, depending on the complexity of the domain.
Can expert interviews replace user research?
No. They provide context and guidance, but they do not reflect actual user behaviour.
Quick take
If you need deep domain knowledge quickly, speak to people who already understand the space.
Related Services
