Hello again. In our previous lesson, we practiced turning the lens of critical thinking inward, using the Automatic Thought Record to catch and reframe cognitive distortions after the fact. This was an important, reactive skill for building self-awareness.
Today, we shift from reacting to the past to proactively shaping the future. We will explore the 'pre-mortem,' a powerful technique for stress-testing a plan before you even start. For someone with your background in systems engineering, you can think of this as a structured form of failure mode analysis applied to project strategy, not just technical components. This lesson is designed to give you a concrete, repeatable method for challenging assumptions and spotting risks early, which is a cornerstone of the confident, out-of-the-box thinking you're looking to cultivate.
1. What if We've Already Failed?
Standard project kick-offs are often exercises in optimism. Team members are encouraged to align on a vision of success. But what if we started by doing the exact opposite?
The pre-mortem is a thought experiment that does just that. You gather the team before a project begins and ask them to imagine that the project has gone forward and has failed spectacularly. Then, you ask: "What went wrong?"
This simple flip in perspective is remarkably effective. Psychologist Gary Klein, who developed the technique, found it dramatically improves a team's ability to identify risks compared to simply asking "What might go wrong?" Let's hear from Klein himself on how he invented the pre-mortem and the psychological dynamics that make it so powerful.
Insights for Making Better Decisions | Gary Klein | Knowledge Project 144
In this excerpt from The Knowledge Project podcast, Gary Klein explains the origins of the pre-mortem and why it works so well to overcome the psychological barriers that typically prevent people from voicing concerns.
First, watch the segment where Klein describes how he came up with the idea and contrasts it with a traditional post-mortem: the origin story. Next, listen as he explains the advantages of the technique, particularly how it reverses the usual meeting dynamic and encourages candor: the benefits.
As Klein explains, the pre-mortem works by subverting several cognitive biases at once:
- It counters optimism bias and groupthink: By making failure the starting point, it legitimizes critical and pessimistic thinking, which is often suppressed in a kick-off meeting's enthusiastic atmosphere.
- It leverages prospective hindsight: Imagining an event has already happened makes it easier for our brains to generate causal explanations.
- It creates psychological safety: Instead of being seen as a naysayer, a team member who identifies a clever reason for failure is seen as a valuable contributor.
2. The Pre-Mortem Process
While the core idea is simple, its effectiveness comes from a structured execution. For a systems engineer, having a reliable process is key. The following reading provides a clear, step-by-step guide for conducting a formal pre-mortem.
Pre-Mortems in Project Management: A Practical Guide for Teams
This guide from MadDevs outlines a comprehensive, seven-step process for running a pre-mortem meeting. This provides the kind of structured framework that can be adapted for any project.
Please read the section titled "7 steps to run in the pre-mortem meeting." Pay close attention to each step, from establishing the plan to revising it based on your findings. Focus on the flow: the preparation and brainstorming, and then the actionable follow-up.
3. Your Turn: Pre-Mortem on a FinTech Project
Now, let's put this into practice. This is a solo exercise to help you internalize the process.
The Scenario: You are the lead engineer for a new project at your finance company. The goal is to build an automated trade reconciliation tool. This tool will replace a manual, spreadsheet-based process that is slow and error-prone. The project team consists of you, another developer, a QA tester, and a product manager.
Step 1: Imagine Spectacular Failure
Fast-forward eight months. The project is a complete disaster. The tool has been delivered, but adoption is near zero. The traders who are supposed to use it have reverted to their old spreadsheets, complaining that the new tool is "unreliable and more confusing than the old way." Your manager is now questioning the value of the project and is considering writing it off as a total loss.
Step 2: Brainstorm the Causes
Take 5-10 minutes and write down all the reasons you can think of for why this failure occurred. Your list should have at least 5-7 distinct causes. To get you started, think about different categories:
- Technical: e.g., "Our technology stack wasn't scalable to handle peak trading volumes."
- Process: e.g., "The requirements from the product manager kept changing every week."
- People: e.g., "The senior trader who was our main champion left the company mid-project."
- External: e.g., "A new compliance regulation was introduced that our architecture couldn't support."
Crucially, as we discussed in our last lesson, don't forget the subtle psychological factors. To get a better sense of these often-overlooked causes, watch the following video. It provides a rich list of potential failure points, especially internal ones.
The Pre-mortem Technique - The Trick To Avoiding Project Failure
The presenter in this Actualized.org video gives an extensive list of reasons why a new business might fail. The logic applies perfectly to any project.
Watch the section from the business example. Listen for the distinction he makes between external factors (like the economy) and internal, psychological factors (like analysis paralysis or perfectionism). Let this inspire your own list of causes for the failed reconciliation tool project.
Step 3: Prioritize and Mitigate
Look at your list of causes.
- Identify the two most likely reasons for failure.
- For each of those two, brainstorm one concrete, actionable strategy you could implement at the beginning of the project to mitigate that risk.
For example:
- Cause: "The traders didn't trust the tool's output because they didn't understand its logic (a 'black box' problem)."
- Mitigation Strategy: "From week one, schedule bi-weekly 30-minute demos with the lead traders. Build a 'validation' feature that allows them to run a small sample of trades through both the old and new systems and see a side-by-side comparison."
4. Pro Tips for Effective Pre-Mortems
Running a pre-mortem well requires care. Here are two final tips to maximize the technique's value.
1. Framing is Everything
As Gary Klein emphasizes, the wording is crucial. A common mistake is to soften the premise.
Insights for Making Better Decisions | Gary Klein | Knowledge Project 144
In this final clip, Gary Klein highlights the most common mistakes people make when trying to run a pre-mortem.
Listen to his explanation of the most critical error: incorrect framing.
The power of the technique comes from the certainty of the premise: the project has failed. Asking what could go wrong keeps you in a mode of speculation. Stating that failure is a fact forces you into a mode of explanation, which is more powerful.
2. Get Creative with Categorization
Sometimes, brainstorming can get stuck on obvious risks. One creative technique to encourage deeper thinking is to categorize risks as "Tigers, Paper Tigers, and Elephants."
Pre-Mortems in Project Management: A Practical Guide for Teams
This section from the MadDevs article introduces a simple but effective vocabulary for classifying risks.
Read the short section "Pre-mortem fun technique: Tigers, Paper Tigers, and Elephants." Understand the definition of each: Tiger: A real, significant danger. Paper Tiger: A risk that seems scary but you believe is not a real threat. Elephant: The undiscussable topic that everyone is avoiding.
This vocabulary provides a safe way to raise sensitive issues ("I think we have an elephant in the room about the project deadline") and to challenge overblown fears ("Is that a real tiger, or just a paper tiger?").
Conclusion
Today we added the pre-mortem to your thinking toolkit. It's more than just a risk-management exercise; it's a powerful method for systematically challenging the optimism and hidden assumptions that often lead projects astray. By deliberately adopting a pessimistic viewpoint in a structured way, you can uncover weaknesses in a plan before they become costly failures.
Key Takeaways:
- The pre-mortem is a proactive technique that imagines project failure at the outset to identify risks.
- It works by leveraging prospective hindsight to overcome optimism bias and encourage candid feedback.
- A structured process involves imagining failure, brainstorming causes, prioritizing them, and creating mitigation plans.
- Focusing on psychological and internal causes of failure is just as important as identifying external ones.
In our next lesson, we will begin a new module focused entirely on the art of deconstructing problems by uncovering assumptions. The pre-mortem is an excellent tool for finding dangerous assumptions in a plan. Next, you will learn a more general method for mapping out all the assumptions—explicit and hidden—that underpin any given problem.