
Learners will execute a structured interview protocol to extract high-level project requirements while securing stakeholder commitment. This capability allows you to navigate diverse organizational perspectives and convert raw feedback into an aligned, prioritized list of 8-12 actionable items.
Learning Objective: By the end of this lesson, learners will be able to apply a structured stakeholder interview process to gather requirements and secure buy-in.
Transcript
Dual Outcome: Requirements and Buy-In
Stakeholder interviews do two things at once. The primary goal is to gather project-related ideas, needs, knowledge, and frustrations from various points of view. This feeds directly into the project requirements. The secondary benefit is securing buy-in. When diverse groups feel they have had a say in the project, their commitment to the final solution increases.
This dual purpose matters because stakeholders are not users. Stakeholders have more influence over goals and objectives than users do. They care less about the user experience and more about the business outcomes. So when you interview them, you are building requirements and building support simultaneously.
The work requires a structured stakeholder interview process to gather requirements and secure buy-in. You need to identify the dual purpose of stakeholder interviews: gathering requirements and securing buy-in. This is the foundation for the entire process.
Once you understand this dual outcome, the next step is preparing for those conversations.
Key Points:
Primary goal: Gather project-related ideas, needs, knowledge, and frustrations from various points of view.
Secondary benefit: Securing buy-in by ensuring diverse groups feel they have had a say in the project.
Distinction: Stakeholders have more influence over goals and objectives than users, with less focus on user experience.
Preparation: Stakeholder Identification and Guide Creation
The first move in preparing for these conversations is identifying the right people to talk to. You need diverse perspectives to capture the full scope of the project's impact, but stakeholders often have tight schedules and competing responsibilities. If you are struggling to build that list, the most effective step is to ask each current stakeholder a simple question: who else should I be speaking to? That single prompt grows your network of diverse perspectives and surfaces voices you might have missed on your own.
These interviews happen before the kickoff workshop, which sets the critical context for your entire approach. You are using this time to learn about the organization’s specific business, culture, and language. This groundwork allows you to speak to the real problems the project needs to solve, rather than just the issues listed in the initial project brief. Without that cultural and business understanding, your dialogue remains surface-level and misses the deeper organizational dynamics at play.
Next, you structure the conversation by creating an interview guide that functions like a script for a user research session. You document the specific questions needed to prepare for the kick-off meeting, aiming for approximately twelve questions in total. This quantity gives you enough depth to cover key areas while keeping the interaction focused and manageable. The structure relies on clear categorization of topics, which draws heavily on information architecture principles to organize your thinking.
Executing this guide requires specific facilitation skills to keep the meeting on topic while maintaining active listening. You must attend to the details of what is being said, ensuring you capture nuances that might not appear in written documents. This preparation stage is about building a foundation of understanding that informs how you lead the actual conversations. Once the guide is ready and the stakeholder list is finalized, you are positioned to conduct the one-on-one interviews that drive the process forward.
Key Points:
Action: Ask current stakeholders, “Who else should I be speaking to?” to grow the list of diverse perspectives.
Context: Conduct interviews prior to the kickoff workshop to learn about the organization’s business, culture, and language.
Structure: Create a script with approximately 12 questions to prepare for the kick-off meeting.
Skills: Apply clear categorization of topics, facilitation skills to keep meetings on topic, and active listening.
Execution: 45-60 Minute One-on-One Conversations
You have your script, your twelve questions, and your list of people to call. Now you block out forty-five to sixty minutes for each conversation. That time window is specific, and it matters because it forces you to hit key areas without prolonging the discussion. You are not running a workshop; you are having a one-on-one where every topic relates directly to the assigned project. If the conversation drifts into general organizational politics, you steer it back to the specific needs and frustrations of this initiative.
The goal is to cover as much ground as possible within that hour, so you need to be decisive about which questions you prioritize. You don’t have time to explore every tangent, so you focus on the core issues that will shape the requirements. When the clock starts to run low, you don’t rush the ending. Instead, you ask a specific question: is there time for a follow-up interview to continue the discussion or cover additional topics?
If the stakeholder found value in the first conversation, they will likely agree to that follow-up. This simple ask does two things. It ensures you capture any critical details you might have missed, and it reinforces their sense of involvement in the process. That ongoing engagement is what turns a single interview into a source of sustained buy-in. You leave the room with a clear path to finish the conversation, which means you walk into the kickoff workshop with a more complete picture of the landscape.
Key Points:
Duration: Block out 45 to 60 minutes for each interview to hit key areas without prolonging the conversation.
Format: Conduct one-on-one conversations where all topics discussed relate directly to the assigned project.
Closing Action: Ask the stakeholder if there is time for a follow-up interview to continue the discussion or cover additional topics.
Synthesis: Defining 8-12 High-Level Requirements
You’ve collected the voices, now you must distill them. Take what you learned from those one-on-one conversations and blend it with your own past experiences and expertise. This synthesis means you walk into the kickoff workshop already informed, not just with a transcript. The goal is to identify high-level requirements that serve as the project’s foundation, not a detailed spec sheet.
Keep that list tight. Limit it to eight to twelve items, because anything more pushes you into the weeds. It’s a constraint that forces clarity. You’re defining the shape of the solution, not its every detail.
Once you have that shortlist, you need the room to agree on what matters most. Facilitate prioritization using an activity like dot voting, where participants place stickers on the requirements they value most. It turns abstract discussion into visible, shared data. Then, discuss the outcome to secure agreement, alignment, and commitment from everyone in the room. You’re not just picking a direction; you’re building a consensus that binds the team to the path forward.
Think about the last time you held a prioritization meeting. Did the group actually commit to the top choices, or did the conversation just end? That’s the difference between a list and a decision.
Key Points:
Synthesis: Combine interview findings with past experiences and expertise to come to kickoff workshops more informed.
Constraint: Limit the requirements list to 8 to 12 items; anything more is considered too detailed or "in the weeds."
Prioritization: Facilitate prioritization using activities like "dot voting" to get agreement, alignment, and commitment.
Weitere Episoden von „5 Minute UX“



Verpasse keine Episode von “5 Minute UX” und abonniere ihn in der kostenlosen GetPodcast App.








