Latest / 5 Minute UX / Balancing Advocate Input (User, Business, Development)
Transcript
- 0:08This lesson is Balancing Advocate Input (User, Business,
- 0:12Development). Let's get started.
- 0:19There is a specific rhythm to effective product decisions, and
- 0:22it comes from balancing three distinct voices. You will find
- 0:25that the core prioritization process relies on a triad of
- 0:27advocates: the user, who demands intuitive value; the business,
- 0:30which requires profitability; and development, which ensures
- 0:33feasibility. This structure prevents any single perspective
- 0:36from dominating the room and steering the product off course.
- 0:39UX designers often step into the role of the user advocate, but
- 0:42you cannot decide alone. You must collaborate with business
- 0:44and development partners to determine which features
- 0:47actually move forward. This is not just a list-making exercise,
- 0:50but a strategic negotiation where you whittle down broad
- 0:52requirements. The goal is to create a prioritized list that
- 0:55satisfies all three constituencies simultaneously.
- 0:57We aim for what experts call good tension among these
- 1:00perspectives. This means keeping the debate healthy so that user
- 1:03needs, business goals, and technical realities remain in
- 1:05balance. When you let one voice overpower the others, the
- 1:08product suffers from unchallenged compromises or
- 1:10missed deadlines. Maintaining this tension ensures that every
- 1:13feature serves the user model, aligns with business objectives,
- 1:16and fits within technical constraints.
- 1:23The sequence begins by identifying which advocate holds
- 1:25the most weight in the current moment, because the balance
- 1:27shifts depending on the specific project conditions you are
- 1:30facing. You do not treat every stakeholder perspective with
- 1:32equal intensity at all times, which means you must recognize
- 1:35the signals that dictate priority. When your project
- 1:37objectives are tightly aligned with specific user pain points
- 1:39identified in the user model, you favor the user advocate to
- 1:42ensure the solution remains relevant to your target groups.
- 1:44This alignment ensures that the design addresses real human
- 1:47needs rather than abstract desires, grounding your work in
- 1:49tangible value for the people who will actually use the
- 1:51product. Conversely, you favor the business advocate when
- 1:54budget constraints are severe or when the business strategy
- 1:56hinges on a specific metric to ensure the project remains
- 1:58viable. In these high-stakes scenarios, the financial reality
- 2:01or strategic goal takes precedence because a product
- 2:03that cannot sustain itself financially is ultimately
- 2:05useless to everyone involved. You must listen closely to the
- 2:08business case when the survival of the initiative depends on
- 2:10hitting a particular number or milestone within a strict fiscal
- 2:13window. This prioritization protects the investment and
- 2:15ensures that the work delivers measurable return on investment
- 2:17for the organization backing the project. You also favor the
- 2:20development advocate when technical debt is high or
- 2:22timelines are compressed to prevent project failure through
- 2:24strict scope control. Ignoring technical realities in these
- 2:27moments leads to missed deadlines and broken promises,
- 2:29so the feasibility assessment must guide the boundaries of
- 2:31what you attempt to build. The development perspective becomes
- 2:34the anchor that keeps the project grounded in what is
- 2:36actually possible to deliver within the given constraints. By
- 2:39respecting these limits, you avoid the trap of promising
- 2:41features that are impossible to implement without compromising
- 2:43the entire system's stability. If one perspective is
- 2:46underrepresented in your team, you should assign a dedicated
- 2:48part-time resource to play the role of an absent advocate to
- 2:50maintain balance. This ensures that no single voice dominates
- 2:53the conversation and that all critical factors are considered
- 2:55before making final decisions. The goal is to preserve the
- 2:58necessary tension among these viewpoints, which leads to more
- 3:00robust and well-rounded outcomes for the product. That's the
- 3:03structure of the work; the specific decisions practitioners
- 3:05face inside it come next.
- 3:11Let's say you have a feature request sitting on your desk
- 3:14that looks fantastic on paper but feels heavy in your gut.
- 3:16Here is how this works in practice when you apply the
- 3:18three-question heuristic to balance the competing voices we
- 3:20discussed earlier. You stop the momentum for a moment and ask
- 3:23three specific questions before you let that requirement move
- 3:25forward. First, you ask if this feature actually serves the user
- 3:28model you built in those early discovery sessions. Second, you
- 3:30check if it aligns with the business objectives that keep
- 3:33the lights on and the strategy moving. Third, you verify if it
- 3:35fits within the technical constraints that the development
- 3:38team is currently managing. If the answer to any one of these
- 3:40three questions is no, you must re-evaluate or deprioritize that
- 3:43requirement immediately. This isn't about being difficult;
- 3:45it's about preventing unchallenged compromises from
- 3:47slipping into your roadmap unnoticed. When teams rush
- 3:49through prioritization without this filter, they often end up
- 3:52with features that are either unusable by customers,
- 3:54unprofitable for the company, or impossible to build on time. The
- 3:56heuristic forces you to hold all three advocates accountable at
- 3:59the same time, rather than letting one voice dominate the
- 4:01conversation. You might find that a feature serves the user
- 4:04perfectly but breaks the budget, which means it has to wait for a
- 4:06later release cycle. Or perhaps it fits the budget but ignores
- 4:09the user model, which signals a design failure before you even
- 4:11write a line of code. By treating research results as
- 4:13input rather than absolute mandates, you create space for
- 4:16these necessary trade-offs to happen openly. This practice
- 4:18ensures that no single perspective overrides the
- 4:20others, maintaining that good tension we need for product
- 4:22success. You will notice that decisions become faster once you
- 4:25stop arguing about feelings and start checking against these
- 4:27three concrete criteria. The goal is to whittle down the
- 4:30broad set of requirements into a prioritized list that satisfies
- 4:32all three constituencies simultaneously. When you see a
- 4:34signal that the devil’s advocate role is missing, pull out this
- 4:37heuristic to restart the scrutiny process. It acts as a
- 4:39circuit breaker for groupthink, forcing the team to confront the
- 4:42reality of the situation rather than the ideal. You might be
- 4:44surprised by how many "good" ideas fail this simple test when
- 4:47you actually write them down. This is the mechanism that
- 4:49protects your project from scope creep and technical debt
- 4:51accumulating in the shadows. So when you sit in your next
- 4:53prioritization meeting, bring these questions with you and
- 4:56apply them to every item on the list. The signals you've just
- 4:58learned to read are the ones the next section gets into how to
- 5:01respond to.
- 5:07Consider your last project where a decision felt right but
- 5:09something was missing. Pause and think about whether that choice
- 5:12survived scrutiny from all three perspectives, or if it became an
- 5:15unchallenged compromise. These compromises happen when teams
- 5:18stop asking uncomfortable questions, which signals that
- 5:21the devil’s advocate role has vanished from the room. Without
- 5:24that tension, decisions stagnate, and design quality
- 5:26degrades over time because no one is challenging the status
- 5:29quo. Watch for the specific risk of treating research
- 5:31results as absolute mandates rather than valuable input for
- 5:34design decisions. When you treat data as a rigid command, you
- 5:37stifle innovation and fail to account for business or
- 5:39technical realities that require balanced trade-offs. The cost of
- 5:42misjudging this balance is severe, leading to poor adoption
- 5:45if users are ignored, no return on investment if business needs
- 5:48are sidelined, or missed deadlines if development
- 5:50constraints are neglected. To avoid these pitfalls, apply the
- 5:53three-question heuristic to deprioritize requirements that
- 5:56fail any single criterion. Ask yourself if the feature serves
- 5:59the user model, aligns with business objectives, and fits
- 6:01within technical constraints before finalizing any
- 6:04requirement. If the answer to any of these is no, you must re-
- 6:07evaluate or deprioritize that item to protect the project’s
- 6:09overall viability. This practice ensures that every
- 6:12prioritization session includes representation from all three
- 6:15advocates, preventing any single voice from dominating the
- 6:17outcome. By fostering a culture where uncomfortable questions
- 6:20are welcomed, you preserve the good tension necessary for
- 6:23effective decision-making across the project lifecycle. You’ll
- 6:26find that evaluating feature requirements using the User-
- 6:28Business-Development triad heuristic helps you balance
- 6:31competing stakeholder interests without sacrificing quality. The
- 6:34signals you’ve just learned to read are the ones the next
- 6:37section gets into how to respond to.
- 6:43Start by identifying who represents each advocate role in
- 6:46your current project, because clarity prevents silent
- 6:48failures. If a voice is missing, bring in a part-time resource to
- 6:51fill that gap and ensure every perspective is heard. Use the
- 6:54three-question heuristic to check each requirement against
- 6:56user, business, and technical criteria before you commit. Ask
- 6:59if the feature serves the user model, aligns with business
- 7:01objectives, and fits within technical constraints. If any
- 7:04answer is no, you must re- evaluate or deprioritize that
- 7:06requirement immediately to protect the project's health.
- 7:09Foster a culture where uncomfortable questions are
- 7:11welcomed, because that friction preserves the necessary good
- 7:14tension. Without a devil’s advocate, teams slide into
- 7:16unchallenged compromises that degrade design quality over
- 7:19time. Treat research results as input rather than mandates,
- 7:21allowing for balanced trade-offs with reality. That brings the
- 7:24lesson full circle, back to the listener and the moment they'll
- 7:27first put the protocol into practice.
- 7:31Welcome to The Take. I'm joined by a fellow practitioner and
- 7:34together we're going to dig into Balancing Advocate Input (User,
- 7:38Business, Development) — what it means in practice and what's
- 7:41worth remembering.
- 7:42[HOST] The idea of treating research as input rather than
- 7:45mandate really stuck with me today. It shifts the dynamic
- 7:48from defending data to negotiating value. [LEARNER]
- 7:51That distinction is crucial because data often feels like a
- 7:54shield in meetings. But treating it as raw material forces us to
- 7:57weigh it against budget and tech constraints explicitly. [HOST]
- 8:00Exactly, and that brings up the tension between user desire and
- 8:04technical debt. When developers push back on feasibility, we
- 8:07often feel like we are compromising the user
- 8:09experience. [LEARNER] It’s easy to view that pushback as
- 8:12resistance, but it’s actually a necessary check. If we ignore
- 8:15the dev advocate’s warning about scope creep, we risk delivering
- 8:18nothing at all. [HOST] I’ve seen teams fail because they let the
- 8:21business voice dominate until the product became unusable. The
- 8:24heuristic helps stop that momentum before it derails the
- 8:27roadmap. [LEARNER] Though I worry the three-question filter
- 8:30might slow down rapid iteration cycles. We need speed, and
- 8:33stopping to interrogate every feature request feels heavy.
- 8:36[HOST] Speed without direction is just noise. The heuristic
- 8:39prevents the costly rework that happens when we build features
- 8:42that don’t align with core objectives. [LEARNER] Fair
- 8:45point, but AI tools are changing how we validate those
- 8:48assumptions. We can now simulate user reactions faster, which
- 8:51might reduce the need for such rigid checks. [HOST] AI can
- 8:54generate options, but it doesn’t understand the strategic trade-
- 8:57offs inherent in the triad. It might optimize for engagement
- 9:00while ignoring long-term technical sustainability.
- 9:03[LEARNER] So we still need human judgment to balance those
- 9:06competing interests, even if AI handles the initial validation.
- 9:09The devil’s advocate role remains irreplaceable. [HOST]
- 9:12Precisely, because the tension comes from understanding the
- 9:15nuance of each stakeholder’s pain. AI lacks the context to
- 9:18know when to favor the business over the user. [LEARNER] That
- 9:21makes sense. We use AI to explore, but we use the
- 9:23heuristic to decide what actually gets built. [HOST]
- 9:26Keeping that separation ensures we innovate without losing sight
- 9:29of viability. It keeps the conversation honest and grounded
- 9:32in reality.