What it is
Structured conversations with internal stakeholders, sponsors, subject-matter experts, and partners to understand business goals, constraints, definitions of success, and organizational context.
When to use it
At the start of a project, during Initiate and into Immerse, before or alongside user research.
Why (value)
Aligns the team on goals and constraints, uncovers political and technical realities, and prevents late-stage surprises. Builds relationships that ease later decisions.
How to run it
- Identify stakeholders across business, tech, and domain expertise.
- Prepare open questions about goals, success, constraints, and concerns.
- Interview one-on-one; listen more than you pitch.
- Capture goals, constraints, risks, and conflicting views.
- Synthesize into shared context and feed the brief.
Inputs and outputs
- Inputs: Stakeholder list, interview guide, scheduling access.
- Outputs: Documented goals, constraints, success criteria, and areas of disagreement.
Time and effort
Medium. A round of interviews plus synthesis over one to two weeks.
Evidence and limitations
Stakeholders provide proxy evidence about users, useful for context and constraints, but not a substitute for talking to actual users. Keep the two clearly separated. See Evidence and limitations.
Tips and pitfalls
- Do not treat stakeholder opinions about users as user evidence.
- Interview individually to hear candid views.
- Capture conflicts, they predict future friction.
Variations
Sponsor interviews, SME interviews, kickoff workshops.
Related methods
Need help planning research or facilitating this method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
Explore related methods
- Interviews — Talk with users one on one to understand their goals, context, and reasoning in their own words.
- Stakeholder mapping — Chart who has interest and influence over the work so you engage the right people at the right time.
- Design briefs — A one-page contract that aligns everyone on goals, scope, constraints, and success before design starts.
