Latest / 5 Minute UX / Defining the Whys: A Practical Guide
Transcript
- 0:08This lesson is Defining the Whys: A Practical Guide. Let's
- 0:12get started.
- 0:19We start with the Four-Phase Definition Framework, which
- 0:22gives us a loose, linear approach to structuring our
- 0:24work. First, we plan the overall strategy by establishing a high-
- 0:27level direction that defines the output. This initial step sets
- 0:29the stage for everything that follows, ensuring we know where
- 0:32we are heading. It’s about getting the big picture right
- 0:34before we dive into the weeds of execution. Next, we define the
- 0:37detailed project requirements by detailing specific efforts for
- 0:40each phase. We clarify what these efforts mean to both the
- 0:42practitioner and the client, creating the approach section
- 0:45for the proposal. This documentation ensures everyone
- 0:47is aligned on the scope and expectations before any real
- 0:49work begins. The length of this section varies, but its purpose
- 0:52is always to lock in the agreement. Then, we develop,
- 0:54test, refine, and launch the work product by executing the
- 0:57design and development cycle. This phase turns our plans into
- 0:59a tangible, launched work product that delivers value to
- 1:02the user. It’s the core of the project where ideas become
- 1:04reality through rigorous testing and iteration. We don’t just
- 1:07build; we refine based on feedback to ensure quality and
- 1:09usability. Finally, we extend the project by recommending
- 1:11enhancements and improvements for future iterations. We use
- 1:14information learned during development, testing, and post-
- 1:16launch to inform these next steps. This phase ensures the
- 1:19project continues to evolve and improve over time, rather than
- 1:21stagnating. It closes the loop, turning past insights into
- 1:24future strategic advantages. By mastering these four phases,
- 1:27you’ll have a solid foundation for defining any project’s
- 1:29scope. This structure prevents drift and keeps the team focused
- 1:32on high-value activities throughout the process. In the
- 1:34next section, we’ll look at how to avoid over-complicating this
- 1:37framework with unnecessary detail.
- 1:44When you start defining the process, it’s tempting to add
- 1:46excessive detail to every single step, which quickly becomes a
- 1:49pitfall of over-complication. You recover from this drift by
- 1:52simplifying your view to the four core phases: Plan, Define,
- 1:55Develop, and Extend. This structure keeps the scope
- 1:57manageable and ensures that both the practitioner and the client
- 2:00share a clear understanding of the work ahead. Think of this
- 2:02framework as a loose, linear approach where definition comes
- 2:05first, even though the steps often overlap in practice. You
- 2:08don’t need rigid boundaries between phases, because the goal
- 2:10is to establish direction rather than lock in every minor detail
- 2:13before you begin. The length of the requirements section will
- 2:16vary depending on the project, the process used, and the
- 2:18specific activities within each step. A small update needs less
- 2:21detail than a new product launch, so you adjust the depth
- 2:24accordingly. By sticking to these core phases, you avoid
- 2:26getting lost in unnecessary complexity. This clarity sets
- 2:29the stage for handling discussion drift, which we’ll
- 2:31address next with the 'why' recovery tactic.
- 2:38You will encounter the rabbit hole problem when participants
- 2:41follow a why question into a deep, specific direction that
- 2:43does not lead anywhere relevant to the group’s goals. This drift
- 2:46happens quickly because a single inquiry can trigger a sudden,
- 2:48detailed debate that yields minimal value for the team. You
- 2:50recognize this pattern when the conversation moves away from the
- 2:53core definition work and into tangential specifics that do not
- 2:55serve the project. It is a common trap that pulls energy
- 2:58away from the primary objectives of the session. To recover from
- 3:00this drift, you apply the recovery action by using the why
- 3:03question itself to help participants assess the value of
- 3:05the current discussion. Use the momentum of the inquiry to pause
- 3:07and reflect on its utility. This approach respects the
- 3:10participant’s curiosity while gently redirecting the focus
- 3:12back to the task at hand. You turn the source of the
- 3:14distraction into the tool for correction. The mechanism
- 3:16requires you to ask participants to evaluate the relevance of the
- 3:19rabbit hole discussion to the group’s overall goals. You guide
- 3:21them to measure the specific topic against the broader
- 3:23objectives you established at the start of the planning phase.
- 3:26This step forces a conscious assessment of whether the deep
- 3:28dive serves the project or merely satisfies individual
- 3:30curiosity. It creates a shared standard for what constitutes
- 3:33valuable conversation during the definition process. The outcome
- 3:35is that participants are pulled back out of the unproductive
- 3:38deep dive and return to the main workflow. They regain their
- 3:40focus on the loose, linear approach because they have
- 3:42explicitly connected their questions to the project’s
- 3:44needs. This tactic ensures that every inquiry contributes to the
- 3:47clarity of the approach section rather than diluting it. You
- 3:49maintain the integrity of the definition phase by keeping the
- 3:52discussion aligned with the strategic goals. By mastering
- 3:54this relevance assessment, you can effectively recover from a
- 3:56rabbit hole scenario and keep the team on track. This skill
- 3:59allows you to manage discussion drift without stifling
- 4:01engagement or losing the collaborative energy of the
- 4:03group. You are now prepared to see how this tactic plays out in
- 4:06a specific scenario where a team debates historical context.
- 4:15Imagine a team member asks why we are prioritizing feature X,
- 4:17which instantly triggers a ten- minute debate on historical
- 4:20context that is entirely irrelevant to our current goals.
- 4:22You need to recognize this specific drift as a rabbit hole
- 4:25triggered by a why question that yields minimal value for the
- 4:27group. The recovery action is to use the why question itself to
- 4:30help participants assess the value of the current discussion
- 4:33against the group’s overall goals. Interrupt the drift by
- 4:35asking the group to evaluate the relevance of this historical
- 4:38debate to the current group’s overall goals. This mechanism
- 4:40pulls participants back out of the unproductive deep dive and
- 4:43redirects the conversation back to defining the detailed project
- 4:46requirements for the current phase. Now picture yourself in a
- 4:48planning session where a tangent starts to form, and you apply
- 4:51the relevance assessment to recover from a rabbit hole
- 4:53scenario. You will know you have succeeded when the team stops
- 4:56debating the past and starts defining the specific efforts
- 4:58for the present. This practice ensures that every why question
- 5:01serves the project rather than distracting from it.
- 5:06Welcome to The Take. I'm joined by a fellow practitioner and
- 5:09together we're going to dig into Defining the Whys: A Practical
- 5:12Guide — what it means in practice and what's worth
- 5:14remembering.
- 5:16[HOST] That framework for locking in scope before we touch
- 5:19a pixel feels like a luxury I rarely get. [LEARNER] It's a
- 5:22luxury until you realize how much time we waste fixing scope
- 5:25creep later. [HOST] Exactly. The Define phase forces us to agree
- 5:28on the output before we debate the features. [LEARNER] But
- 5:31clients hate waiting for that agreement. They wanna jump
- 5:34straight to solutions. [HOST] That's where the Why recovery
- 5:37tactic becomes your best defense against their impatience.
- 5:40[LEARNER] I tried that last week. A stakeholder went down a
- 5:43rabbit hole about legacy code. [HOST] Did you let them dig, or
- 5:46did you ask if that history served our current goals?
- 5:49[LEARNER] I asked the relevance question. It killed the vibe,
- 5:52but it saved the timeline. [HOST] It feels confrontational
- 5:55because it challenges their ego, not their logic. [LEARNER] True.
- 5:59And now with AI generating specs in seconds, that drift happens
- 6:02even faster. [HOST] AI gives us speed, but it doesn't give us
- 6:05strategic alignment on its own. [LEARNER] Right. The tool builds
- 6:08the what, but we still have to fight for the why. [HOST] So the
- 6:12framework isn't just about planning. It's about maintaining
- 6:15human judgment. [LEARNER] I never thought of it as a
- 6:17guardrail against algorithmic drift. [HOST] It is. We define
- 6:20the boundaries so the AI stays within them.