What The Framework Offers
A premortem gives a team permission to be constructively pessimistic before commitment becomes identity. Instead of asking "what might go wrong?", it asks people to imagine the project has already failed and explain what did go wrong.
That small change matters. Concerns become the assignment rather than an act of disloyalty, which makes it easier for quiet risks to surface.
When To Use It
Use a premortem before a launch, agency engagement, large stock buy, hiring decision, platform migration, funding push, operational change or any plan where failure would be expensive, public or hard to reverse.
It is especially useful when the room is already excited. Optimism is not the enemy, but untested optimism is expensive.
The Premortem Flow
Premortem Output Template
| Risk | Early warning sign | Prevention action | Owner | Stop or redesign trigger |
|---|---|---|---|---|
| Orders arrive faster than fulfilment can handle. | Response times exceed one working day or errors repeat. | Cap launch volume and prepare packaging, support replies and dispatch rhythm. | Operations lead or founder. | Pause ads if backlog exceeds the agreed limit. |
| Agency produces assets the team cannot use. | First review shows missing examples, unclear ownership or slow feedback. | Write a sharper brief with examples, acceptance criteria and review cadence. | Project owner. | Do not extend contract if first milestone is unusable. |
| New hire enters a messy role. | Founder still approves every exception after two weeks. | Define decisions the role owns and what "good work" looks like. | Founder or manager. | Redesign role before adding more responsibility. |
Worked Example: The Ads Push
A founder wants to spend more on ads because early sales were encouraging. The premortem does not say "do not advertise". It imagines the campaign worked and still failed.
Failure story
The ads drove orders into two busy days. Packaging ran out, replies slowed, delivery promises slipped and refunds damaged trust. Revenue rose, but the operation bent around the founder.
Design response
Cap spend for two weeks, limit daily order volume, prepare standard replies, pre-pack common items, define a backlog limit and review complaints before increasing spend.
Worked Example: The Contractor Brief
A contractor is hired to relieve workload, but the premortem reveals a different risk: the contractor cannot succeed because the founder has not translated the work out of their own head.
Likely failure
The founder is too busy to review work, examples of good output are missing and every decision comes back for approval. The business blames contractor quality when the real issue is unclear ownership.
Design response
Create a short brief, provide three examples, define acceptance criteria, set two review points and name which decisions the contractor can make without asking.
Common Failure Modes
- Theatre of pessimism The team lists scary risks but does not assign owners, early warning signs or prevention actions.
- Leader contamination The most senior person shares their worries first, and the room quietly organises around those concerns.
- Doom without design The exercise makes everyone anxious but does not reduce the size, timing or reversibility of the bet.
- Risk dumping Everyone names what could go wrong, but the work is handed back to the same overloaded founder.
- Late premortem The exercise is run after contracts, promises or spend have already made the plan hard to change.
What To Do With The Risks
Prevent
Change the plan so the risk is less likely: clearer brief, capped budget, smaller audience, backup supplier or better quality check.
Detect
Name the early warning sign: backlog, refund rate, complaint theme, cash threshold, missed milestone or slow handover.
Contain
Limit the downside before launch: pilot scope, daily order cap, short contract, manual fallback or staged migration.
Decide
Write the trigger that pauses, reverses or redesigns the plan. A risk without a decision rule is only a worry.
Quick Premortem Script
- State the plan in one paragraph.
- Ask: "It failed badly. What happened?"
- Write silently before discussion.
- Share one risk each until the list stops growing.
- Vote for the top risks by likelihood and consequence.
- Assign owner, early warning sign and prevention action.
- Decide what would pause or redesign the plan.
Connected Patterns And Decisions
Run decision quality first, then premortem the preferred option.
Archetype Optimistic OperatorThe archetype most likely to need a premortem before adding volume.
DecisionForge The Ads Machine Wants FeedingA clear case where growth can outrun operational capacity.
DecisionForge The Contractor BriefA useful place to premortem delegation before blaming the contractor.
DecisionForge Something BreaksThe downside of not naming fragile points early.
