Latest / 5 Minute UX / Planning Your Stakeholder Requirements Meetings
Transcript
- 0:08This lesson is Planning Your Stakeholder Requirements
- 0:11Meetings. Let's get started.
- 0:19Before you schedule a single meeting or draft a question, you
- 0:21must define two specific roles within your team. First,
- 0:24identify who is primarily responsible for gathering and
- 0:26scheduling the right business stakeholders into the most
- 0:29productive groups. This person handles the logistics of who
- 0:32sits in the room, ensuring internal and external partners
- 0:34are included where they add value. Second, determine who
- 0:37creates the structure of topics and questions for those
- 0:39meetings. This person builds the agenda, deciding what needs to
- 0:42be asked and in what order. You might think you can just wing
- 0:45it, but defining these responsibilities early prevents
- 0:47inefficiency in the gathering process. When roles are blurry,
- 0:50you end up with duplicated work or critical stakeholders left
- 0:53out entirely. The source notes that creating the topic
- 0:55structure is a great collaborative exercise for the
- 0:57team, provided you have the time to do it properly. If you don't,
- 1:00one person takes the lead to keep the process moving. Once
- 1:03you have these two roles locked in, you can move to the next
- 1:06step. You need to calibrate the level of detail for each group,
- 1:08which is where the real planning work begins.
- 1:17Decide up front on the level of detail you're aiming for,
- 1:19because that single decision shapes how the entire meeting
- 1:22unfolds. The source distinguishes between two very
- 1:24different scenarios, and your plan must reflect which one
- 1:27you're facing. For large, one- time groups, such as members of
- 1:29various departments coming together once, aim to gather
- 1:32ideas rather than solve problems. Avoid spending too
- 1:34much time diving into gritty details during that session,
- 1:37because you don't have the bandwidth to investigate every
- 1:39thread with everyone present. For smaller or repeated
- 1:42sessions, allow for deeper investigation into specific
- 1:44needs. This is where you can ask targeted questions, like how the
- 1:47sales process differs for different product lines, and
- 1:49really dig into the mechanics. Even if your questions overlap
- 1:52between groups, you still create a different plan for each one.
- 1:55The structure stays the same, but the depth and focus shift to
- 1:58match the group's size and frequency. This ensures you
- 2:00respect the time of everyone in the room.
- 2:08When you apply the group- specific planning method, you
- 2:11need to create a structured agenda that defines exactly who
- 2:13is in the room. This means listing specific participants by
- 2:16their roles, not just their names. For a sales department
- 2:18meeting, that looks like Inside Sales with Jenny Bee, Tracy Kim,
- 2:21and Joseph Arnold, plus Lead Management with Kevin Abernathy
- 2:24and Cat Parnell. Naming them this way clarifies whose
- 2:26perspective you are capturing. It prevents the meeting from
- 2:29drifting into generalities when you need specific operational
- 2:31insights from a particular tier of the organization. Next, you
- 2:34set a concrete time frame, such as two hours, and attach a clear
- 2:37objective to that block. The objective for this sales group
- 2:39is to understand the current sales process and identify
- 2:42issues and opportunities for how the web could better support
- 2:45that process. Having a fixed duration forces you to be
- 2:47selective about what you ask. A vague goal like "discuss sales"
- 2:50leads to rambling, but a specific objective anchors every
- 2:52question that follows. This structure keeps the conversation
- 2:55focused on actionable insights rather than broad brainstorming.
- 2:58Before the first question is asked, you include background
- 3:00context to align everyone’s understanding. In this scenario,
- 3:03the team reviewed a PowerPoint presentation on the purchasing
- 3:05process, which provided background on how purchasing
- 3:08decisions are made. This step ensures that the sales team is
- 3:10not explaining basic mechanics to the design team. Instead, the
- 3:13time is spent on the nuances and pain points. It creates a shared
- 3:16baseline so that the conversation can move
- 3:18immediately to the specific challenges they face in their
- 3:20workflow. Finally, you draft targeted questions that dig into
- 3:23the specific differences within their work. One key question for
- 3:26this group is: "How is the sales process different for different
- 3:29product lines?" This question is designed to uncover variations
- 3:32that a generic process map might miss. It prompts the
- 3:34participants to detail their unique workflows. By asking
- 3:36this, you are applying the group-specific planning method
- 3:39to ensure the agenda is tailored to the specific group you are
- 3:42meeting with. This specific combination of participants,
- 3:44time, context, and questions forms the core of your meeting
- 3:47plan.
- 3:53Stop reading the guide and start drafting. Pick one stakeholder
- 3:56group from your current project context. List their names by
- 3:59role, like you did for Inside Sales and Lead Management.
- 4:01Define a clear objective, such as understanding the current
- 4:04sales process. Formulate one or two targeted questions that
- 4:07align with the group's specific level of detail. If you are
- 4:09meeting a large, one-time group, aim to gather ideas. Do not dive
- 4:12into gritty details. If the session is smaller or repeated,
- 4:15allow for deeper investigation. Your plan must be tailored to
- 4:18that specific group, even if the questions overlap with others.
- 4:21The reason this works is that you have already defined your
- 4:23internal roles for scheduling and structure. You have
- 4:26calibrated the detail depth. You have structured the group-
- 4:28specific meeting plan. Now, apply the group-specific
- 4:31planning method to create a structured agenda including
- 4:33participants, time frame, and targeted questions. This is the
- 4:36moment you move from planning to action. You have the framework,
- 4:39the roles, and the detail levels. Now, design a tailored
- 4:41meeting plan for a specific stakeholder group that defines
- 4:44participants, objectives, and appropriate detail levels. That
- 4:47is how you turn a generic guide into a working project.
- 4:52Welcome to The Take. I'm joined by a fellow practitioner and
- 4:55together we're going to dig into Planning Your Stakeholder
- 4:58Requirements Meetings — what it means in practice and what's
- 5:01worth remembering.
- 5:03[HOST] The biggest trap I see is treating a large, one-time
- 5:06gathering like a deep-dive workshop. [LEARNER] Exactly.
- 5:09People try to solve technical edge cases with forty
- 5:11stakeholders in the room. [HOST] It’s a bandwidth failure. You
- 5:15can’t investigate every thread with that many voices. [LEARNER]
- 5:18So you have to strictly limit those sessions to idea
- 5:21generation only. [HOST] Right. Save the gritty details for the
- 5:24smaller, repeated sessions. [LEARNER] That’s where the real
- 5:27friction usually lives, though. [HOST] True. But if you push for
- 5:31mechanics in a large group, you lose the quiet voices. [LEARNER]
- 5:34Speaking of quiet voices, how do you handle the logistics of who
- 5:38actually sits in the room? [HOST] That’s the role of the
- 5:41scheduler. They curate the mix of internal and external
- 5:44partners. [LEARNER] I’ve seen teams skip that and just invite
- 5:47everyone with a relevant job title. [HOST] That leads to
- 5:50duplicated perspectives and missed operational nuances.
- 5:53[LEARNER] It’s messy. Who creates the structure of the
- 5:56questions, then? [HOST] That’s the second role. Someone builds
- 5:59the agenda and decides the order of inquiry. [LEARNER] Can AI
- 6:02help with that structuring step? [HOST] It can draft the flow,
- 6:06but it misses the political context of who needs to speak.
- 6:09[LEARNER] So it’s a tool, not a replacement for the scheduler’s
- 6:12judgment. [HOST] Precisely. The AI handles the syntax of the
- 6:15agenda, the human handles the strategy. [LEARNER] That makes
- 6:18sense. The structure stays the same, but the depth shifts by
- 6:22group size. [HOST] Yes. Even if the questions overlap, the plan
- 6:25must be tailored to the specific group. [LEARNER] So I’d ask "how
- 6:29does the process vary?" to the small team, not the large one.
- 6:32[HOST] Correct. The small team gives you the mechanics, the
- 6:35large team gives you the landscape. [LEARNER] That
- 6:38distinction is the whole game, isn’t it? [HOST] It is. Define
- 6:41the roles, calibrate the depth, and the rest follows.