Latest / 5 Minute UX / Listening to Stakeholders: A Practical Guide
Transcript
- 0:09This lesson is Listening to Stakeholders: A Practical Guide.
- 0:13Let's get started.
- 0:20You control the flow of discussion by passing the
- 0:22virtual microphone around the room, which means you are
- 0:25actively managing who speaks next. This isn't about shouting
- 0:28over people; it's about subtle, non-verbal cues that signal who
- 0:31has the floor without interrupting the natural rhythm
- 0:33of the session. You maintain this control through four
- 0:36specific mechanisms: eye contact, volume of speech, arm
- 0:38movements, and orientation of body. Eye contact is your
- 0:41primary tool for inviting a stakeholder to speak, while a
- 0:43slight decrease in volume can signal that it is time to pause.
- 0:46Arm movements help you physically direct the
- 0:48conversation toward one person and away from another, creating
- 0:51a clear visual path for the dialogue. Most importantly, you
- 0:54use body orientation to include or exclude participants from the
- 0:57current thread of conversation, turning slightly to engage the
- 0:59next speaker. These cues work together to keep the session
- 1:02moving forward smoothly, ensuring that every voice is
- 1:05heard in the right order. Once you have mastered this physical
- 1:07control, you can focus on how to handle the content of what is
- 1:10being said.
- 1:17Once you’ve established control with those non-verbal cues,
- 1:20you’ll encounter the inevitable moments of silence or
- 1:22disagreement that test your facilitation skills. The goal
- 1:25isn’t to force conversation, but to guide it back to productive
- 1:28territory without creating interpersonal friction. When a
- 1:30stakeholder remains silent after being called on, the first step
- 1:33is to repeat the question explicitly. This simple recovery
- 1:36strategy acknowledges that they might not have understood the
- 1:38prompt, or perhaps weren’t listening closely to the
- 1:41previous statements. By restating the question clearly,
- 1:43you give them a fair chance to engage without assuming
- 1:46disinterest or resistance. It’s a low-pressure way to re-engage
- 1:48someone who has drifted out of the flow, ensuring everyone
- 1:51stays aligned with the session’s objectives. However, silence is
- 1:54often the easier challenge compared to handling
- 1:56disagreement among stakeholders. The mistake many moderators make
- 1:59is framing differences of opinion as direct disagreements
- 2:01between individuals. This approach inevitably triggers
- 2:04defensiveness and shifts the focus from the product problem
- 2:06to personal conflict. For instance, asking Bob, “We
- 2:09haven’t heard from you yet. What do you think about what Chris
- 2:12just said?” forces him to take a stance against Chris’s opinion.
- 2:14This phrasing invites criticism rather than insight, turning a
- 2:17collaborative session into a debate where egos compete rather
- 2:20than ideas merge. You want to avoid this trap because it
- 2:22derails the listening session and damages team dynamics.
- 2:25Instead, apply the technique of reframing disagreement to keep
- 2:28the conversation focused on experiences rather than
- 2:30reactions. A much more effective approach is to ask, “How about
- 2:33you, Bob? What kinds of experiences have you had with
- 2:35this subject?” This correct phrasing invites Bob to share
- 2:38his personal history and observations, which adds
- 2:40valuable context without requiring him to agree or
- 2:42disagree with Chris. By shifting the focus to individual
- 2:45experiences, you transform potential conflict into a rich
- 2:47collection of diverse perspectives. This method turns
- 2:49differences of opinion into data points for understanding the
- 2:52user landscape. As you master these verbal adjustments, you’ll
- 2:55find that structuring participation for non-
- 2:57researchers becomes easier, allowing everyone to contribute
- 3:00meaningfully without feeling disruptive.
- 3:08When non-design stakeholders observe listening sessions, they
- 3:11often feel excluded or disruptive because they lack the
- 3:13researcher’s toolkit. You need to provide structure and
- 3:16direction so they feel part of the team rather than in the way.
- 3:19Consider inviting them to influence the interview script
- 3:21or tasks before the session begins. This allows them to
- 3:24integrate their specific anecdotes and concerns into the
- 3:27questions you ask. Think about how you might adapt your current
- 3:30script to include a stakeholder’s unique
- 3:32perspective. By letting them shape the inquiry, you validate
- 3:34their expertise and reduce resistance to the process. This
- 3:37shifts their role from passive observer to active contributor,
- 3:40which means they engage more deeply with the findings.
- 3:42Reflect on how this structured participation changes the
- 3:45dynamic when they hear customer feedback that aligns with their
- 3:48own experiences. You’re applying recovery strategies for handling
- 3:51silence and stakeholder exclusion by giving them a
- 3:53formal voice early on. The goal is to ensure they see their
- 3:56input reflected in the work, which builds trust and minimizes
- 3:59later pushback.
- 4:06You’ll hit three common pitfalls, but each has a
- 4:08specific recovery strategy that keeps the session moving
- 4:11forward. First, stakeholders often misunderstand questions or
- 4:13simply weren’t listening to the previous statements. The
- 4:16recovery is simple: repeat the question explicitly. This clears
- 4:19up confusion without calling anyone out for being
- 4:21inattentive. Second, differences of opinion can quickly turn into
- 4:24interpersonal conflict if you frame them as disagreements
- 4:27between individuals. Avoid asking Bob what he thinks about
- 4:30Chris’s comment. Instead, reframe the question to focus on
- 4:33experiences or specific topics. Ask, “What kinds of experiences
- 4:35have you had with this subject?” This shifts the focus back to
- 4:38the work. Third, non-design stakeholders may feel excluded
- 4:41or disruptive during research sessions. Provide structure and
- 4:44direction so they feel part of the team rather than in the way.
- 4:47Invite them to influence interview scripts or tasks to
- 4:49integrate their anecdotes and concerns. These recoveries
- 4:52maintain momentum and preserve relationships during high-stakes
- 4:55feedback loops. With these strategies in place, you’re
- 4:58ready to apply these techniques to milestone outputs.
- 5:07You apply these techniques during Discovery to define the
- 5:10product space, and again during Define to prioritize
- 5:13requirements based on relative importance and effort.
- 5:15Structured participation during beta feedback ensures you gather
- 5:18specific insights from potential users. Whether working in
- 5:21Waterfall or Agile, your sign- off points depend on clear,
- 5:24conflict-free discussions that avoid interpersonal friction.
- 5:27Effective facilitation leads to prioritized lists driven by
- 5:29data, not by who speaks loudest in the room. By controlling flow
- 5:32and reframing disagreement, you turn stakeholder input into a
- 5:35reliable foundation for design decisions. Now, when you sit
- 5:38down for your next listening session, you’ll know exactly how
- 5:41to guide the conversation toward productive outcomes.
- 5:47Welcome to The Take. I'm joined by a fellow practitioner and
- 5:50together we're going to dig into Listening to Stakeholders: A
- 5:53Practical Guide — what it means in practice and what's worth
- 5:56remembering.
- 5:58[HOST] I found the bit about reframing disagreement to focus
- 6:01on experience rather than opinion particularly powerful.
- 6:04It shifts the dynamic from a debate to data collection.
- 6:07[LEARNER] Absolutely. Asking "what do you think about Chris's
- 6:10point" is a trap. It forces people into defensive positions
- 6:14immediately. [HOST] Exactly. When you ask for their personal
- 6:17history with the problem, you bypass the ego. You get richer
- 6:20insights without the friction. [LEARNER] But let's be honest.
- 6:23Executives often don't have personal user history. They only
- 6:27have business metrics in mind. [HOST] That’s where the non-
- 6:30verbal flow control becomes critical. You have to physically
- 6:33guide the conversation away from abstract metrics. [LEARNER] I
- 6:37struggle with that. Turning my body slightly feels like a
- 6:40subtle power move. Some stakeholders sense it and get
- 6:43annoyed. [HOST] It’s not about power. It’s about clarity. If
- 6:46you don’t signal who speaks next, the loudest voice wins.
- 6:49[LEARNER] True. But in hybrid meetings, body orientation
- 6:52doesn’t translate well to the screen. The remote participants
- 6:55are always excluded. [HOST] That’s a valid edge case. You
- 6:58have to use verbal cues more explicitly when the room is
- 7:02split. [LEARNER] Right. I’ve started using AI to transcribe
- 7:05sessions in real time. It helps me spot when I’m favoring one
- 7:08speaker over another. [HOST] Interesting. Do you use it to
- 7:11analyze sentiment or just to keep a record of who spoke?
- 7:14[LEARNER] Mostly to catch blind spots. The AI flags when I
- 7:17interrupt or when silence stretches too long. It’s an
- 7:20objective mirror. [HOST] That’s a clever adaptation. It turns
- 7:24facilitation from an art into a measurable practice. [LEARNER]
- 7:27It definitely reduces the cognitive load. I can focus on
- 7:30the nuance instead of tracking the clock. [HOST] Well, if we
- 7:33can externalize the monitoring, we free up mental space for
- 7:37empathy. That’s the ultimate goal.