Latest / 5 Minute UX / Interview Stakeholders to Build Buy-In
Transcript
- 0:08This lesson is Interview Stakeholders to Build Buy-In.
- 0:11Let's get started.
- 0:19Stakeholder interviews do two things at once. The primary goal
- 0:21is to gather project-related ideas, needs, knowledge, and
- 0:24frustrations from various points of view. This feeds directly
- 0:27into the project requirements. The secondary benefit is
- 0:29securing buy-in. When diverse groups feel they have had a say
- 0:32in the project, their commitment to the final solution increases.
- 0:35This dual purpose matters because stakeholders are not
- 0:37users. Stakeholders have more influence over goals and
- 0:39objectives than users do. They care less about the user
- 0:42experience and more about the business outcomes. So when you
- 0:45interview them, you are building requirements and building
- 0:47support simultaneously. The work requires a structured
- 0:50stakeholder interview process to gather requirements and secure
- 0:52buy-in. You need to identify the dual purpose of stakeholder
- 0:55interviews: gathering requirements and securing buy-
- 0:57in. This is the foundation for the entire process. Once you
- 1:00understand this dual outcome, the next step is preparing for
- 1:03those conversations.
- 1:11The first move in preparing for these conversations is
- 1:13identifying the right people to talk to. You need diverse
- 1:15perspectives to capture the full scope of the project's impact,
- 1:18but stakeholders often have tight schedules and competing
- 1:20responsibilities. If you are struggling to build that list,
- 1:22the most effective step is to ask each current stakeholder a
- 1:25simple question: who else should I be speaking to? That single
- 1:27prompt grows your network of diverse perspectives and
- 1:29surfaces voices you might have missed on your own. These
- 1:31interviews happen before the kickoff workshop, which sets the
- 1:34critical context for your entire approach. You are using this
- 1:36time to learn about the organization’s specific
- 1:38business, culture, and language. This groundwork allows you to
- 1:41speak to the real problems the project needs to solve, rather
- 1:43than just the issues listed in the initial project brief.
- 1:45Without that cultural and business understanding, your
- 1:47dialogue remains surface-level and misses the deeper
- 1:49organizational dynamics at play. Next, you structure the
- 1:52conversation by creating an interview guide that functions
- 1:54like a script for a user research session. You document
- 1:56the specific questions needed to prepare for the kick-off
- 1:58meeting, aiming for approximately twelve questions
- 2:00in total. This quantity gives you enough depth to cover key
- 2:03areas while keeping the interaction focused and
- 2:05manageable. The structure relies on clear categorization of
- 2:07topics, which draws heavily on information architecture
- 2:09principles to organize your thinking. Executing this guide
- 2:11requires specific facilitation skills to keep the meeting on
- 2:14topic while maintaining active listening. You must attend to
- 2:16the details of what is being said, ensuring you capture
- 2:18nuances that might not appear in written documents. This
- 2:20preparation stage is about building a foundation of
- 2:22understanding that informs how you lead the actual
- 2:24conversations. Once the guide is ready and the stakeholder list
- 2:27is finalized, you are positioned to conduct the one-on-one
- 2:29interviews that drive the process forward.
- 2:38You have your script, your twelve questions, and your list
- 2:40of people to call. Now you block out forty-five to sixty minutes
- 2:43for each conversation. That time window is specific, and it
- 2:46matters because it forces you to hit key areas without prolonging
- 2:48the discussion. You are not running a workshop; you are
- 2:51having a one-on-one where every topic relates directly to the
- 2:53assigned project. If the conversation drifts into general
- 2:56organizational politics, you steer it back to the specific
- 2:58needs and frustrations of this initiative. The goal is to
- 3:01cover as much ground as possible within that hour, so you need to
- 3:04be decisive about which questions you prioritize. You
- 3:06don’t have time to explore every tangent, so you focus on the
- 3:08core issues that will shape the requirements. When the clock
- 3:11starts to run low, you don’t rush the ending. Instead, you
- 3:13ask a specific question: is there time for a follow-up
- 3:16interview to continue the discussion or cover additional
- 3:18topics? If the stakeholder found value in the first
- 3:20conversation, they will likely agree to that follow-up. This
- 3:23simple ask does two things. It ensures you capture any critical
- 3:26details you might have missed, and it reinforces their sense of
- 3:28involvement in the process. That ongoing engagement is what turns
- 3:31a single interview into a source of sustained buy-in. You leave
- 3:34the room with a clear path to finish the conversation, which
- 3:36means you walk into the kickoff workshop with a more complete
- 3:39picture of the landscape.
- 3:48You’ve collected the voices, now you must distill them. Take what
- 3:51you learned from those one-on- one conversations and blend it
- 3:53with your own past experiences and expertise. This synthesis
- 3:56means you walk into the kickoff workshop already informed, not
- 3:59just with a transcript. The goal is to identify high-level
- 4:01requirements that serve as the project’s foundation, not a
- 4:04detailed spec sheet. Keep that list tight. Limit it to eight to
- 4:07twelve items, because anything more pushes you into the weeds.
- 4:09It’s a constraint that forces clarity. You’re defining the
- 4:12shape of the solution, not its every detail. Once you have
- 4:14that shortlist, you need the room to agree on what matters
- 4:17most. Facilitate prioritization using an activity like dot
- 4:19voting, where participants place stickers on the requirements
- 4:22they value most. It turns abstract discussion into
- 4:24visible, shared data. Then, discuss the outcome to secure
- 4:27agreement, alignment, and commitment from everyone in the
- 4:29room. You’re not just picking a direction; you’re building a
- 4:32consensus that binds the team to the path forward. Think about
- 4:35the last time you held a prioritization meeting. Did the
- 4:37group actually commit to the top choices, or did the conversation
- 4:40just end? That’s the difference between a list and a decision.
- 4:46Welcome to The Take. I'm joined by a fellow practitioner and
- 4:48together we're going to dig into Interview Stakeholders to Build
- 4:51Buy-In — what it means in practice and what's worth
- 4:53remembering.
- 4:55[HOST] The twelve-question limit feels arbitrary until you
- 4:58realize it’s actually a constraint that forces clarity.
- 5:01[LEARNER] It does, but I struggle to drop good questions
- 5:04just to hit that number. [HOST] You have to prioritize the
- 5:07questions that change the solution, not the ones that just
- 5:10sound smart. [LEARNER] True. I usually keep the ones that
- 5:13validate my initial bias instead. [HOST] That’s the trap.
- 5:16Stakeholders wanna feel heard, not just confirmed. [LEARNER] So
- 5:20how do you decide which ones to cut without losing their trust?
- 5:23[HOST] You frame the interview around their specific pain
- 5:26points, not the project scope. [LEARNER] That makes sense. It
- 5:29shifts the focus from what we wanna what they need. [HOST]
- 5:32Exactly. And that’s where the follow-up ask becomes critical.
- 5:36[LEARNER] I often skip that because it feels like an extra
- 5:39burden on them. [HOST] It’s not a burden. It’s a signal that you
- 5:42value their input enough to continue. [LEARNER] I see. So
- 5:45it’s a relationship builder, not just a data point. [HOST]
- 5:48Precisely. It turns a transaction into a partnership.
- 5:51[LEARNER] That’s a mindset shift I need to make. [HOST] It is.
- 5:54And it’s where AI can help you analyze the patterns in those
- 5:58conversations. [LEARNER] Really? I thought AI was just for
- 6:01generating transcripts. [HOST] No. It can spot recurring themes
- 6:04across multiple interviews that you might miss. [LEARNER] That
- 6:07could save me hours of manual coding. [HOST] Yes. But you
- 6:10still need to interpret the context. AI gives you the data,
- 6:14you give it meaning. [LEARNER] So it’s a collaboration, not a
- 6:17replacement. [HOST] Always. The human insight is what drives the
- 6:20buy-in. [LEARNER] That’s a good reminder. I can lean on the
- 6:23tools, but I have to lead the conversation. [HOST] Absolutely.
- 6:27The structure supports the connection, not the other way
- 6:30around.