The short version: a pre-mortem asks your team to assume the forecast has already been missed, then explain why. In Abacum, you can price those reasons against revenue, cash, and headcount before the meeting ends. The technique works because it changes who in the room can speak.
In 2007 Gary Klein published two pages in Harvard Business Review about why projects fail. His answer had nothing to do with complexity or bad estimates. It was that too many people are reluctant to speak up about their reservations during the all-important planning phase.
His fix was a technique he called a premortem. Get the team together before the work starts, tell them to assume it’s already failed, and ask what went wrong. Klein is precise about why the phrasing makes all the difference. Unlike a typical critiquing session, in which team members are asked what might go wrong, the premortem assumes the project has failed.
The research underneath it is older. In 1989, Deborah Mitchell, Jay Russo, and Nancy Pennington found that prospective hindsight, imagining that an event has already occurred, increases the ability to correctly identify reasons for future outcomes by 30%.
I keep thinking about that one in the context of forecast reviews. The ordinary monthly review, where somebody presents a number, and the room nods.
Your forecast review has a problem
The problem: a forecast review asks the owner of a number to defend it. That’s the structure. Sales brings the pipeline; the sales leader defends the pipeline; finance probes. Everybody knows their job is to hold the line on explaining the number they walked in with.
Which means the person most likely to know the forecast is wrong is the person least able to say it. Usually that’s the analyst who built the roll-up and knows three deals will move out of quarter. You ask that person whether they see any risks, in front of their boss, and the question has exactly one safe answer.
Hey, I know how that sounds. I ran meetings this way for years, and I thought I was being rigorous. Probing harder doesn’t fix it. Probing harder is what makes people defensive. Try a pre-mortem instead.
Structuring your pre-mortem
Put it before the roll-up, not after
Once a number exists in a deck, it has an author, and the meeting becomes about protecting it. Run the pre-mortem while the forecast is still a draft. Fifteen minutes, no slides.Ask questions in the past tense
Skip “what are the risks to Q4”. Ask this instead: It’s January; we missed Q4 by 12%. What happened? The tense lets somebody describe a failure that hasn’t cost anybody anything yet, because in that room it hasn’t happened.Price the top three risks
A reason isn’t worth much until it has a number and a contingency plan attached. Enterprise deals slipping a quarter becomes $2.1M in delayed revenue, pushing the hiring plan into Q2. That’s a plan you can act on.
Where tools actually help
No tool will run this meeting for you, and I wouldn’t trust one that claims it can. What software genuinely fixed is the pricing step. Somebody says enterprise deals slipped a quarter, and you should be able to move that assumption and watch it impact revenue, cash, and headcount before the meeting is over. That used to take a week and somebody’s weekend. Now it takes minutes.
Before your next forecast review, book fifteen minutes and ask one question in the past tense. Write down what comes back. Then go and price the top three. If you want more on the mechanics, our guide to building better forecasts covers seven approaches that hold up.
