Latest / 5 Minute UX / Pre-Mortem: A Practical Guide
Transcript
- 0:08This lesson is Pre-Mortem: A Practical Guide. Let's get
- 0:11started.
- 0:18Most teams fail because they ignore their own optimism. A
- 0:21pre-mortem flips the script. It’s a prospective hindsight
- 0:23exercise where you imagine your project has already crashed.
- 0:26This simple mental shift moves your group from blind optimism
- 0:29to sharp, critical analysis. You need three core principles
- 0:32to make this work. First, Silent Writing First. Have everyone
- 0:35write down failure reasons alone before talking. This stops loud
- 0:38voices from steering the room and kills groupthink. Second,
- 0:41use Specific Failure Scenarios. Don’t just say “it failed.” Say,
- 0:43“We missed the launch by three months.” Concrete details
- 0:46trigger real risks, not vague worries. Third, practice Root
- 0:49Cause Mapping. Trace every risk back to a current decision or
- 0:52assumption. Stop blaming bad luck. Find the process gap.
- 0:54When you lock these principles in, you stop guessing and start
- 0:57preventing. The next section shows you how to set up the room
- 1:00and run the clock.
- 1:06Think back to when you scheduled a meeting that ran over time
- 1:09because the agenda was too vague. A pre-mortem needs
- 1:11tighter logistics to avoid that trap, so you start by gathering
- 1:14four to eight participants who are directly involved in the
- 1:16execution. You also need a neutral facilitator who does not
- 1:18lead the project, which keeps the conversation objective and
- 1:21prevents defensive reactions from the team. Before you open
- 1:23the whiteboard, ensure a finalized project scope or
- 1:25roadmap is present, along with a list of key stakeholders. Having
- 1:28these documents ready grounds the exercise in reality, so when
- 1:31you allocate sixty to ninety minutes for the full exercise,
- 1:33every minute counts toward identifying real risks rather
- 1:35than hypothetical ones. You will use a large whiteboard or a
- 1:38digital tool like Miro or Mural to capture ideas visually,
- 1:40allowing the team to see connections forming in real
- 1:42time. If your team is larger than six people, set up the room
- 1:45for small group clustering so everyone has space to contribute
- 1:47without feeling crowded. This physical or digital structure
- 1:50supports the Silent Writing First principle by giving each
- 1:52person a dedicated space to think before speaking. With the
- 1:54right people, tools, and time in place, you create the conditions
- 1:57for a productive session that leads naturally into the five-
- 1:59step execution process we will explore next.
- 2:07The sequence begins by setting the scene, a move that takes
- 2:09five to ten minutes and establishes the psychological
- 2:12safety needed for honest critique. The facilitator
- 2:14presents a specific narrative of catastrophic failure, stating
- 2:16clearly that it is six months from now and the project has
- 2:19failed because of a concrete reason. This framing shifts the
- 2:21group from optimistic bias to critical analysis by treating
- 2:23the failure as a hypothetical past event. When you define the
- 2:26scenario as specific, such as missing the launch date by three
- 2:29months, participants feel safe to voice concerns they would
- 2:31otherwise suppress. The second step involves silent
- 2:33brainstorming for ten to fifteen minutes, where participants
- 2:36individually write down every possible reason for the failure
- 2:38on sticky notes. They must focus on why the project failed, not
- 2:41just what failed, which prevents dominant voices from steering
- 2:43the conversation early in the process. This individual writing
- 2:46phase is crucial because it ensures that quieter team
- 2:48members contribute their insights before group dynamics
- 2:50take over. By capturing these thoughts separately, you build a
- 2:53comprehensive list of risk factors that reflects the
- 2:55diverse perspectives of the entire team. In the third step,
- 2:57you group and categorize these risks for fifteen to twenty
- 3:00minutes by having participants share their notes one by one.
- 3:02The facilitator clusters similar concerns into distinct
- 3:04categories like Technical, Resource, or Stakeholder issues,
- 3:07which reveals patterns in thinking and ensures all voices
- 3:09are heard. This categorization transforms a chaotic list of
- 3:12worries into a structured map of potential failure points that
- 3:14the team can analyze systematically. It allows the
- 3:16group to see where their anxieties converge, highlighting
- 3:19the areas that require the most attention and discussion. The
- 3:21fourth step is root cause analysis, which takes twenty to
- 3:24thirty minutes and requires the team to ask "Why?" repeatedly
- 3:26for each major category. You link these causes back to
- 3:28current project decisions or assumptions, transforming vague
- 3:31worries into actionable insights grounded in reality. This
- 3:33process forces the team to look beyond surface-level symptoms
- 3:36and identify the underlying systems or choices that could
- 3:38lead to disaster. By connecting risks to specific project
- 3:40elements, you create a clear line of sight between present
- 3:43actions and future outcomes. The final step is mitigation
- 3:45planning, lasting fifteen to twenty minutes, where the team
- 3:47develops specific actions to prevent or mitigate the top
- 3:50three risks. These actions must be assigned to owners with clear
- 3:52deadlines, closing the loop from identification to prevention and
- 3:55ensuring accountability. This step turns the exercise from a
- 3:58theoretical discussion into a practical plan that integrates
- 4:00directly into the project workflow. The output is a
- 4:02concrete risk mitigation plan that the team can reference and
- 4:05act upon immediately. That completes the five-step
- 4:07execution sequence, and the next section examines the common
- 4:09pitfalls that can derail this process.
- 4:16Let’s say you run the session and hit one of three common
- 4:19pitfalls. First, if your scenario is too vague, like just
- 4:22saying the project failed, participants struggle to
- 4:24generate specific risks. The recovery is simple: refine the
- 4:27narrative to a concrete outcome, such as losing a key client due
- 4:30to poor communication. This specificity triggers the brain’s
- 4:32ability to simulate reality, which means you get sharper,
- 4:35more actionable insights from the group. Second, watch for
- 4:38the blame game, where participants start pointing
- 4:40fingers at individuals rather than processes. You must enforce
- 4:43a strict no blame rule and redirect comments by asking what
- 4:45process allowed this to happen. This shift keeps the focus on
- 4:48systems and decisions, not people, which preserves
- 4:50psychological safety and ensures the team stays focused on fixing
- 4:53the workflow rather than attacking colleagues. Third,
- 4:56avoid the trap of lack of follow-through, where
- 4:58identifying risks without acting on them creates a false sense of
- 5:01security. Integrate the mitigation plan directly into
- 5:03your project management tool and review these risks in regular
- 5:06stand-ups. This ensures the work doesn’t disappear after the
- 5:09session ends. Applying these recovery strategies turns the
- 5:12exercise from a theoretical discussion into a practical
- 5:14shield against failure, and next we’ll look at how to practice
- 5:17this technique in your own projects.
- 5:24Consider your last project where things went sideways. Pause and
- 5:27think about how you would adapt the Silent Brainstorming step
- 5:30for a remote team using anonymous polling. This small
- 5:32tweak prevents dominant voices from steering the conversation
- 5:35early, ensuring every risk gets equal weight. You can identify
- 5:37one current project where you will apply the Specific Failure
- 5:40Scenario technique this week. Instead of vague worry, define a
- 5:43concrete narrative like losing a key client due to poor
- 5:45communication. Then schedule a fifteen-minute Mini Pre-Mortem
- 5:48for your next big decision. Skip the categorization step entirely
- 5:51and focus only on the top three risks. That brings the lesson
- 5:54full circle, back to the listener and the moment they
- 5:56will first put the protocol into practice.
- 6:01Welcome to The Take. I'm joined by a fellow practitioner and
- 6:04together we're going to dig into Pre-Mortem: A Practical Guide —
- 6:07what it means in practice and what's worth remembering.
- 6:11[HOST] I keep thinking about that silent writing phase. It
- 6:14feels counterintuitive to silence the room when you want
- 6:17energy, but it’s the only way to kill groupthink. [LEARNER]
- 6:20Exactly. I tried skipping it once on a tight deadline. The
- 6:23loudest engineer dominated the first ten minutes, and we missed
- 6:26three critical integration risks because nobody else felt safe
- 6:29speaking up. [HOST] That’s the trap. You trade speed for
- 6:32safety, and safety is what lets you find the real problems. But
- 6:36I’m worried about the root cause mapping step. It’s easy to slide
- 6:39into blaming people instead of processes. [LEARNER] Oh,
- 6:42absolutely. I had to intervene last week when someone blamed
- 6:45the design team for a delay. I forced them to ask why the
- 6:48handoff protocol failed, not why the designers were slow. It
- 6:51shifted the room instantly. [HOST] Good call. Redirecting to
- 6:54the system preserves psychological safety. Now, what
- 6:57about using AI to help draft those failure scenarios? Could
- 7:00we prompt an LLM to generate catastrophic outcomes based on
- 7:03our project scope? [LEARNER] I’ve experimented with that.
- 7:06It’s surprisingly good at listing generic technical
- 7:09failures. But it lacks the political context. It won’t
- 7:12predict that the stakeholder will ghost you because of a
- 7:14budget freeze. [HOST] Right. AI gives you the obvious risks, but
- 7:18humans bring the hidden ones. You still need the team to fill
- 7:21in the gaps that data misses. So how do you ensure the mitigation
- 7:24plan actually sticks? [LEARNER] I treat it like any other
- 7:27ticket. If it’s not in Jira, it doesn’t exist. I assign an owner
- 7:31and a deadline right there in the workshop. Otherwise, it’s
- 7:34just a nice conversation we had. [HOST] Accountability is the
- 7:37glue. Without it, the pre-mortem is just theater. We identify the
- 7:40risks, but we don’t prevent them. [LEARNER] True. It’s the
- 7:43difference between knowing the house might burn and actually
- 7:46buying a fire extinguisher. [HOST] Precisely. The insight is
- 7:50useless without the action. Let’s make sure we’re building
- 7:53the extinguisher, not just spotting the smoke.