Latest / 5 Minute UX / The Three Advocate Roles on a UX Project
Transcript
- 0:08This lesson is The Three Advocate Roles on a UX Project.
- 0:11Let's get started.
- 0:19Projects often suffer from unchallenged compromises that
- 0:22quietly accumulate as the work progresses. This happens because
- 0:25team discussions during requirements gathering and
- 0:27throughout the rest of the project require consistent
- 0:30challenge to stay sharp. Without a consistently present devil’s
- 0:33advocate, the group tends to drift toward easy answers rather
- 0:36than necessary truths. The absence of uncomfortable but
- 0:38important questions leads directly to degraded project
- 0:41outcomes for everyone involved. We see this pattern when teams
- 0:43avoid friction, assuming harmony means success, but it actually
- 0:46means they are ignoring critical risks. These small concessions
- 0:49compound over time, eroding the quality of the final design
- 0:52without anyone noticing until it is too late. The reason is that
- 0:55no one is actively pushing back against the path of least
- 0:58resistance. So when you observe a meeting where everyone agrees
- 1:01too quickly, you should worry about what is being left unsaid.
- 1:03This lack of tension allows bad decisions to solidify into the
- 1:06project plan. We need to recognize that silence is not
- 1:09consent; it is often a sign of unchecked compromise.
- 1:11Identifying the three advocate roles helps us understand where
- 1:14that missing challenge should come from.
- 1:22You will identify the Business, User, and Development advocate
- 1:25roles that shape every decision. [pause:1s] These positions pull
- 1:29against each other to maintain good tension during discussions.
- 1:32Think back to projects where scope creep or missed user needs
- 1:35crept in. That drift happened because no one asked the
- 1:38uncomfortable but important questions. We need to recognize
- 1:41how these specific roles interact to prevent that decay.
- 1:50We start by looking at the first concrete move in this framework,
- 1:53which is identifying the specific roles that pull against
- 1:55each other during team discussions. The source material
- 1:57defines three distinct advocate positions: the Business
- 2:00Advocate, the User Advocate, and the Development Advocate. These
- 2:02roles are not just titles on an organizational chart, but active
- 2:05forces that create what we call good tension. When you identify
- 2:08these roles clearly, you establish the structure needed
- 2:10to prevent unchallenged compromises from accumulating.
- 2:13This identification is the foundation of the entire
- 2:15process. Let’s examine the Business Advocate first, because
- 2:17this role carries the weight of the company’s strategic
- 2:20direction. This person represents business needs and
- 2:22requirements, ensuring they are captured and met as faithfully
- 2:24as possible. Their primary concerns are meeting strategic
- 2:27objectives for the company and department, which keeps the work
- 2:30aligned with broader goals. They also focus on ensuring the
- 2:32business vision doesn’t get lost during the project, which is a
- 2:35common risk in long-term development. By setting and
- 2:37maintaining focus on project objectives, the Business
- 2:39Advocate anchors the team in reality. Next, we look at the
- 2:42User Advocate, who represents the needs and perspectives of
- 2:44the primary users who will experience the site. This role
- 2:47ensures that the human element remains central to every
- 2:49decision, balancing the commercial pressures from the
- 2:51business side. Without this specific voice, the project
- 2:54risks becoming a collection of features that no one actually
- 2:56wants or needs. The User Advocate asks the uncomfortable
- 2:59but important questions about usability and accessibility that
- 3:01might otherwise be ignored. This perspective is crucial for
- 3:04creating a product that people will genuinely use and value.
- 3:06The Development Advocate serves as the third primary role in
- 3:09prioritization discussions, pulling against the other two to
- 3:11maintain balance. This role ensures that technical
- 3:13feasibility and resource constraints are respected,
- 3:16preventing the team from promising more than they can
- 3:18deliver. While the source material is brief on this
- 3:20specific role, its function is to ground the discussion in
- 3:23technical reality. This creates a necessary counterweight to the
- 3:25idealism of the user and the ambition of the business. All
- 3:28three roles must be present to keep the project moving forward
- 3:30effectively. If a single person must hold more than one role,
- 3:33you should find a part-time resource to play the other roles
- 3:36occasionally. This strategy helps maintain good tension even
- 3:38when team structures are lean or resources are limited. By
- 3:41bringing in an outside perspective, you ensure that no
- 3:43single viewpoint dominates the conversation unchecked. This
- 3:45approach allows you to apply the part-time resource strategy to
- 3:48maintain tension during critical moments. It’s a practical way to
- 3:51simulate the full triangle of advocacy when you don’t have the
- 3:54luxury of a large team. Identifying these three advocate
- 3:56roles gives you the vocabulary to recognize when one voice is
- 3:58missing from the room. You can now see how the Business, User,
- 4:01and Development advocates interact to shape the final
- 4:03product. This understanding prepares you to look at how
- 4:06these roles pull against each other to create productive
- 4:08conflict. The next step is to explore how this dynamic tension
- 4:11actually improves the quality of your design decisions.
- 4:19Maintaining good tension requires the three advocate
- 4:21roles to pull against each other during team discussions, which
- 4:24prevents any single perspective from dominating the
- 4:26conversation. [pause:2s] When the business, user, and
- 4:29development advocates challenge one another, they create a
- 4:31healthy friction that surfaces hidden assumptions and forces
- 4:34the team to justify every design decision. This dynamic ensures
- 4:36that unchallenged compromises do not accumulate as the project
- 4:39progresses, protecting the integrity of the final product.
- 4:41If you allow one voice to go unchallenged, the project risks
- 4:44drifting away from its core objectives without anyone
- 4:46noticing until it is too late. [blank line] You need a
- 4:48consistently present devil’s advocate to ask uncomfortable
- 4:51but important questions throughout the requirements
- 4:53gathering phase and beyond. [pause:1s] Without this
- 4:55consistent challenge, small concessions add up over time,
- 4:58leading to degraded project outcomes that fail to meet
- 5:00strategic or user needs. The reason this happens is that
- 5:02teams naturally seek consensus, often at the expense of critical
- 5:05scrutiny. By actively seeking out those uncomfortable
- 5:07questions, you ensure that the business vision remains clear
- 5:10and that user perspectives are not lost in the shuffle of daily
- 5:13tasks. [blank line] If a single person must hold more
- 5:15than one role, you should find a part-time resource to play the
- 5:18other roles occasionally to maintain good tension.
- 5:20[pause:2s] This resource strategy ensures that good
- 5:22tension is maintained even when team structures are lean and
- 5:25budgets are tight. You might bring in an external consultant
- 5:27or a colleague from another department to temporarily fill
- 5:30the gap left by your dual responsibilities. Their fresh
- 5:32perspective helps simulate the natural push-and-pull that
- 5:34occurs when three distinct advocates are present, keeping
- 5:37the discussion balanced and rigorous. [blank line] So when
- 5:39you step into these advocate roles, remember that your goal
- 5:42is to apply the resource strategy to maintain tension
- 5:44during every key discussion. [pause:1s] Identify the
- 5:46Business, User, and Development advocate roles clearly, and
- 5:49ensure each voice has someone dedicated to defending its
- 5:51interests. This deliberate structure transforms potential
- 5:54conflict into constructive dialogue, leading to better
- 5:56decisions and a more resilient design. You now have the
- 5:58framework to navigate these tensions effectively, turning
- 6:01what could be chaotic debates into focused, productive
- 6:03exchanges that drive the project forward.
- 6:08Welcome to The Take. I'm joined by a fellow practitioner and
- 6:11together we're going to dig into The Three Advocate Roles on a UX
- 6:15Project — what it means in practice and what's worth
- 6:18remembering.
- 6:19[HOST] The idea that silence is often unchecked compromise
- 6:22really stuck with me today. It challenges the way we usually
- 6:25interpret smooth meetings as signs of progress. [LEARNER] I
- 6:28feel that tension every time a stakeholder nods along too
- 6:31quickly. We mistake their comfort for alignment, when they
- 6:34might just be avoiding conflict. [HOST] Exactly. That’s why
- 6:37identifying the Business, User, and Development advocates
- 6:40matters so much. We need to ensure those specific voices are
- 6:43actively pulling against each other. [LEARNER] But in smaller
- 6:46teams, one person often wears multiple hats. How do we
- 6:49maintain that healthy friction if the Business and User
- 6:52advocates are the same person? [HOST] The lesson suggests using
- 6:55a part-time resource to fill the missing role occasionally. It’s
- 6:58about simulating that counterweight even when your
- 7:01team structure is lean. [LEARNER] That makes sense, but
- 7:04bringing in an outsider can feel artificial at first. They might
- 7:07not grasp the nuance of the project context immediately.
- 7:10[HOST] True, but their lack of internal bias is precisely what
- 7:13creates the necessary tension. They ask the uncomfortable
- 7:16questions that insiders have learned to ignore. [LEARNER] I
- 7:19wonder if AI tools could serve as that neutral third party now.
- 7:22We could prompt an LLM to critique designs from a strict
- 7:25technical or business perspective. [HOST] That’s a
- 7:27fascinating angle. AI could definitely simulate the
- 7:30Development Advocate by flagging feasibility issues instantly.
- 7:33[LEARNER] Or it could role-play the User Advocate by generating
- 7:36harsh feedback based on accessibility standards. It
- 7:39removes the interpersonal risk of playing devil’s advocate.
- 7:42[HOST] But we have to be careful not to let it replace human
- 7:45judgment entirely. The goal is good tension, not just automated
- 7:48compliance checks. [LEARNER] Right. The AI can surface the
- 7:51risks, but humans still need to navigate the trade-offs. It’s a
- 7:54tool for tension, not a replacement for dialogue. [HOST]
- 7:57Precisely. Use it to keep the conversation sharp, but never
- 8:00let it silence the necessary human debate.