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 starting 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?
Output
- Stakeholder insight summary
- Decision and dependency map
- Open assumptions list