UR
Stakeholder Interviews
A practical discovery method for understanding business goals, assumptions, constraints, and internal priorities.
How to use stakeholder interviews to surface business expectations, risks, assumptions, and alignment before design or research begins.
What it is
glossaryStakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term 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 understand business goals, assumptions, glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term, and priorities from the people responsible for a product or service.
They are a core part of UX 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, helping align teams before design or serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service begins.
Unlike guideUser InterviewsDirect conversations with users to understand behaviours, needs and motivations.Open guide, these focus on internal perspectives. They reveal what the business believes, what it needs, and where risks or pressures sit.
The goal is to uncover expectations, surface assumptions, and identify where glossaryAlignmentAlignment is a shared understanding of goals and priorities across teams and stakeholders, strong enough that people act consistently without checking first. It is not the same thing as everyone agreeing.Open glossary term or tension exists.
Stakeholder interviews help you understand what the business believes, what it needs, and where the pressure points sit before work begins.
When to use it
Use this method at the start of a project or when glossaryAlignmentAlignment is a shared understanding of goals and priorities across teams and stakeholders, strong enough that people act consistently without checking first. It is not the same thing as everyone agreeing.Open glossary term is unclear.
It is most useful when:
It is less useful when:
Stakeholder interviews are often used alongside user interviews and analytics to balance business and user needs.
Key takeaway
Run stakeholder interviews early when business priorities, assumptions, or constraints could shape the direction of the work.
How to run it
Set up properly
Be clear on what you need to learn about the business, which glossaryStakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term to include, and how their roles differ. Interviewing five people with the same view is a formality.
Include the people who will resist as well as the ones who commissioned the work. The objections surface eventually, and it is cheaper to hear them now.
Run the method
glossaryStakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term interviews are serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service about the organisation rather than the user. They tell you what the business believes, what it will permit, and where the real glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term sit.
- Start with their role and responsibilities, which establishes what they can actually influence.
- Understand their goals and how they are measured. Conflicting success measures between departments explain most contradictory requirements.
- Explore their assumptions about users, and record them as assumptions rather than facts. These become the hypotheses your serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service tests.
- Identify glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term and risks: technical, legal, commercial, political. The undocumented ones are the ones that stop projects.
- Ask where they see problems and opportunities, and where they expect the work to fail. The last question is the most useful and the least asked.
Treat what you hear as evidence about the organisation, not about users. Both matter, and conflating them is how a project ends up designing the org chart.
Capture and make sense of it
The value comes from understanding the terrain. After the interviews, document:
- Goals and success measures, and where they conflict
- Assumptions about users, flagged for validation
- glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term that genuinely bind, separated from preferences
- Areas of disagreement, which need resolving before design starts
Use this to shape scope and to anticipate resistance. glossaryStakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service is how a good design survives the review it has to pass.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If everything sounds aligned, you may not have gone deep enough.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps ensure you are solving the right problem, not just the visible one.
Get in touch
If this sounds like something you need, we can help you align your teams and get clarity before moving forward.
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 stakeholder interviews in UX?
Stakeholder interviews are a research method used to understand business goals, assumptions, and constraints from internal stakeholders.
When should you run stakeholder interviews?
They are most useful at the start of a project or when there is a lack of alignment across teams.
Who should be included in stakeholder interviews?
Anyone responsible for the product or service, including product managers, designers, engineers, marketers, and leadership.
What is the difference between stakeholder interviews and user interviews?
Stakeholder interviews focus on internal perspectives and business needs, while user interviews focus on real user behaviour and experiences.
Why are stakeholder interviews important?
They help uncover assumptions, align teams, and ensure decisions are based on a shared understanding of goals and constraints.
Quick take
If you need to understand the business, constraints, and internal expectations before you start, run stakeholder interviews.
Related Services
