Latest / 5 Minute UX / WhoDo Matrix: A Practical Guide
Transcript
- 0:08This lesson is WhoDo Matrix: A Practical Guide. Let's get
- 0:12started.
- 0:18You gain the ability to move a group from abstract discussion
- 0:21to concrete, time-bound commitments by setting up the
- 0:23WhoDo Framework correctly. Start by preparing a flip chart or
- 0:26whiteboard with three distinct columns labeled WHO, WHAT, and
- 0:28WHEN. This visual structure creates a blank framework ready
- 0:31for input, which means you have a clear path from confusion to
- 0:34clarity. It’s crucial to ensure the group size is between one
- 0:36and ten people, because effective engagement drops when
- 0:39too many voices compete for space. You should also allocate
- 0:41fifteen to thirty minutes for the entire exercise, as this
- 0:44timeframe maintains focus without dragging out the
- 0:46decision-making process. The reason we set these boundaries
- 0:48is to establish a goal of moving away from vague task lists and
- 0:51toward specific individual ownership. When you define the
- 0:53logistics upfront, you create the container that makes
- 0:56accountability possible. This preparation allows you to
- 0:58facilitate a session where every participant knows exactly what
- 1:01is expected of them. Once the board is ready and the time is
- 1:03set, you are positioned to begin populating the matrix with
- 1:06people rather than problems.
- 1:14The first move you make is to write every participant’s name
- 1:16into the WHO column of the matrix, establishing the
- 1:18foundation before any work is discussed. This step forces you
- 1:21to adhere to the critical constraint of describing the
- 1:23critical constraint of starting with people rather than tasks,
- 1:26which fundamentally shifts the dynamic of the meeting. You are
- 1:29not listing duties yet; you are identifying the human agents who
- 1:31will drive the project forward, creating a list of accountable
- 1:34individuals right from the start. By populating this column
- 1:37first, you ensure that ownership is established immediately,
- 1:39preventing the common pitfall where tasks float without a
- 1:42clear owner attached to them. This initial act of naming names
- 1:44signals that the focus is on who is doing the work, not just what
- 1:47the work is, which sets a tone of personal responsibility for
- 1:50the entire session. It is vital that you do not start with the
- 1:52tasks in the WHAT column, because doing so often leads to
- 1:55abstract lists of tasks handed out to possibly unwilling
- 1:57participants with no particular deadline attached. When you
- 2:00begin with tasks, the discussion tends to drift into vague
- 2:02territory where responsibilities are blurred and accountability
- 2:05is lost in the shuffle of general objectives. Instead, you
- 2:07must force the sequence to start with WHO, connecting people with
- 2:10clear actions they have defined and committed to themselves,
- 2:13rather than assigning abstract tasks from the outside. This
- 2:15approach ensures that the people in the room are the ones
- 2:18accountable for the next steps, grounding the project in real
- 2:20human commitment rather than theoretical outputs. By starting
- 2:23with the individuals, you create a direct link between the person
- 2:26and the potential action, making the subsequent commitments feel
- 2:29more personal and binding. The reason this sequence matters is
- 2:31that it prevents the breakdown where participants feel like
- 2:34they are being handed arbitrary duties without their input or
- 2:36agreement. When you start with the people, you are essentially
- 2:39asking who is available and willing to take on
- 2:41responsibility, which naturally leads to more genuine engagement
- 2:44from the group. You are building a framework where each name
- 2:46represents a potential source of action, ready to be filled with
- 2:49specific commitments in the next phase. This method avoids the
- 2:52trap of creating a to-do list that feels imposed, which often
- 2:54results in resistance or lack of follow-through from the team
- 2:57members involved. By prioritizing the WHO column, you
- 2:59are setting the stage for a more collaborative and accountable
- 3:02process, where each participant sees their role clearly defined
- 3:05from the outset. Once the names are in place, you have a solid
- 3:07base of accountable individuals ready to define their specific
- 3:10contributions to the project. This preparation allows the next
- 3:13step to focus on eliciting concrete next steps from each
- 3:15person, ensuring that the actions listed are self-defined
- 3:18and personally owned. The transition from listing names to
- 3:20defining tasks becomes smoother because the context of
- 3:22responsibility has already been established by the presence of
- 3:25the participants' names in the matrix. You are now ready to ask
- 3:28each individual what they can commit to, knowing that the
- 3:30framework supports personal accountability rather than
- 3:32generic task assignment. This setup ensures that the
- 3:35subsequent commitments are tied directly to the people who made
- 3:37them, reinforcing the sense of ownership throughout the
- 3:40process.
- 3:46Now that the names are in place, you move to the heart of the
- 3:49exercise by asking each participant individually what
- 3:51concrete next steps they can commit to. This is where the
- 3:53abstract becomes real, because you are no longer discussing
- 3:56vague responsibilities but specific actions that a person
- 3:58has chosen for themselves. You record these self-defined
- 4:01actions directly in the WHAT column next to their name,
- 4:03creating a clear link between the person and the task. This
- 4:05step prevents the common pitfall where tasks are handed out to
- 4:08unwilling participants, which usually results in a list of
- 4:10items that no one actually owns. You might notice that a single
- 4:13participant feels required to list multiple next steps, and
- 4:16you should absolutely allow this if they strongly believe in
- 4:18those actions. When someone identifies several tasks they
- 4:21are ready to tackle, it signals genuine engagement and a clear
- 4:23understanding of their role in the project. By letting them
- 4:26define the scope of their own work, you ensure that the
- 4:28commitments are realistic and personally meaningful rather
- 4:30than imposed from the outside. This approach connects people
- 4:33with clear actions they have defined themselves, which is far
- 4:36more effective than assigning abstract tasks that feel
- 4:38disconnected from their daily work. Once the actions are
- 4:40recorded, you must ask the responsible person WHEN they
- 4:43will have each item done to establish a firm deadline. You
- 4:45record this specific date or time in the WHEN column,
- 4:47completing the triad of accountability that the WhoDo
- 4:50Matrix relies upon. This final step transforms a simple list of
- 4:52tasks into a binding agreement, because the participant has
- 4:55staked their credibility on taking action in a public
- 4:57setting. By making these commitments in front of peers,
- 4:59participants are significantly more likely to follow through on
- 5:02what they have promised. The reason this sequence works is
- 5:04that it forces the group to focus on the human element of
- 5:07project management rather than just the logistical details.
- 5:09When you apply the step-by-step execution process to populate
- 5:12the matrix, you create a visible record of who is doing what and
- 5:15by when. This visual clarity helps everyone in the room see
- 5:17the full picture of the upcoming work and the individuals driving
- 5:20it forward. As the matrix fills out, you will see how the
- 5:22collective effort is distributed and where potential bottlenecks
- 5:25might arise. With the commitments and deadlines firmly
- 5:27established, the matrix is now ready for the final layer of
- 5:30social reinforcement. The next step involves leveraging the
- 5:32presence of peers to strengthen the accountability that has been
- 5:35built through these personal pledges.
- 5:43Think about the person standing by the whiteboard as they write
- 5:46down a new commitment. They are not just listing a task for a
- 5:49document, but staking their credibility in front of peers.
- 5:51This social pressure transforms abstract duties into personal
- 5:54promises because people commit more strongly to each other than
- 5:57to vague actions. Consider how the room shifts when everyone
- 6:00hears a specific deadline announced aloud. The silence
- 6:02that follows is powerful because it clarifies that the people in
- 6:05the room are accountable for the next steps. You are leveraging
- 6:08social accountability to ensure follow-through, which means the
- 6:11matrix becomes a public record of who owes what to whom. Ask
- 6:14yourself if you are relying on written notes or human
- 6:16connection to drive progress. The reason peer pressure works
- 6:19is that it connects clear actions to individuals rather
- 6:21than assigning abstract tasks to a void. When you make
- 6:24commitments in front of peers, you create a shared sense of
- 6:27responsibility that outlasts the meeting itself. Notice how the
- 6:29completed matrix now serves as a tangible anchor for these
- 6:32interpersonal agreements. It’s no longer just a list, but a map
- 6:35of credibility staked on follow- through by every person present.
- 6:38As you step back to observe the full board, you’ll see how these
- 6:41individual promises weave together into a coherent plan of
- 6:44action.
- 6:51You verify that every WHAT has a corresponding WHO and WHEN
- 6:53before closing the session. This final review ensures no abstract
- 6:56tasks remain without a named owner, which is the core
- 6:58strength of the framework. If you see an action item floating
- 7:00without a person attached, you must stop and assign it
- 7:02immediately because unowned tasks simply vanish into the
- 7:05air. The matrix becomes the definitive output for next
- 7:07steps, so you need to confirm that deadlines are specific and
- 7:09agreed upon by the responsible person. This step solidifies the
- 7:12commitments made in front of peers, turning social
- 7:14accountability into concrete follow-up actions. By forcing
- 7:16this sequence, you connect people with clear actions they
- 7:19defined themselves rather than assigning vague duties. The
- 7:21completed chart now serves as a shared reference point that
- 7:24clarifies who is accountable for what. When you step back, you
- 7:26see a list of specific, self- defined actions linked directly
- 7:29to individuals. This prevents the common pitfall where teams
- 7:31drift back to abstract discussions about work that
- 7:33needs doing. Instead, you have a clear record of credibility
- 7:35staked in a public setting. Participants are more likely to
- 7:38follow through because they verbally committed to these
- 7:40timelines in front of their colleagues. The facilitator’s
- 7:42job is to ensure this document remains accurate and accessible
- 7:45for future check-ins. You’ve now applied the step-by-step
- 7:47execution process to populate the matrix fully. This creates a
- 7:50reliable artifact that drives actual progress rather than just
- 7:52planning. The lesson’s core insight is that starting with
- 7:55people, not tasks, transforms vague intentions into owned
- 7:57outcomes. You began by asking who is in the room, and you end
- 8:00with a clear map of who does what.
- 8:04Welcome to The Take. I'm joined by a fellow practitioner and
- 8:07together we're going to dig into WhoDo Matrix: A Practical Guide
- 8:10— what it means in practice and what's worth remembering.
- 8:14[HOST] I was struck by how starting with the WHO column
- 8:17shifts the room's energy immediately. It forces people to
- 8:20own the space before they even discuss the work. [LEARNER]
- 8:23Absolutely. In my last sprint retro, we tried listing tasks
- 8:26first and got stuck in abstract debate for twenty minutes.
- 8:30Writing names down first stops that drift instantly. [HOST] It
- 8:33creates a psychological contract right from the start. But I
- 8:36worry about the peer pressure aspect feeling too heavy for
- 8:39introverted team members. [LEARNER] That's a valid
- 8:42concern. I found that framing it as a commitment to the group
- 8:45rather than a performance helps. They're promising to their
- 8:48peers, not being judged by the manager. [HOST] Exactly. The
- 8:51social accountability is the engine here. If they don't feel
- 8:54that gentle pressure, the deadlines become suggestions
- 8:57instead of agreements. [LEARNER] I agree. Though I wonder how AI
- 9:00assistants might change this dynamic in the future. If a bot
- 9:04tracks tasks, do we still need this human ritual? [HOST] Tools
- 9:07can track data, but they can't build the credibility that comes
- 9:10from speaking in front of your team. The AI might remind them
- 9:13of the date, but it won't make them care about keeping the
- 9:16promise. [LEARNER] True. The value is in the public staking
- 9:19of reputation. A notification from a bot lacks that social
- 9:22weight. [HOST] So the matrix remains vital for the human
- 9:25layer of accountability. We use the tool to record, but the
- 9:29ritual to bind. [LEARNER] I like that distinction. It keeps the
- 9:32focus on relationships rather than just checkboxes. [HOST] It
- 9:35turns a logistical exercise into a team-building moment. That's
- 9:38where the real progress happens.