Latest / 5 Minute UX / Finding the Right Stakeholders: What It Is and Why It Matters
Transcript
- 0:08This lesson is Finding the Right Stakeholders: What It Is and Why
- 0:11It Matters. Let's get started.
- 0:19Projects often fail to capture diverse perspectives, which
- 0:21leads directly to incomplete requirements that miss user
- 0:24needs. When specific individuals are not identified early on, the
- 0:27team gathers a narrow slice of knowledge rather than the full
- 0:29picture of project-related ideas and frustrations. This gap means
- 0:32viewpoints remain silent, creating blind spots that the
- 0:34final design cannot address because the input sources were
- 0:37never properly identified. Without early involvement,
- 0:39stakeholders frequently lack buy-in for the final solution,
- 0:42viewing it as something imposed upon them rather than co-
- 0:44created. Participation is the mechanism that secures this
- 0:47commitment, ensuring different groups feel they have genuinely
- 0:49had their say in shaping the outcome. When people are
- 0:52excluded from the process, their resistance can undermine the
- 0:54project’s success even if the technical execution is flawless.
- 0:57Unclear objectives at the start of a project create ambiguity
- 0:59about the broader business context, leaving the team
- 1:02guessing at priorities. Involving the right stakeholders
- 1:04helps clarify this ambiguity by grounding the work in real
- 1:07business-related constraints and opportunities. This early
- 1:09engagement clarifies goals, preventing the team from
- 1:11building solutions that miss the mark entirely. Responsibility
- 1:14gaps also emerge when it is unclear who schedules and
- 1:16structures stakeholder interactions, causing valuable
- 1:19time to slip through the cracks. Defining who gathers whom early
- 1:21on ensures an efficient process, eliminating the confusion that
- 1:24often paralyzes initial planning stages. Once these
- 1:26responsibility gaps are resolved, we can move toward
- 1:28defining stakeholder identification as a deliberate
- 1:31practice.
- 1:37Stakeholder identification is the process of identifying and
- 1:40involving specific individuals or groups to gather relevant
- 1:42project-related ideas, needs, knowledge, and frustrations. You
- 1:45are capturing diverse perspectives from various points
- 1:47of view, which feeds directly into your project requirements
- 1:49and helps secure buy-in for the final solution. This early
- 1:52involvement clarifies ambiguity when objectives are unclear and
- 1:54ensures different groups feel they have had their say. The
- 1:57process also involves determining who is primarily
- 1:59responsible for gathering and scheduling these stakeholders
- 2:01into the most productive groups. You must define who gathers whom
- 2:04early on to resolve responsibility gaps within the
- 2:06project team and ensure an efficient workflow. This
- 2:08includes coordinating with both internal team members and
- 2:10external parties such as partners and vendors. By
- 2:12establishing clear ownership of these interactions, you prevent
- 2:15the common issue where responsibilities during
- 2:17requirements gathering remain unclear. Defining these roles
- 2:19upfront allows the team to focus on understanding the business-
- 2:22related context rather than figuring out who should be in
- 2:24the room. With the right people identified and scheduled, you
- 2:27can move toward understanding the contextual factors that will
- 2:29shape your engagement strategy.
- 2:36Think back to your last project, where you had to decide how to
- 2:39engage the team. You likely adjusted your approach based on
- 2:41whether everyone was in the same room or scattered across time
- 2:44zones. That same instinct applies here, because knowing
- 2:46the methodology is a prerequisite for understanding
- 2:48when and how to involve others. The choice of methodology
- 2:51depends on the structure and location of the project team,
- 2:53which means your engagement strategy shifts if people are
- 2:56remote. You must also consider the technologies being used on
- 2:58the project, since complex tools often require more specialized
- 3:01input from technical stakeholders. Furthermore, the
- 3:03degree to which collaboration is part of the company’s culture
- 3:05dictates the approach you take to gather requirements. If your
- 3:08organization values open dialogue, you might host larger
- 3:10workshops, whereas a hierarchical culture might
- 3:12require one-on-one interviews. These contextual factors
- 3:15determine how you structure those early conversations. As
- 3:17you navigate these variables, you’ll see how identifying the
- 3:20right people differs from simply managing the meeting itself.
- 3:28Distinguish stakeholder identification from related
- 3:30concepts to ensure the process remains efficient and focused.
- 3:33Many teams confuse the act of finding people with the act of
- 3:35managing them, which creates confusion about who is
- 3:37responsible for what. You must define specific responsibilities
- 3:40for team members early on, particularly determining who
- 3:42schedules and structures these interactions. This clarity
- 3:44resolves responsibility gaps and ensures that the right voices
- 3:47are heard without administrative friction. Facilitation manages
- 3:49the meeting dynamics, whereas finding stakeholders manages the
- 3:52composition of the group itself. While facilitation skills keep
- 3:54meetings on topic and ensure participation, they do not
- 3:56determine who should actually be in the room. Finding the right
- 3:59stakeholders is the distinct work of identifying and
- 4:01involving specific individuals to gather their unique needs and
- 4:03frustrations. If you mix these roles, you may facilitate a
- 4:06productive meeting with the wrong people, rendering the
- 4:08output useless for the project’s actual requirements. Information
- 4:11Architecture is the structural output or skill set, while
- 4:13finding stakeholders is the identification of the people
- 4:15providing the input. You need a knack for clear categorization
- 4:18to structure topics and questions, but that is separate
- 4:20from knowing who holds the relevant business context. IA
- 4:22organizes the data after it is collected, but stakeholder
- 4:24identification locates the live sources of that data in the
- 4:27first place. Understanding this difference prevents you from
- 4:29designing a perfect interview structure and then asking the
- 4:31wrong people to fill it out. Personas humanize research data
- 4:34with names and photos, such as distinguishing "Nicolle" from a
- 4:36generic "Mid-30s Blonde Professional Mom." Stakeholders
- 4:38are the live sources of that data, not the composite
- 4:41characters we create to represent them later. Personas
- 4:43are a tool for empathy and design reference, but they do
- 4:45not replace the need to engage actual people who have real
- 4:47frustrations and ideas. You cannot build a persona without
- 4:50first finding the stakeholders who provide the raw material for
- 4:52those humanized profiles. By distinguishing these concepts,
- 4:54you secure buy-in and clarify ambiguity from the very start of
- 4:57the project. You now know how to define stakeholder
- 4:59identification and separate it from facilitation, Information
- 5:01Architecture, and persona creation. This precision ensures
- 5:04you feed requirements with diverse perspectives rather than
- 5:06assumptions or empty structures. When you begin your next
- 5:08project, you will know exactly who to invite, who to schedule,
- 5:11and how to keep those roles distinct.
- 5:15Welcome to The Take. I'm joined by a fellow practitioner and
- 5:18together we're going to dig into Finding the Right Stakeholders:
- 5:21What It Is and Why It Matters — what it means in practice and
- 5:24what's worth remembering.
- 5:26[HOST] The distinction between facilitation and stakeholder
- 5:29identification hit home for me today. We often confuse running
- 5:32a good meeting with actually finding the right people to
- 5:35invite. [LEARNER] Exactly. I’ve sat in so many well-run
- 5:38workshops that produced zero value because the wrong voices
- 5:41were in the room. It’s a classic case of optimizing the process
- 5:44while ignoring the input. [HOST] That’s the trap. We think clear
- 5:47structure solves ambiguity, but structure only helps if you’ve
- 5:50already identified who holds the context. You can’t facilitate
- 5:53your way out of missing key perspectives. [LEARNER] True.
- 5:56And in my last project, we assumed the product owner had
- 5:59all the answers. We didn’t dig for the support staff who
- 6:02actually handled the edge cases. [HOST] Those support staff
- 6:05members are the ones with the real frustrations. Without them,
- 6:08your requirements are just assumptions dressed up as facts.
- 6:11It creates that blind spot we talked about. [LEARNER] It does.
- 6:14I’m curious if AI changes how we do this initial mapping. Could a
- 6:17tool scan internal docs to suggest who we’re missing before
- 6:20we even start scheduling? [HOST] It’s tempting to think AI can
- 6:24automate the discovery phase. But algorithms might miss the
- 6:27informal influencers who don’t have official titles but hold
- 6:30the tribal knowledge. [LEARNER] That’s a fair point. AI might
- 6:33find the org chart, but it won’t find the person everyone
- 6:36actually goes to for help. We still need human intuition to
- 6:38spot those hidden stakeholders. [HOST] Right. AI is a great
- 6:41filter, but it’s a poor judge of social dynamics and unspoken
- 6:45influence. We need to keep the human in the loop for that final
- 6:48verification step. [LEARNER] So the tech helps us cast a wider
- 6:51net, but we still have to decide who actually matters. It shifts
- 6:54the burden from finding names to validating relevance. [HOST]
- 6:57Precisely. The tool gives you a list, but you provide the
- 7:00judgment. That keeps the process grounded in real business
- 7:03context rather than just data points. [LEARNER] I like that
- 7:06framing. It makes the designer’s role more critical, not less.
- 7:09We’re curating the reality, not just collecting it. [HOST] And
- 7:12that curation is what turns vague goals into actionable
- 7:15understanding. We’ll keep that distinction sharp as we move
- 7:18into the next phase.