Teams can become attached to a plan once effort and reputation are invested in it. A pre-mortem creates a temporary change of perspective: participants imagine that the decision has been implemented and produced a disappointing result, then identify plausible causes. The exercise can reveal risks without requiring anyone to attack the proposal directly.

Frame the decision and the imagined outcome

State the decision, intended outcome, scope, assumptions, and time horizon. The exercise works best when the proposal is concrete enough to examine but still open to change. Give participants the same short briefing so discussion does not depend on private knowledge.

Ask everyone to imagine a specific future in which the plan failed to deliver its intended value or caused serious avoidable difficulty. This is not a prediction. Readers may also want to visit shaftdeals.com.

Create psychological safety by separating risk discovery from loyalty. A person who identifies a weakness is helping the decision. Senior participants should contribute after others when their opinions might shape the room too early.

Generate causes independently first

Give people quiet time to write possible causes before group discussion. Invite operational, customer, people, technical, supplier, timing, and governance perspectives. Encourage causes within the organization’s control as well as external events it must prepare to handle.

Useful prompts include:

• Which assumption proved false?
• What did customers or employees find harder than expected?
• Where did ownership or authority break down?
• Which dependency failed or arrived late?
• What warning sign did the team dismiss?
• What did the plan make difficult to reverse?

Collect the causes without debating them immediately. Combine duplicates only after preserving the meaning. You can also visit Konami-europe.net for more reading.

Avoid vague entries such as “poor execution.” Ask what action, condition, or missing capability would make the execution poor. Specific causes lead to useful safeguards.

Prioritize and design proportionate responses

Discuss which causes are plausible, consequential, and poorly controlled. Do not spend all the time calculating scores; written reasoning matters more. Identify existing controls and whether the team has evidence that they work.

For priority risks, choose a response: change the plan, gather evidence, add a checkpoint, clarify authority, prepare a fallback, or accept the risk explicitly. Give each action an owner and due date. Some findings may justify delaying the decision, while others need monitoring rather than prevention.

Name early warning signs and who will watch them. A safeguard that triggers only after failure offers little protection. Also identify a point at which the organization can pause or reverse the decision before further commitment.

Carry the learning into governance

Summarize the strongest risks, evidence, chosen actions, accepted exposure, and open questions for the decision-maker. Do not present the entire brainstorm as equally likely. Update the plan and decision record so the exercise affects real work.

Review warning signs after implementation and revisit the pre-mortem when assumptions change. For a related read on this site, see A Manager’s Guide to Giving Feedback That Leads.

Invite people close to the work as well as senior decision-makers. Frontline employees may understand handoffs, customer behavior, or tool limits that are invisible in a strategy document. Consider anonymous inputs before the session when status differences could suppress candor. The facilitator should make room for minority views without turning the meeting into an argument over every remote possibility.

Time-box brainstorming, grouping, and action design separately. If the group debates the first risk immediately, later participants may never contribute. During prioritization, ask what evidence would change the view. An uncertain high-impact risk may justify a small test, while a familiar low-impact issue may need a simple owner rather than another meeting.

Review safeguard quality. “Communicate more” and “monitor closely” are intentions, not controls unless audience, trigger, owner, and response are defined. Add actions to the real project plan and budget. If there is no capacity to implement a safeguard, the decision-maker should see that exposure explicitly before approving the work.

A pre-mortem does not make a decision safe by imagining every bad outcome. It improves judgment by giving doubt a structured, constructive role. When the exercise produces specific changes and monitored signals, the team gains a plan that has been challenged before reality performs the test. That challenge is most useful when leaders remain willing to change the decision, scope, timing, or safeguards. Record that willingness clearly in the final decision notes.