Latest / 5 Minute UX / Building an Inclusive Design Practice
Transcript
- 0:08This lesson is Building an Inclusive Design Practice. Let's
- 0:12get started.
- 0:19Think about a project where everyone in the room shared the
- 0:22same background, the same instincts, and the same blind
- 0:24spots. Nobody set out to leave anyone behind, but a team that
- 0:27looks and thinks alike quietly builds for itself. That's the
- 0:30real inclusion challenge, and it starts inside the team long
- 0:33before it ever reaches a user. Inclusion is an active practice
- 0:36of building a team where different perspectives are
- 0:38present, heard, and able to shape the work. When we treat it
- 0:41as passive, hidden assumptions drive our decisions and we put
- 0:44up walls without noticing. When we treat it as active, we go
- 0:47looking for the barriers that keep people out of the team and
- 0:50the conversation, and we remove them on purpose. That shift,
- 0:53from hoping for inclusion to deliberately building it, is
- 0:55where real change begins for your team.
- 1:03By the end of this section, you'll be able to identify the
- 1:06three core pillars of inclusive team building, which means
- 1:09shifting from passive inclusion to active barrier removal. The
- 1:12first pillar is cultivating diverse teams with varied
- 1:14backgrounds, because experienced practitioners know that
- 1:17homogeneous groups tend to produce solutions that exclude
- 1:19users simply due to unconscious bias. The second pillar is
- 1:22empowering team members through purposeful collaboration, so
- 1:25when you establish norms that value every voice, the team
- 1:28surfaces risks earlier and designs with greater empathy.
- 1:30The third pillar is actively removing barriers that exclude
- 1:33users or colleagues, which transforms inclusion from a
- 1:35vague ideal into a measurable practice of clearing obstacles
- 1:38in your workflow. By implementing these three
- 1:40strategies, you create a structure where diversity
- 1:43becomes productive, and the next section shows you how to audit
- 1:46your current team for gaps.
- 1:53The sequence begins by auditing your current team composition
- 1:55for diversity gaps, which is the essential first move in
- 1:58implementing an inclusive design practice. You need to look at
- 2:00who is in the room and identify where the blind spots are,
- 2:03because a lack of diverse perspectives leads to
- 2:05inaccessible solutions that exclude real users. This audit
- 2:07is about understanding the specific backgrounds and
- 2:09experiences missing from your decision-making process. When
- 2:12you map out these gaps, you create a clear picture of what
- 2:14you need to change to shift from passive inclusion to active
- 2:17barrier removal. Once you understand who is missing, the
- 2:19next step is to establish collaboration norms that empower
- 2:21every voice within the team. You cannot have inclusion without
- 2:24purposeful collaboration, so you need to set rules that ensure
- 2:27everyone feels safe to speak up and challenge ideas. This means
- 2:29creating a culture where quiet voices are amplified and
- 2:31dominant voices are checked, so the best ideas win regardless of
- 2:34who proposes them. When teams calibrate these norms carefully,
- 2:37the dynamic shifts from hierarchy to meritocracy, and
- 2:39the work itself becomes more robust because it has been
- 2:41stress-tested by more perspectives. After you have
- 2:43the people and the norms in place, you must identify
- 2:45specific barriers in your current workflow that prevent
- 2:48inclusion. These barriers often hide in plain sight, like a
- 2:50critique format that only rewards the loudest voice or
- 2:52tools that require expensive software licenses, so you need
- 2:55to look for friction points that exclude users or colleagues. You
- 2:58should ask your team where they feel stuck or where they see
- 3:00users dropping off, because those pain points are usually
- 3:03symptoms of deeper structural issues. Identifying these
- 3:05specific obstacles allows you to target your efforts rather than
- 3:08trying to fix everything at once, which prevents overwhelm
- 3:10and keeps the team focused. The final move is to remove those
- 3:13identified barriers through concrete process changes, which
- 3:15completes the cycle of building and sustaining inclusive design
- 3:18teams. You might simplify an approval step, rewrite confusing
- 3:20language, or adopt a tool that is accessible to everyone, but
- 3:23the key is to act on what you found during the identification
- 3:25phase. This action-oriented approach ensures that inclusion
- 3:28becomes a daily practice embedded in how you work. By
- 3:30removing these barriers, you demonstrate to the team that
- 3:32their feedback matters and that the organization is committed to
- 3:35doing the hard work of inclusion. That is the step-by-
- 3:37step implementation of an inclusive design practice,
- 3:39moving from audit to action to create a team that is diverse,
- 3:42empowered, and barrier-free. The next section puts it into
- 3:44practice with a worked example.
- 3:51Here's how this plays out, starting with a concrete example
- 3:54from the field. Picture a weekly design critique where the
- 3:57same two senior voices drive every decision. The newer and
- 4:00quieter members have sharp instincts, but the format never
- 4:02gives them room, so their perspective never reaches the
- 4:05work. The barrier is the meeting structure itself, which rewards
- 4:08whoever speaks first and loudest. An inclusive team
- 4:11changes the format. They open critiques with a few minutes of
- 4:14silent, written feedback before anyone speaks, so every idea is
- 4:17on the table before the room anchors on one opinion. They
- 4:19rotate who leads the discussion, and they hold a shared norm that
- 4:23the goal is to understand an idea before anyone moves to
- 4:25change it. When the team removes that structural barrier,
- 4:28the quiet expertise finally shapes decisions, and the design
- 4:31gets stronger because more perspectives have stress-tested
- 4:34it. Now apply the same lens to your current project by focusing
- 4:37on just one barrier at a time. Trying to fix everything at once
- 4:40leads to overwhelm, which means your efforts stall before they
- 4:43gain traction. Identify one specific barrier in your
- 4:46workflow that keeps a voice out of the work, whether it's a
- 4:49critique format, an approval process, or a feedback channel
- 4:51only some people can reach. Pick that single point of friction
- 4:54and ask how removing it would let more of your team shape the
- 4:57outcome. The goal is to shift from passive inclusion to active
- 5:00barrier removal, one deliberate step at a time. That's the
- 5:03structure of the work; the specific decisions practitioners
- 5:06face inside it come next.
- 5:13How many users are you accidentally excluding right
- 5:16now? The answer is likely more than you think. Inclusive
- 5:18design is a structured practice built on three core pillars:
- 5:21cultivating diverse teams, empowering collaboration, and
- 5:24actively removing barriers. Remember when you spent weeks on
- 5:27a feature that confused half your users? That was a barrier
- 5:30you missed. Now, apply these three pillars to your next
- 5:32design sprint. Start by scheduling a meeting to discuss
- 5:35just one specific barrier in your workflow. Don't try to fix
- 5:38everything at once. Focus on that single point of friction.
- 5:41Measure your success by increased team empowerment. When
- 5:43your team feels safe to challenge assumptions, your
- 5:46designs improve naturally. That brings the lesson full circle,
- 5:49back to the moment you'll first put these strategies into
- 5:51practice. That's how you start building a more inclusive design
- 5:54practice.
- 5:58Welcome to The Take. I'm joined by a fellow practitioner and
- 6:01together we're going to dig into Building an Inclusive Design
- 6:04Practice — what it means in practice and what's worth
- 6:06remembering.
- 6:08[HOST] That audit step felt heavy. We usually skip straight
- 6:11to fixing symptoms because staring at our own blind spots
- 6:14is uncomfortable. [LEARNER] It is. I found myself wanting to
- 6:17jump to the barrier removal phase immediately. The audit
- 6:20forces you to admit who isn’t in the room. [HOST] Exactly. And
- 6:23that admission is the only way to stop designing for the median
- 6:27user who doesn’t exist. You have to map the gaps before you can
- 6:30fill them. [LEARNER] But how do you measure if the new norms are
- 6:33actually working? It’s easy to say we value quiet voices, but
- 6:37hard to prove they’re being heard. [HOST] You look at
- 6:39decision logs. If the same three people always drive the final
- 6:43call, your norms are just theater. Real inclusion changes
- 6:46the outcome, not just the meeting vibe. [LEARNER] That’s a
- 6:49sharp metric. I’ve seen teams claim inclusivity while the
- 6:52loudest voice still dictates the wireframes. It’s performative
- 6:55inclusion. [HOST] And AI might make that worse if we aren’t
- 6:58careful. We risk feeding homogeneous data into models
- 7:01that then reinforce those same blind spots. [LEARNER] True. If
- 7:04the training data lacks diverse perspectives, the AI becomes an
- 7:07echo chamber for our existing biases. It scales exclusion
- 7:10rather than solving it. [HOST] So the human audit remains
- 7:13critical. We need to verify that the AI isn’t just optimizing for
- 7:17the dominant user group we’ve already built for. [LEARNER]
- 7:20Right. The tool is only as inclusive as the guardrails we
- 7:23put around it. We have to actively check for exclusion in
- 7:26the outputs. [HOST] It brings us back to active barrier removal.
- 7:29We can’t automate empathy. We have to design the checks that
- 7:32catch what the algorithm misses. [LEARNER] I like that framing.
- 7:35It keeps the responsibility on us to build the safety nets,
- 7:39rather than trusting the tech to be fair by default. [HOST]
- 7:42Precisely. The lesson isn’t about using better tools. It’s
- 7:45about building a team culture that questions every tool,
- 7:48including the smartest ones.