You know that sinking feeling when a project collapses? When you’re sitting there going, “We should’ve seen it coming”? This is the thing, you probably did. Most project failures are not surprises. They’re simply issues that no one wanted to discuss sooner. That’s when this method, called a pre-mortem, which essentially makes you have those uncomfortable conversations before disaster strikes, comes as a great business strategy. It’s easy: you sit down with your team and imagine the project already failed. And then you ask why. Sounds dismal, yes. But here’s what you find: people just feel at liberty to share all those fears they’ve been staying quiet about. That budget issue? The unrealistic deadline, everyone knows it is? The technical problem someone’s been too afraid to raise? All of it surfaces. And if you know what can go wrong in advance, you can do something about it. That’s worth an hour of worst-case fantasising.
What a Pre-Mortem Really Is?
That’s how it works. You gather everybody and say something like, “Alright, six months down the line, and this thing totally crashed and burned. What went wrong?” Then you give folks a couple of minutes to scribble down their responses in private. No debating, no discussing, just everyone considering what might actually go wrong. Then you go around and discuss what everyone wrote and talk it through together. The magic isn’t in the exercise. It’s in what occurs when you reverse the typical script.
Typically, when you’re planning something, everybody’s in “make it work” mode. People want to sound upbeat and supportive. Nobody wants to be the negative person who rains on everyone’s parade. But if you ask them to actually imagine failure, suddenly it’s safe to tell the truth. In fact, that’s the whole exercise. You’ll be amazed at the number of people who have been thinking the same things in secret. Perhaps everyone knows the timeline’s insane, but nobody was brave enough to say it first. Perhaps there’s a vendor everyone’s nervous about but assumed someone else had vetted. Those common worries count a lot.
Why This Beats Learning from Mistakes
We’ve all endured those cringeworthy meetings after something hasn’t gone right. Everyone’s wading through the wreckage trying to determine what went wrong. Sometimes these meetings do serve to teach you for the next time. But by then, you’ve already lost money, wasted time, and possibly hurt relationships with customers or clients. It’s like waiting for your car to get a breakdown on the highway before you check to see if it needs an oil change.
A pre-mortem is merely preventive maintenance for your project. You’re looking under the hood before you ever get on the road. Can you still have issues? Certainly. But at least you’ve examined the obvious things and repaired what you can. The distinction between “we never saw this coming” and “we knew this could occur and here’s our contingency plan” is great. One makes you appear sloppy. The other makes you appear ready.
When to Actually Do This?
The optimal time is when you’ve completed planning but not actually begun. You’ve got your map, you know who’s working on what, you’ve got some numbers on the budget, but you haven’t yet signed huge contracts or spent significant money. You’re at that stage where it’s still relatively easy to change direction. Wait too long and you’ve already invested. Do it too soon, and you don’t yet know enough about the project to be able to dream up plausible problems.
This is most important when the stakes are high. If you’re introducing something new, risking a big portion of your budget on a notion, or implementing changes that will impact lots of people, take the time to do this. Low-risk, small projects? Perhaps you can omit it. But if failure would truly hurt, or if the project is complex with many variables, don’t omit this step. An hour or two now could save you months of headaches later.
How to Run One Without Making It Weird
Invite the right people to the room first. You need different perspectives, people from other teams, different levels of experience, people who will see things differently. Don’t invite just the optimists or the pessimists. You need those too. Begin by being incredibly clear about what you’re doing and why. Get everyone on board that this is not about killing the project or placing blame. You’re attempting to make it better.
Let individuals have time to think individually before others contribute. This is absolutely crucial. If you simply introduce the question, the most vocal individual will be the first one to speak, and everybody else will simply agree or add on to what was said. When individuals write first, you see greater honest diversity. Go around next and have all contribute what they wrote. Seek out the items that many people noted; those are most likely your greatest risks. After you have everything up there, discuss which issues are going to be most likely or most hazardous. Then determine what you’re really going to do about those.
What You Get Out of It
The largest victory is that individuals finally speak their minds. In typical meetings, there is this thing about being upbeat and accommodating. Individuals self-censor because they don’t want to appear challenging or non-supportive. However, when the entire exercise is about discovering issues, all of a sudden, it’s okay. Everyone is expected to shoot down. That authorisation shifts everything. You actually have honest conversations rather than diplomatic ones.
You catch assumptions you didn’t realise you were making, too. For instance, maybe everyone just assumed the IT department would take care of the tech end, but no one actually double-checked. Or maybe everyone assumed that customers would adore this new feature, but that’s unproven. When you’re purposefully searching for places where things might go wrong, these assumptions leap out at you. Then you can test them or make contingency plans. Your team walks away with more confidence, strangely enough. Sure, you just spent an hour visualising disaster, but now everybody knows you’ve thought it out and have contingencies in place.
What You End Up With
Your plan is different after a good pre-mortem. You may pay for things that can get held up. You may have a backup supplier in place in case your first one doesn’t work out. You may find you require more personnel or a different set of skills on the team. All of the unsubstantiated concerns become tangible risks that you can monitor. Rather than simply “may go over budget,” you have “if we do not secure prices by March, expenses could increase by 20 per cent.”
Individuals also feel more like a team afterwards. There is something about openly sharing what frightens you that unites people. Everyone feels their fears taken seriously. Everyone knows what lies ahead and what the strategy is for tackling it. When something does go wrong later, and something always does, nobody freaks because you’ve already discussed this as an option. You have a plan. You switch to plan B rather than scrambling around trying to decide what to do.
Easy Tools That Assist
You don’t have to be all fancy. A shared document or whiteboard is sufficient to take ideas down. Some people prefer using a spreadsheet to manage risks, what might happen, how probable it is, how terrible it would be, what you’re going to do about it, and who’s on it. That’s your risk register, and it’s just a neat list basically. Some teams do a SWOT exercise where you examine strengths, weaknesses, opportunities, and threats. That can give you a structure to think about.
But honestly, the single most valuable tool is simply having space in which people feel safe to be honest with you. Sometimes that involves establishing ground rules such as “no idea is stupid” or “we’re not judging.” Occasionally, it’s helpful to have an outside person facilitate the meeting so folks feel safer. The mechanics are much less important than people trusting that they can be open without reprisal.
Making It Actually Useful
Don’t do this once and never look back. As projects go forward, things change. Risks you were concerned about may no longer be an issue. New risks you didn’t even think about may arise. Schedule times to go back over what you discussed. Perhaps every month, or at significant milestones, grab that risk list and review it again. Are these still concerns? Did something new arise? Do your plans hold up?
Also, ensure that you are getting genuine diversity in the room. People involved in marketing are concerned about different things than operations people. New joiners notice things veterans overlook. Old hands have experience, but new employees are frequently aware of new problems. You want it all. And be curious in your tone, not accusatory. You’re trying possibilities together, not assigning blame. The instant it comes across as finger-pointing, people close off, and you lose all the value.
Why This Changes How Teams Work
When you do that on a regular basis, it shifts your entire business culture. Rather than acting like everything is okay until it isn’t, people learn to discuss problems up front. It doesn’t feel negative to say “hey, I’m concerned about this.” Teams working in this fashion deal with surprises more effectively because they’ve rehearsed, considering what might not work. Issues don’t faze them as much.
It also makes it simpler to cope with real failures. When something does go wrong after you’ve done a pre-mortem, you can look back and say, “Did we see this coming or is this new?” If you did predict it, what went wrong with your prevention plan? If you didn’t predict it, what did we miss? It turns failure into a learning opportunity rather than a game of blame. That’s the type of culture where individuals innovate and take intelligent risks, because they realise failure is not the end of the world, it’s merely information.
FAQs
1. Won’t this make everyone gloomy and destroy motivation?
No, actually, individuals feel more confident when they realise the team has considered issues and has contingency plans in place.
2. How long does this take?
Generally, one to two hours is enough for most projects, but larger or more complicated ones may require a little more.
3. Can I do this on my own, or do I have to get the entire team involved?
You can work through some of the risks on your own, but you actually need separate brains to catch things you would otherwise miss yourself.
4. What if we find issues we can’t solve?
That’s valuable information; perhaps the project requires major changes, additional resources, or perhaps it shouldn’t happen yet.
5. Should we report to stakeholders outside of the team about the risks that we identify?
Yes, reporting important risks to stakeholders helps to build trust and ensures everyone has realistic expectations upfront.
Stay updated with the latest news, innovations, and economic insights at Inspirepreneur Magazine.
