Standard risk identification at kickoff goes like this: “Are there any risks we should be aware of?” The client says something general. You nod. Everyone moves on feeling like they addressed it. Three weeks later, the exact thing nobody wanted to name happens, and everyone acts surprised.
The pre-mortem breaks this pattern by changing the question. Instead of “what might go wrong?” you ask “it went wrong, what happened?” The shift from hypothetical future to imagined past unlocks honesty that forward-looking questions suppress. People know why projects fail. They just don’t like saying it out loud when there’s still hope.
The pre-mortem removes the hope. It puts the failure in the room. And once it’s in the room, you can work on it.
The Psychology Behind Why Pre-Mortems Work
When you ask “what could go wrong?” you’re asking people to voice pessimism in a room full of people trying to project confidence. The client just hired you. They want to believe in the project. Nobody wants to be the person who lists all the reasons it won’t work.
The pre-mortem reframes the conversation as an intellectual exercise, not a complaint session. “Pretend it failed” is speculative, it doesn’t accuse anyone or predict doom. It gives people permission to be honest without being negative.
The result is that information surfaces in a pre-mortem that would never surface in a risk review. The client mentions the internal politics around this project. Someone names the real reason the last vendor didn’t work out. The project lead admits they haven’t fully briefed their CEO. These are the risks that will actually derail the project. They just needed a framing that made them safe to say.
The 20-Minute Pre-Mortem Agenda
Run this at the end of your kickoff meeting. You need 20 minutes and a shared document or whiteboard. Here’s the script:
0:00, Frame the exercise (2 minutes)
“Before we wrap up, I want to do a quick exercise that I run with every new client. It’s called a pre-mortem, it takes about 20 minutes and it’s genuinely the most useful thing we can do at this stage.
Here’s the setup: imagine it’s three months from now and this project didn’t go the way we hoped. Not catastrophically, just didn’t quite land. In your experience, what are the most likely reasons that would happen? I want everyone to take 3 minutes and write down 2-3 things independently. Don’t edit yourself, write what comes to mind.”
0:02, Independent writing (3 minutes)
Silence. Everyone writes. This step is non-negotiable. If you skip individual writing and go straight to group sharing, you get the socially safe answers from whoever talks first, and everyone else nods along. Independent writing produces divergent answers. Divergent answers surface real risks.
You write too. Your independent list captures what you see as a risk from your professional experience, risks the client can’t identify because they don’t know what you know about how similar projects fail.
0:05, Round-robin sharing (8 minutes)
Go around the group and ask each person to share one item. Write everything on a shared document or whiteboard. No discussion yet, just capture.
Keep going until the list is exhausted. You’ll typically get 8-15 items from a group of 3-5 people. Common items you’ll hear:
- “We don’t have full stakeholder alignment internally”
- “The timeline feels tight given our approval process”
- “We’ve tried something similar before and it stalled because [reason]”
- “Budget is contingent on Q2 performance”
- “The team member who knows this system is leaving in 6 weeks”
Capture every item verbatim. Don’t rephrase, their exact language matters for the mitigation conversation.
0:13, Prioritize (5 minutes)
Group similar items and dot-vote on the top 3-4 by a combination of probability and impact. You can do this informally: “Of everything on this list, which 3 are you most worried about? Just call them out.”
You’re looking for items that have high consensus (multiple people flagged it) or high specificity (someone named a concrete scenario, not a vague “communication issues”). These are the real risks.
0:18, Assign mitigations (2 minutes)
For each top risk, answer two questions: “What would we do to reduce the chance of this happening?” and “Who owns that action?”
This is not a deep planning session, you’re assigning responsibility for a follow-up action. “Sarah will schedule a stakeholder alignment meeting before Week 2.” “I’ll build a 5-day legal review buffer into the project plan.” “We agree to escalate if approval takes more than 3 business days.”
Quick assignments. One owner per item. You’ll do the full mitigation planning after the call.
The pre-mortem doesn’t predict the future. It surfaces the organizational knowledge that was already in the room but had no venue to be spoken. Your clients know why projects fail in their organization. They just needed someone to ask.
The Document Produced
After the call, send a “Pre-Mortem Summary” email within 2 hours. This is the artifact that gives the exercise value:
Subject: Kickoff Pre-Mortem Summary, [Project Name]
Hi [Name],
Following today’s kickoff, here’s the pre-mortem summary for the record.
Top risks identified:
- [Risk], Owner: [Name], Mitigation: [Action], By: [Date]
- [Risk], Owner: [Name], Mitigation: [Action], By: [Date]
- [Risk], Owner: [Name], Mitigation: [Action], By: [Date]
Full list from the exercise: [Everything from the whiteboard/doc, ungrouped]
I’ve added the top three to the project risk register. I’ll reference them in my weekly Friday update.
[Your name]
This email does three things. It confirms that both parties acknowledged the risks. It assigns ownership (which creates accountability). And it creates a paper trail, if Risk #2 materializes at Week 5, you can say “we flagged this at kickoff and assigned the mitigation to [name].” That’s a collaborative problem-solving conversation, not a blame conversation.
Facilitation Tips for Difficult Groups
The overly optimistic client: Some clients resist the framing. “This project won’t fail, we’re going to make sure it works.” Accept the premise, then push: “I completely agree. The pre-mortem is actually how we make sure, we’re identifying things to prevent, not predicting. What would we want to make sure we avoid?” Most clients relax once they understand it’s prevention-oriented.
The dominating voice: If one person is talking first every round and others are deferring, break the pattern explicitly: “Let’s hear from [other person] on this one.” Independent writing makes this easier because everyone has their own list before anyone speaks.
The surface-level response: If someone gives a vague answer (“communication issues”), probe: “Can you say more about what that typically looks like in your organization? Is there a specific scenario you have in mind?” Specificity is the goal. “We’ve had issues where the client’s legal team needs to review and it takes 3 weeks” is actionable. “Communication issues” is not.
The 1-on-1 client: If you work solo with a single point of contact, run the pre-mortem as a conversation rather than a group exercise. You can skip the silent writing and go straight to the question: “Walk me through how this project could go sideways from your side, what would be the most likely cause?” The solo version takes 10 minutes and still surfaces the critical information.
What Changes After Running a Pre-Mortem
The immediate change is a more complete risk register and a more honest project plan. The deeper change is to the relationship dynamic.
Clients who go through a pre-mortem with you have had a different kind of conversation than they’ve had with other vendors. They’ve been asked to be honest about their organization’s failure modes, and they were. That level of candor early in a relationship changes how they communicate with you throughout.
They’re less likely to hide problems. More likely to flag issues early. More likely to treat setbacks as shared challenges rather than your failures. The pre-mortem signals that you’re capable of handling difficult conversations, so clients bring you more of them.
Run it at every kickoff. Even 15-minute version. Even for small projects. The habit is worth more than any individual pre-mortem output.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
