Use when
- You need business rules, constraints, policy context, or domain expertise.
- You need to understand ownership, dependencies, or delivery constraints.
Do not use when
- You are using stakeholder opinion as a substitute for user evidence.
Best for
- Clarifying scope and rules
- Understanding domain, risk, or compliance context
- Surfacing assumptions and decision criteria
How to design it
- Use structured prompts for goals, constraints, policy, dependencies, and success measures.
- Separate factual constraints from assumptions and preferences.
- Record what still needs user evidence after stakeholder sessions.
Stakeholder Interview TemplateUse this when you need a practical reading template.
View template
- What problem are we trying to solve and for whom?
- What rules, constraints, or risks matter most?
- What would make this initiative fail operationally or politically?
- What still needs direct user evidence?
Typical output
- Stakeholder insight summary
- Decision and dependency map
- Open assumptions list
Useful resources
Nielsen Norman GroupStakeholder Interviews 101
Primary method guidance for learning business goals, processes, pain points, and priorities.
Nielsen Norman GroupStakeholder Analysis for UX ProjectsHelps identify which stakeholders matter and how their influence affects discovery.
Nielsen Norman GroupHow to Collaborate with Stakeholders in UX ResearchUseful when stakeholder participation and buy-in affect research quality.