Risk Before Rescue: How to Think About Failure Before It Happens

Think about the last major decision you made at work. A new hire, a product launch, a process overhaul, or a budget commitment. What did you do before you made the call?

Most leaders spend their pre-decision time doing one thing: building the case for yes. They calculate projected ROI, draft launch timelines, and visualize success. There is genuine value in that posture. But there is a significant gap in that approach, and most leaders never notice it until they are standing in the wreckage of a decision they were certain would work.

They planned carefully for success. They forgot to plan for failure.

This post is about two tools that fix that gap: premortems and decision checklists. Neither is complicated. Both are dramatically underused. And together, they will change how you make high-stakes calls.

The Problem With Positive Thinking

There is a cognitive bias called optimism bias, and it operates like a silent saboteur inside your decision-making process. Optimism bias is the tendency to overestimate the likelihood of good outcomes and underestimate the likelihood of bad ones. It affects almost everyone, and it gets stronger the more emotionally invested you are in an outcome.

In leadership, optimism is celebrated. Setting the vision and committing to it is practically a commandment. And there is real value in that posture. Leaders who catastrophize every decision never make any. But optimism without analysis is not boldness. It is blindness.

Here is a number worth sitting with. According to research from the Harvard Business Review, approximately 70% of organizational initiatives fail to meet their stated objectives. Not fail outright. Fall short. Scope reduction, budget overruns, missed timelines, and underperformed metrics. Seven out of ten.

One of the most consistent culprits is that decision-makers and project teams systematically underestimate the risks they could have seen coming. Not black swan events. Not global disruptions. Predictable operational problems that were hiding in plain sight.

A key supplier relationship that was shakier than anyone acknowledged. A technology dependency nobody had stress-tested. A team capability gap that was visible but uncomfortable to raise. These are the risks that kill projects. And they are the risks that a premortem is specifically designed to surface.

What Is a Premortem?

A premortem is a structured exercise where you imagine that a project or decision has already failed, then work backward to figure out why.

The concept was formalized by cognitive psychologist Gary Klein, and the mechanics are straightforward: before you launch, before you sign the contract, before you finalize the plan, you gather your team and say, "Imagine we are six months from now. This project is dead. It completely fell apart. What happened?"

That framing matters more than it might seem. Most teams spend pre-launch time identifying risks in the abstract. What could go wrong? But abstract thinking produces abstract answers. The premortem creates a specific, vivid scenario: failure has already occurred. Now your brain is not evaluating risk. It is reconstructing a past event. And humans are very good at that.

Research from the Wharton School found that prospective hindsight, thinking about the future as if it has already happened, increased the ability to correctly identify reasons for future outcomes by 30%. That is not a marginal improvement. That is a meaningful jump in your team's ability to see what it is missing.

The premortem works for three reasons.

First, it gives people permission to voice concerns they would not otherwise raise. In most teams, there is social pressure to align once leadership has committed to a direction. The premortem explicitly breaks that pressure. Identifying failure points is not disloyalty. It is the exercise.

Second, it surfaces diverse failure scenarios. When you ask what could go wrong, the most senior or most vocal person in the room typically dominates. When you tell everyone the project has already failed and ask what happened, you get much more varied responses. Each person draws from their own domain expertise and their own history with failure.

Third, it creates a record. The outputs of a premortem are not just conversation. They are documented risks that can be tracked, mitigated, and monitored throughout execution.

How to Run a Premortem

Running a premortem does not require a consultant, a special platform, or a full day off-site. Here is the process in five steps.

Step 1: Set the scene.

Make the failure specific and vivid. Say something like: "It is six months from now. This project is a complete failure. We missed the deadline, we are over budget, the client is furious, and leadership is asking what happened. What went wrong?" The specificity of the imagined failure drives the specificity of the responses.

Step 2: Write independently before speaking.

This is the most commonly skipped step and the most important one. Give everyone three to five minutes to write their own failure scenarios in silence before the group discussion begins. Group conversations are shaped by whoever speaks first. Independent writing breaks that pattern and generates more honest, diverse thinking across the whole room.

Step 3: Collect all responses without judgment.

Go around the room and capture every scenario without evaluation or pushback. Your goal in this phase is to generate, not filter. Nothing gets dismissed.

Step 4: Prioritize by likelihood and impact.

Once you have the full list, work through it together. Which scenarios are most likely? Which would be most damaging if they occurred? Where likelihood and impact intersect, those are your highest-priority risks.

Step 5: Assign ownership.

For each high-priority risk, name the person responsible for addressing it. Their job is to either eliminate the risk or build a mitigation plan before the project launches. Give them a specific deadline and a clear reporting structure.

The whole exercise takes about 45 minutes to an hour for a complex initiative, and as little as 20 minutes for smaller decisions. When that hour prevents a six-figure mistake, the return is extraordinary.

A Real-World Example

Premortems are sometimes positioned as tools for large corporate initiatives. They work at every scale, and this example shows why.

Toby's Taco Truck had been operating solo for two years in a downtown business district. Consistent lunch crowd, strong reviews, loyal regulars. Then an opportunity arrived: a technology company wanted to book the truck for a full-day corporate catering event. Four hundred guests, four hours, the biggest single-day revenue contract in the business's history.

The obvious answer was yes. But before signing anything, the owner ran a 20-minute premortem.

The question: "It is the day after the event. It was a complete disaster. The client wants a refund and is threatening a public review. What happened?"

Three failure scenarios emerged quickly.

The kitchen could not handle the volume. The truck was built for a lunch rush that builds and tapers over 90 minutes. Four hundred people in a four-hour window is a completely different demand curve. At peak, ticket times tripled, and the line stretched off the client's property.

The meat supply chain broke down. Feeding 400 people required ordering three times the normal weekly protein volume. The primary supplier could not fill the full order on short notice. The backup supplier's quality was inconsistent. The tacos people showed up for were not the tacos they received.

Staffing fell through. One additional helper was not enough for that volume. Service slowed, the register became a bottleneck, and the operational strain showed in the food.

None of those scenarios is catastrophic in isolation. Together, they describe an event that would have earned one-star reviews, damaged a relationship with a company that employs 600 people who all go to lunch somewhere, and turned the biggest revenue opportunity in the business's history into its most visible failure.

The premortem did not kill the deal. It changed the deal. The owner negotiated a higher rate that covered two additional staff members, sourced a second protein supplier, and simplified the menu specifically for high-volume output. The event ran without problems. The company booked a follow-up three months later.

That is what a premortem does. It does not stop you from taking the leap. It makes sure you do not trip on the landing.

Decision Checklists: The Companion Tool

The premortem surfaces failure scenarios. The decision checklist ensures you have addressed the critical thinking steps before you commit.

Checklists have a mixed reputation in professional environments. In some cultures, they are seen as tools for beginners. If you have been making decisions for twenty years, why would you need a checklist?

Because the data does not support that confidence.

In 2009, the World Health Organization introduced a standardized 19-item surgical safety checklist into hospitals across eight countries. The results were published in the New England Journal of Medicine. Major complication rates dropped by 36%. Deaths dropped by 47%. These were not inexperienced surgeons. These were trained professionals with years of expertise. And the checklist caught things that their experience and confidence did not.

Pilots use pre-flight checklists before every single flight, regardless of logged hours. The checklist is not an insult to their skill. It is a cognitive backstop against the specific failure mode expertise creates: overconfidence.

Here is a practical framework organized into five categories. Work through each one before finalizing any high-stakes decision.

Clarity

Can you state the decision in one clear sentence? If you cannot, you have not defined it well enough to decide well.

Do you know what success looks like and how you will measure it? Vague success metrics make it impossible to assess outcomes.

Have you defined the point of no return? At what moment does this decision become difficult to reverse?

Stakeholders

Who is affected by this decision beyond the obvious people in the room? Have you gotten input from people who will be impacted, not just people who already agree with you?

Is there someone in your organization who thinks this is a bad idea? Have you actually heard their reasoning?

Data

What data are you relying on, and how confident are you in its accuracy?

What data would change your mind? And is there any way to get that data before deciding?

Are you making this decision on facts or on a narrative you have built around the facts? Humans connect data points into stories that feel coherent. But the narrative is not the data. Sometimes the narrative is just wishful thinking dressed in spreadsheets.

Risk

What is the worst realistic outcome if this fails? Not the worst theoretical outcome. The worst realistic one. Can your organization, your team, or your project survive that outcome?

Have you run a premortem?

Reversibility

How easy is it to reverse this decision if it does not work?

Some decisions are two-way doors. You go through, find out it does not work, and come back. Those deserve solid diligence but not paralysis. One-way doors are different. Signing a long-term lease, selling a business unit, or committing to a major strategic partnership. Those are much harder to reverse, and they deserve a level of scrutiny most teams do not apply. Your checklist helps you know which door you are walking through before you step.

Putting It Together

Premortems and decision checklists work best as a pair. Here is how they fit together in practice.

Start with your tentative decision. Get clear on what you are inclined to do. Hold it loosely.

Run the decision checklist. Work through each category. Flag weak answers, knowledge gaps, and assumptions you have not tested.

Run the premortem. With your tentative decision on the table, bring your team together and ask them to imagine it has failed. Collect their failure scenarios. Document everything.

Map the overlap. Where do your checklist gaps and premortem failures intersect? Those intersections are not peripheral risks. They are priorities. Address them before finalizing.

Then decide. Not with false certainty, because certainty in decision-making is a myth. With clear eyes, a solid process, and a record of how you got there.

The Leadership Case

Leaders who use premortems and decision checklists do not become timid or indecisive. In practice, the opposite tends to happen. They become more decisive because they are not paralyzed by unexamined fear. They have looked at the risks directly. They know what they are taking on. And they are moving forward because they assessed the situation, not because they avoided the assessment.

The leaders who skip this process are not braver. They are less informed. In a high-stakes environment, the difference between courage and recklessness is usually the quality of the thinking that came before the action.

Great leaders do not avoid failure. They prepare for it, plan around it, and learn from it systematically. Premortems and decision checklists are two of the most practical tools available for doing exactly that.

Bring them into your next project kickoff. Use them on your next major hire. Apply them to the next budget decision or strategic initiative. And notice what changes.

For more tools and frameworks built for leaders and professionals, head to toby-talks.com. That is where everything lives.