Latest / 5 Minute UX / Stakeholder Interviews: Uncovering Business Requirements
Transcript
- 0:08This lesson is Stakeholder Interviews: Uncovering Business
- 0:11Requirements. Let's get started.
- 0:19What if the project brief you're holding is actually describing
- 0:22the wrong problem entirely? Stakeholder interviews are the
- 0:24critical research activity designed to surface project
- 0:26goals, constraints, success criteria, and organizational
- 0:29politics before a single kickoff meeting occurs. These
- 0:31conversations allow practitioners to understand the
- 0:33history and context, ensuring the final solution addresses the
- 0:36real problems plaguing the organization rather than just
- 0:38the symptoms listed in a brief. You cannot afford to miss the
- 0:41hidden context that defines true project success. By engaging
- 0:44various groups, designers not only gather essential
- 0:46requirements but also foster a sense of ownership among
- 0:48stakeholders, which increases the likelihood of buy-in for the
- 0:51final solution. These sessions typically last between thirty to
- 0:53sixty minutes, so every minute must be tightly structured to
- 0:56respect stakeholder schedules while uncovering unstated
- 0:58business needs. Imagine walking into a kickoff workshop already
- 1:01armed with the organization's language and culture. This
- 1:04preparation transforms raw data into actionable intelligence,
- 1:06allowing you to challenge initial assumptions and align
- 1:09project direction with actual business needs. You will learn
- 1:11to identify the diverse mix of stakeholders required to ensure
- 1:14all relevant perspectives and frustrations are represented,
- 1:16setting the stage for a truly informed project scope.
- 1:25By the end of this section, you'll be able to identify the
- 1:27diverse mix of stakeholders required to ensure all relevant
- 1:30perspectives are represented. You must map out these groups
- 1:32before scheduling, because involving many different voices
- 1:35is essential for securing their buy-in for the final solution.
- 1:37Your primary goal is to uncover unstated business needs,
- 1:40organizational culture, and language to inform project
- 1:42scope. This means you need to dig deeper than the symptoms
- 1:45listed in a project brief to find the real problem. Without
- 1:47this context, your solution might address the wrong issue
- 1:49entirely. You'll also learn to describe the structure for
- 1:52organizing topics and questions to maximize value within a
- 1:5430-to-60-minute timeframe. Interviews typically last 30 to
- 1:5760 minutes and must be tightly structured to respect
- 1:59stakeholder schedules. A clear structure keeps the conversation
- 2:02productive without overrunning their valuable time. Finally,
- 2:04we'll apply active listening techniques to capture
- 2:06organizational language and culture while distinguishing
- 2:09real problems from symptoms. This requires paying attention
- 2:11to details and remaining flexible to explore emerging
- 2:13themes during the discussion. These insights allow you to
- 2:16align project direction with the actual needs of the business.
- 2:26Begin by mapping out the diverse groups within your organization
- 2:29who hold relevant knowledge or frustrations regarding the
- 2:31project. You must identify the diverse mix of stakeholders
- 2:33required to ensure all relevant perspectives and frustrations
- 2:36are represented. This selection ensures no critical viewpoint is
- 2:38missed before you even schedule the first meeting. Involving
- 2:40many different groups makes each group feel heard, which is
- 2:43essential for securing their buy-in. When people feel
- 2:45represented, they are far more likely to support the final
- 2:47solution. So, your participant list must reflect the full
- 2:49spectrum of organizational voices. Next, create a clear
- 2:52structure for topics and questions using categorization
- 2:54to hit key areas without prolonging the conversation. You
- 2:56need to organize your inquiry effectively because stakeholders
- 2:58often have tight schedules and many responsibilities. This
- 3:01structure allows you to cover the necessary ground within a
- 3:03strict thirty-to-sixty-minute session. Describe the structure
- 3:05for organizing topics and questions to maximize value
- 3:08within a 30-to-60-minute timeframe. A categorized list
- 3:10acts as your roadmap, preventing the discussion from drifting
- 3:12into unproductive tangents. Keep the focus tight so you respect
- 3:15their time while extracting maximum insight. During the
- 3:17interview, apply active listening techniques to capture
- 3:19organizational language and culture while distinguishing
- 3:21real problems from symptoms. Listen closely to how they speak
- 3:24about their work, because that language reveals the true
- 3:26context of the challenge. This deep listening helps you uncover
- 3:28the real problem the project needs to solve. Your goal is to
- 3:31surface project goals, constraints, and organizational
- 3:33politics to inform project scope. By synthesizing these
- 3:35findings with your own expertise, you can redefine the
- 3:37project's real problem before the kickoff workshop. This
- 3:39preparation ensures you enter the workshop fully informed and
- 3:42ready to lead.
- 3:49Let's say you have a thirty-to- sixty-minute session scheduled
- 3:52with a key stakeholder. Your job is to lead the discussion using
- 3:54your prepared structure while remaining flexible to explore
- 3:57emerging themes. You must manage this time strictly because
- 3:59stakeholders have tight schedules and many
- 4:01responsibilities. This balance ensures you cover all necessary
- 4:04topics without overrunning their day. While asking your
- 4:06questions, you must actively listen to learn about the
- 4:08organization's business, culture, and language. This is
- 4:10your time to do on-the-ground research to arm yourself with
- 4:13the necessary information around the new project. Paying
- 4:15attention to these details allows you to capture the true
- 4:18context that defines the work ahead. Here is the critical
- 4:20part: pay attention to details to uncover the real problem the
- 4:22project needs to solve. Often, this real problem differs
- 4:25significantly from the one listed in the project brief or
- 4:27statement of work. You are looking for the actual issues
- 4:29plaguing the organization rather than just the symptoms. Once
- 4:32you finish the interview, you must add what you have learned
- 4:35to your own past experiences and expertise. This synthesis allows
- 4:37you to come to kickoff workshops more informed and prepared to
- 4:40speak to specific problems. By integrating these insights, you
- 4:42ensure the final solution addresses the real needs of the
- 4:45business. The tangible output of this process is a set of
- 4:47insights that directly feed into the project requirements. You
- 4:50now have plenty of content to use during workshops or in later
- 4:52sessions to align project direction. This depth of
- 4:54knowledge ensures you are solving the right problem from
- 4:57day one.
- 5:04Pause and think about your last project kickoff. Did you enter
- 5:07that room ready to point out the real problem, or were you just
- 5:10addressing surface-level symptoms? The source material is
- 5:12clear: you must combine newly gathered stakeholder insights
- 5:15with your own professional experience to form a holistic
- 5:17view. This integration is what separates a generic meeting from
- 5:20a strategic intervention. Now, consider how you will feed these
- 5:23insights directly into your project requirements and the
- 5:25kickoff workshop. When you align the project direction with
- 5:28actual business needs, you move beyond the initial statement of
- 5:31work. You are no longer guessing at constraints or success
- 5:33criteria. Instead, you are armed with the true organizational
- 5:36context that defines the project's real scope. Finally,
- 5:38reflect on the diverse mix of stakeholders you engaged. Did
- 5:41you ensure all relevant perspectives and frustrations
- 5:43were represented in your synthesis? If you can answer
- 5:46yes, you have successfully surfaced the organizational
- 5:48politics that often hide in plain sight. This is how you
- 5:51ensure your solution addresses the root cause, not just the
- 5:53symptoms.
- 5:57Welcome to The Take. I'm joined by a fellow practitioner and
- 6:00together we're going to dig into Stakeholder Interviews:
- 6:02Uncovering Business Requirements — what it means in practice and
- 6:05what's worth remembering.
- 6:08[HOST] I'm still wrestling with that idea of distinguishing the
- 6:11real problem from the symptoms listed in the brief. [LEARNER]
- 6:13That's the hardest part because stakeholders often arrive with a
- 6:16solution already baked into their description of the
- 6:19problem. [HOST] Exactly, and if we don't catch that early, we
- 6:22just end up validating a bad decision instead of solving the
- 6:24actual issue. [LEARNER] So the thirty-minute window becomes
- 6:27even tighter when you realize you have to dismantle their
- 6:30assumption before you can start mapping the real scope. [HOST]
- 6:33It forces us to use active listening not just to gather
- 6:35data, but to decode the organizational politics hiding
- 6:38behind their language. [LEARNER] I've found that listening for
- 6:41their specific jargon is the only way to spot where the brief
- 6:43is missing the cultural context. [HOST] And now with AI, we can
- 6:46transcribe those sessions instantly to flag recurring
- 6:49terms that might signal a deeper political constraint. [LEARNER]
- 6:52That's useful, but I worry AI might smooth over the awkward
- 6:54silences or the hesitation that often hints at what they aren't
- 6:57saying. [HOST] True, the tool helps with the synthesis, but
- 7:00the human still needs to read the room to understand the
- 7:03unspoken risks. [LEARNER] It comes down to whether we trust
- 7:05the algorithm to catch the nuance or if we rely on our own
- 7:08gut to spot the friction. [HOST] We need both, because the
- 7:11algorithm finds the pattern, but only we can decide if that
- 7:14pattern represents a real business blocker. [LEARNER] So
- 7:16the goal isn't to replace our intuition with data, but to use
- 7:19that data to challenge our own biases about the project scope.
- 7:22[HOST] Precisely, and that preparation is what lets us walk
- 7:25into the kickoff ready to redefine the problem before the
- 7:27meeting even starts.