How to Conduct Stakeholder Interviews for UX Research

Before you talk to a single user, you need to understand the business landscape you're working in. That's where stakeholder interviews come in. These are conversations with the people who shape your product -- decision-makers, subject matter experts, team leads -- to surface business goals, technical constraints, and the assumptions everyone is carrying around but rarely says out loud.

Done well, stakeholder interviews align your research with what the business actually needs and reveal contradictions worth investigating through methods like usability testing or card sorting.

Difficulty: Beginner Time Required: 2-3 hours (including preparation and follow-up)

Whether you're kicking off a new project or revisiting an existing one, these interviews shape everything that comes after.

What You'll Need

• Interview participants: A handful of key stakeholders -- product managers, developers, business analysts, marketing leads
• Recording tool: Zoom, Teams, or whatever your team uses for calls
• Note-taking method: A document, notebook, or interview template
• Question framework: A prepared list of open-ended questions
• Scheduling tool: Your calendar app
• Analysis workspace: A spreadsheet or affinity mapping tool for pulling themes together

Step 1: Identify and Prioritize Your Stakeholders

Start by mapping out everyone who has influence over or knowledge about your project. Think broadly: product owners, engineering leads, marketing managers, customer support reps, domain experts. Then narrow it down.

You don't need to talk to everyone. A small group of well-chosen stakeholders -- typically somewhere around four to six people -- will give you diverse perspectives without burying you in data. Talking to more people than that rarely adds proportional value, and the synthesis gets unwieldy fast.

Prioritize based on two things: how much decision-making power someone has, and how close they are to your users.

For example: On an e-commerce redesign, your top picks might be the product manager (high influence, deep knowledge), the lead developer (high influence, understands technical constraints), and the customer service manager (moderate influence, but talks to users every day).

Choosing the right people matters more than choosing more people.

Step 2: Craft Your Interview Questions Around Three Key Areas

Your questions should cover three areas: business objectives, user assumptions, and project constraints. Aim for open-ended questions that encourage people to tell stories rather than give you yes-or-no answers.

Business objectives:

• "What does success look like for this project in 6 months?"
• "How does this initiative tie to broader company goals?"
• "What metrics will determine if we've succeeded?"

User assumptions:

• "Who do you think our primary users are?"
• "What's the biggest challenge users face with our current solution?"
• "What user feedback have you heard recently?"

Project constraints:

• "What technical limitations should I be aware of?"
• "Are there any features that are absolutely non-negotiable?"
• "What's our realistic timeline and budget?"

You don't need to be rigid about the number of questions. Eight to twelve is a reasonable range, but what matters is that you're covering all three areas. These categories tend to surface the assumptions and blind spots that matter most for planning your research.

Step 3: Schedule and Structure 45-Minute Interviews

Forty-five minutes is a sweet spot for stakeholder interviews. It's long enough to go deep, short enough that busy people will actually show up. Send your questions a day ahead so participants have time to think.

A loose structure helps keep things on track:

• First 5 minutes: Warm up, explain what you're doing and why
• Next 25 minutes: Work through your core questions
• 10 minutes: Follow up on anything interesting, ask clarifying questions
• Last 5 minutes: Wrap up and outline next steps

Record the conversation (with permission) and take notes at the same time. Notes help you catch nuances in the moment and prompt better follow-up questions -- something you'll miss if you rely entirely on going back through a recording later.

A good opener: "I'm talking to a few people on the team to understand our business goals and user needs before we start research. Your perspective will directly shape what we focus on."

Step 4: Listen for Contradictions and Dig Deeper

This is the most important part. When stakeholders disagree with each other -- about who the users are, what they want, or what matters most -- those disagreements are gold. They tell you exactly where you need objective user research.

Keep a few follow-up probes in your back pocket:

• "Can you give me a specific example of that?"
• "How do you know that's true?"
• "What would happen if we didn't prioritize that?"
• "Who else shares that perspective?"

Here's a common one: Your product manager says users want more features. Your customer support lead says users already find the interface overwhelming. Both believe they're right. That tension is exactly the kind of thing card sorting, usability testing, or user interviews can resolve with actual data.

Don't try to settle these disagreements in the room. Your job is to note them and turn them into research questions.

Step 5: Synthesize Findings into Themes and Research Questions

Don't let your notes go stale. Review them soon after you wrap up interviews -- ideally within a day or two, while everything is still fresh.

As you go through your notes, sort what you're hearing into a few buckets:

• Consensus: Things everyone agreed on. These are likely solid requirements.
• Conflicts: Places where stakeholders disagreed. These become your most important research questions.
• Gaps: Things nobody could answer. These become research priorities.

A simple spreadsheet works well here. Track the stakeholder, the theme, a representative quote, and what it means for your research. You'll quickly spot which themes come up again and again.

For example: If three stakeholders all mention "improving navigation" but describe completely different navigation problems, that's a strong signal you need navigation-focused research -- tree testing or card sorting -- to understand how users actually think about your content.

The goal is to turn a pile of individual opinions into a clear set of research priorities your whole team can get behind.

Step 6: Create a Stakeholder Requirements Summary

Pull your findings into a short, shareable document. Keep it brief -- a couple of pages at most. Include:

• Business objectives consensus: The handful of goals everyone aligned on
• User assumptions to validate: Specific beliefs about users that need research
• Technical and resource constraints: Limitations that will shape your approach
• Recommended research activities: Methods that address the gaps and conflicts you found

Share this with everyone you interviewed within a week and ask for corrections. This step builds buy-in and catches misunderstandings before they become problems.

For example: "Stakeholders disagreed on how users categorize our product features. We recommend running an open card sort with 20-30 users to understand their mental models before redesigning the information architecture."

This summary becomes your research roadmap and gives you clear justification when you need to make the case for budget or resources.

Tips and Best Practices

Record everything. The most interesting stuff often comes out in the minutes before or after the "official" interview. Always ask permission, and label your recordings clearly.

Ask about past research. Stakeholders frequently reference old studies or customer feedback you should review before planning new work. No point repeating what's already been done.

Push for specifics. When someone says "users hate X," ask for examples, data, or customer quotes. Broad claims without evidence are assumptions -- and assumptions are what you're here to identify.

Pay attention to politics. How stakeholders talk about other teams tells you a lot about internal dynamics that will affect your project. You don't need to get involved, but you should be aware.

Follow up quickly. Send thank-you notes within a day. Share your summary within a week. Momentum matters, and people forget details faster than you'd expect.

Common Mistakes to Avoid

Talking to too many people. After six or seven interviews, you'll hear mostly the same things. Focus on getting the right people, not more people.

Asking leading questions. "Don't you think users would prefer X?" is going to get you agreement, not insight. Try "How do you think users would respond to X?" instead.

Skipping synthesis. Raw interview notes sitting in a folder help no one. The value is in the patterns, and patterns only emerge when you actively look for them.

Ignoring contradictions. It's tempting to smooth over disagreements diplomatically. Resist that. Contradictions are your most valuable research leads.

Treating stakeholder opinions as facts. Stakeholder interviews surface assumptions. You still need user research to find out which assumptions hold up and which don't.

Next Steps

• What is Card Sorting? Complete Guide
• User Research (UX Glossary)
• Ux Research Methods (UX Glossary)
• Card Sorting Examples

Now take what you've learned and put it to work. If stakeholders disagreed about how users think about your content or product categories, a card sorting study will give you real data to work with. If they made assumptions about user preferences, plan usability tests or surveys to check those against actual behavior.

Build a research roadmap that prioritizes based on business impact and where stakeholders were least aligned. Share it with your team to keep things moving and show how you got from stakeholder conversations to a concrete plan.

Ready to validate what you heard? Run a card sort to find out how your users actually organize and think about your content -- and settle those stakeholder debates with data.

Frequently Asked Questions

How many stakeholders should you interview for UX research? Somewhere around four to six is a good target for most projects. That range gives you enough viewpoints to see where people agree and disagree, without making synthesis a nightmare. Beyond that number, you tend to hear diminishing new information.

What questions should you ask stakeholders in UX interviews? Focus your questions on three areas: what the business is trying to achieve, what people believe about users, and what constraints exist around technology, timeline, or budget. The goal is to uncover assumptions -- not to confirm what everyone already thinks they know.

How long should stakeholder interviews take? Around 45 minutes works well. That gives you enough time for real conversation without losing people's attention or making it hard to find a slot on their calendar. A short warm-up, a focused question block, and some room for follow-up discussion is all you need.

When should you conduct stakeholder interviews in the UX process? Before you do any user research. Stakeholder interviews help you understand the business context, figure out which user assumptions are worth testing, and identify constraints that will shape your approach. Starting with user research before you've talked to stakeholders often means you're asking the wrong questions.

How do you analyze stakeholder interview data? Go through your notes while they're still fresh and group what you find into themes: areas of agreement, points of conflict, and things nobody could answer. A spreadsheet works fine for tracking themes across interviews. The conflicts and gaps are where your most important research questions will come from.