Latest / 5 Minute UX / Turning Stakeholder Ideas Into Requirements
Transcript
- 0:08This lesson is Turning Stakeholder Ideas Into
- 0:10Requirements. Let's get started.
- 0:19Before you gather ideas, analyze the current state of the site or
- 0:22its competitors to establish context. This step is critical
- 0:25because it allows you to properly interpret the ideas
- 0:27that will emerge during requirements gathering. Without
- 0:30this baseline, you risk missing subtle differences in
- 0:33stakeholder expectations. Consider a stakeholder who
- 0:35suggests, "Customers can track their orders online." If you
- 0:38lack context about the underlying problem, you might
- 0:40build a basic status page. But the stakeholder actually wanted
- 0:43packages tracked by GPS. Missing that specific expectation means
- 0:46you develop a solution that misses stakeholder intent. That
- 0:49mismatch causes redesign and lost money. It creates unhappy
- 0:52stakeholders and wasted time. So, always start by
- 0:54understanding the current landscape. This prevents you
- 0:57from seizing on a feature without grasping the problem.
- 1:00[pause:0.5s] Once you have that context, you’re ready to move
- 1:03into the four-step consolidation sequence.
- 1:11The sequence starts by analyzing the current state of the site or
- 1:14its competitors to establish the necessary context. You are
- 1:16looking at what already exists to create a baseline for
- 1:19interpretation. This prevents you from misreading a
- 1:21stakeholder's intent before you even begin collecting new data.
- 1:24Next, you gather needs and ideas from business stakeholders,
- 1:26current users, and potential users. This phase is about
- 1:29collecting raw, unfiltered input from all three groups. You are
- 1:32not solving anything yet. You are simply ensuring you have
- 1:34heard from every relevant perspective that will impact the
- 1:37final product. The third step is where the real work happens:
- 1:39coalescing ideas into requirements. This is where you
- 1:42take fuzzy ideas and complaints and consolidate them into
- 1:44distinct, trackable components. A critical part of this step is
- 1:47distinguishing between business requirements, which come from
- 1:50business stakeholders, and user requirements, which come from
- 1:52research with users. They have different sources and different
- 1:55drivers, so keeping them separate ensures you address
- 1:57both business intent and user needs accurately. Finally, you
- 2:00prioritize requirements using project objectives to focus your
- 2:03efforts. This creates a consolidated list of project
- 2:05requirements that guides the build. You are cutting the noise
- 2:08and keeping only what aligns with the core goals of the
- 2:10project. This four-step sequence moves you from raw
- 2:12input to a clear, actionable plan. It ensures that the final
- 2:15solution aligns with business intent and project objectives.
- 2:18The next challenge is avoiding the trap of seizing on a
- 2:20specific feature and calling it a requirement without
- 2:22understanding the underlying problem.
- 2:30Here is the spoken narration. A frequent error is seizing on a
- 2:33specific feature and calling it a requirement without first
- 2:35understanding the problem and the expectations around a
- 2:38solution. This happens because the requirements-gathering
- 2:40process is often shortened, as gathering ideas and coalescing
- 2:43them into requirements can take quite a bit of time. The core
- 2:46principle is that requirements are statements defining what the
- 2:49site or application needs to do, not prescribing specific
- 2:51solutions. When a stakeholder says "Customers can track their
- 2:54orders online," that is a feature, not a requirement. To
- 2:57avoid this pitfall, you must understand the underlying
- 2:59problem before defining the solution. The requirement should
- 3:02define the capability, such as "The system provides real-time
- 3:05order status updates." This distinguishes the business need
- 3:07from the technical implementation. By defining
- 3:09what the site needs to do, you ensure the final solution aligns
- 3:12with business intent. This prevents the development of
- 3:15solutions that miss stakeholder intent, which leads to unhappy
- 3:18stakeholders, lost time, and money if features require
- 3:20redesign.
- 3:27Think about a recent stakeholder request where you skipped the
- 3:30context step. You heard "customers can track their
- 3:32orders online" and started sketching a dashboard. You
- 3:34likely treated it as a business requirement, but you missed the
- 3:37underlying problem. If you had analyzed the current state of
- 3:40competitors, you might have discovered that the real
- 3:42expectation was specific GPS tracking for packages. That
- 3:44distinction changes the entire scope of work. Ask yourself:
- 3:47did you seize on that feature without understanding the
- 3:49expectations around the solution? Because the source of
- 3:52that idea was a business stakeholder, it belongs in the
- 3:54business requirements category, not user research. But without
- 3:57that context, you risked developing a solution that
- 3:59misses stakeholder intent. That leads to redesign, lost time,
- 4:02and money. Next time a stakeholder suggests a feature,
- 4:04pause. Identify if it comes from a business stakeholder or user
- 4:07research. Then, ask what problem it solves before you define the
- 4:10requirement. This prevents the common pitfall of shortening the
- 4:13process because coalescing ideas takes quite a bit of time. You
- 4:15are now equipped to turn fuzzy ideas into trackable
- 4:18requirements that align with business intent and project
- 4:20objectives.
- 4:24Welcome to The Take. I'm joined by a fellow practitioner and
- 4:27together we're going to dig into Turning Stakeholder Ideas Into
- 4:30Requirements — what it means in practice and what's worth
- 4:33remembering.
- 4:34[HOST] I keep coming back to that distinction between a
- 4:37feature and a requirement. It’s the hardest line to draw when a
- 4:40stakeholder is excited. [LEARNER] Exactly. They say "I
- 4:43want a chatbot" and your brain wants to start wireframing. But
- 4:47that’s just a feature. [HOST] Right. The requirement is
- 4:49"reduce support ticket volume by twenty percent." That changes
- 4:53everything. [LEARNER] It does. And the context step is where
- 4:56most of us skip because it feels like busywork. [HOST] It’s not
- 4:59busywork. It’s the difference between building a GPS tracker
- 5:02and a status page. [LEARNER] I had a client last year who
- 5:05wanted "online order tracking." We built a simple timeline.
- 5:08[HOST] And they were furious. Because they actually wanted
- 5:12real-time GPS for high-value items. [LEARNER] Exactly. We
- 5:15missed the intent because we didn't analyze the competitor
- 5:18landscape first. [HOST] That’s the trap. We seize on the
- 5:21feature because it’s tangible. The problem is abstract.
- 5:23[LEARNER] And now with AI, this is getting messier. Stakeholders
- 5:27say "make it smart" and expect magic. [HOST] True. They don't
- 5:30know if they need a recommendation engine or a
- 5:32simple rule-based filter. [LEARNER] So the context step is
- 5:35even more critical now. You have to decode the "smart" part.
- 5:39[HOST] I think so. You have to ask what specific problem the AI
- 5:42is solving before you pick the tech. [LEARNER] Otherwise you're
- 5:45just adding complexity for the sake of it. [HOST] Which leads
- 5:48to the redesign nightmare we talked about. Lost time, lost
- 5:52money. [LEARNER] Yeah. The coalescing step is where you
- 5:54save the budget. [HOST] It’s where you cut the noise. You
- 5:57keep only what aligns with the core goal. [LEARNER] That’s the
- 6:01real value. Not the list, but the clarity. [HOST] Precisely. A
- 6:04clear, trackable requirement is worth more than a vague feature
- 6:07wish. [LEARNER] I’ll try to pause and ask "what problem does
- 6:10this solve" before I sketch anything. [HOST] That’s the
- 6:13habit that saves projects. Always start with the problem,
- 6:16not the solution.