Most launches fail in predictable ways, and most launch teams don't pre-mortem for them. The post-mortem happens after the launch, when the findings route to "next launch" and the current launch's damage is already done. The pre-mortem — a 45-minute meeting held three weeks before ship date — asks the team to imagine the launch has failed, then work backwards to identify why. It is the cheapest intervention in launch planning and the one most consistently skipped.
The pre-mortem concept originated with Gary Klein at the U.S. Army research lab and Daniel Kahneman popularized it. Its application to B2B SaaS launches is narrow: the pre-mortem catches positioning mistakes specifically. Not timing mistakes, not technical mistakes, not execution mistakes. Those belong in other reviews. The pre-mortem is a forcing function for the question most launch teams avoid asking: "is our positioning right."
Why three weeks before, not one
The timing matters. Three weeks is long enough to change the positioning if the pre-mortem surfaces a problem. One week is not. If the pre-mortem happens in the final sprint, the team will acknowledge the finding, nod gravely, and ship the launch anyway because the pricing page is already live and the press release is already embargoed.
Three weeks is the last window in which the positioning is genuinely changeable. The sales deck can be redrafted. The homepage hero can be rewritten. The battle cards can be re-scoped. Past that window, the pre-mortem becomes a retrospective in disguise — a ritual that makes the team feel rigorous while changing nothing.
Who should lead it
One person. Not a committee. The pre-mortem has to be facilitated by someone who is not the launch owner, because the launch owner has a psychological stake in the positioning holding up. The facilitator's job is to ask the seven questions, maintain the premise (that the launch has failed), and resist the team's instinct to defend the current plan.
The right facilitator is typically a senior PMM from an adjacent product line, a director of marketing not involved in this specific launch, or occasionally the CMO if the launch is high-stakes and political cover is needed. The wrong facilitator is the launch PMM, the CEO (too senior for candor), or a cross-functional peer who benefits from the launch shipping on time.
The setup
Three weeks before launch. Forty-five minutes. Eight to ten people in the room: the launch PMM, the product lead, a sales leader, a CS leader, the content owner, and the facilitator at minimum. No decks are presented; the pre-mortem starts with the facilitator reading a single framing sentence out loud.
"It is three months after this launch. The launch has failed. The positioning did not land, sales cannot articulate the new offer, and prospects are confused about what we do. Take five minutes to write, individually, what went wrong."
Five minutes of silent writing. Then the facilitator works through the seven questions below, soliciting the room's anonymized pre-written notes at each step.
The seven questions
Each question is designed to surface a specific category of positioning mistake. The facilitator asks the questions in order, and the team's job is to take the premise seriously — imagining the failure mode rather than defending the current plan.
1 · "The sales team couldn't explain it. Why not?"
This question catches the internal-clarity problem. Sales can usually articulate a launch if the positioning is sharp and the message is memorable. They cannot articulate a launch if the positioning uses adjective-heavy language, references unfamiliar frameworks, or depends on context a prospect doesn't have.
A useful follow-up: "Have three people in this room try to articulate the launch in one sentence right now, without looking at the deck." The variance is almost always the answer. If three people produce three different one-sentence versions, the sales team will produce forty different versions.
2 · "The press release didn't get picked up. Why not?"
This question catches the newsworthiness problem. Trade press picks up launches that either create a new category, signal a strategic shift, or produce genuinely novel data. Launches that are feature improvements dressed up as category-creating usually get ignored, and the pre-mortem has to ask whether the launch has a real news angle or an aspirational one.
The honest answer often: "The launch is a good feature but not a news event, and we've been pretending otherwise in the press materials." If that's true, the fix is smaller than it sounds — reframe the PR effort toward paid amplification or customer advocacy rather than earned media. The alternative is embarrassment on launch week when no outlet writes about the launch.
3 · "Prospects clicked the CTA but didn't convert. Why not?"
This question catches the conversion-path problem. A launch with strong interest at the top of funnel can still fail at the conversion step if the CTA doesn't match the buyer's readiness or if the subsequent experience doesn't match the launch narrative.
A specific check: what happens when a prospect clicks "book a demo" the day after launch? If the demo flow shows the standard product and doesn't specifically demo the new capability, the launch has a conversion-path problem. If the demo script wasn't updated, the conversion-path problem is still there.
4 · "Customers we already have churned or downgraded. Why?"
This question catches the existing-customer problem. Launches that introduce new tiers, new capabilities, or new positioning can inadvertently signal to existing customers that they are in the wrong plan, using the wrong features, or no longer in the target ICP. The pre-mortem has to check whether the launch produces unintended negative signals for the installed base.
We launched a new enterprise tier and saw 12% of our mid-market customers initiate renewal conversations within 60 days — because the launch copy implied they were now in the 'junior' tier. We had to publish a clarification post and restructure the tier naming. A pre-mortem would have caught it for a quarter of the cost.
5 · "The competitor matched it within two weeks. How?"
This question catches the differentiator-durability problem. If the launch's core differentiator is a single feature that the competitor can ship quickly, the launch's half-life is short. The pre-mortem asks whether the positioning rests on a sustainable differentiator (process, narrative, installed base) or a temporary one (feature).
If the honest answer is "the competitor will match this in six weeks," the launch narrative should shift toward a differentiator with longer durability — usually process or narrative — even if the feature is what's technically shipping.
6 · "The board meeting slide about the launch was thin. Why?"
This question catches the executive-narrative problem. If the launch's first-quarter results are going to be presented on a board slide, the launch has to produce a specific, measurable outcome that survives a board-level summary. Launches that produce soft signals ("customer engagement," "market presence") usually read as theater at the board level.
The pre-mortem forces the team to draft the board slide now — what specific number will appear on it? If no specific number can be named, the launch's measurement plan needs work before ship date.
7 · "We re-ran the launch six months later. What did we change?"
This question is the integration question — it forces the team to imagine the retrospective they'll write and asks what from the retrospective could be anticipated now. The answers here are often the most useful, because they surface the "we should have known" items the team secretly suspects but has not articulated.
Preparing the room for the pre-mortem
The post-pre-mortem follow-up
The pre-mortem produces findings; the follow-up produces changes. The 48-hour window after the meeting is when the launch owner and the facilitator meet privately to triage the findings. Some will be actionable in the three-week window; some will be tabled for the post-mortem. Each finding gets a status — "fixing before launch," "accepted risk," or "revisit in retro" — and that status goes into the launch plan.
The discipline is that "accepted risk" is a legitimate outcome but has to be named out loud. A finding that's quietly ignored will surface later as an unforced error. A finding that's named as an accepted risk is a conscious choice the team has made and can explain if it becomes a problem.
Most launches will emerge from the pre-mortem with two or three changes scheduled before ship date, a few findings tabled as accepted risks, and a note in the launch plan. The cost is 45 minutes plus a 90-minute follow-up. The value is catching the positioning mistakes that would otherwise become the next post-mortem's findings — after they had already damaged the launch's outcomes.
Launch Playbook
Drafts the announcement, FAQ, and battle-card patch from your Strategic Context when you ship.
See how it worksOne sharp positioning read, most Thursdays.
Field-tested frameworks, teardowns, and pattern notes from our working library. No "Top 10" lists. No launch roundups. Unsubscribe whenever.
Keep reading
Product Launch Narrative Checklist (No Fluff)
Twelve items every launch narrative has to pass before the campaign ships — no inspirational quotes, no mood boards, just the checks that keep the story from sounding like every other launch.
Feature Launch vs. Narrative Launch: Why Most Fail
A feature launch announces shipped code. A narrative launch advances a point of view. Why the latter is memorable, sellable, and defensible — and the test for which one you're running.
Launch Positioning for Enterprise vs. SMB
A single launch narrative almost never works across both ends of the market. Here's the two-track positioning playbook, the seven places the tracks have to diverge, and the one they should stay identical.