How do you design a meeting that hears the doubts before the disaster, not after?
We have all sat in the meeting after the project failed, the one where someone finally says "I had a bad feeling about this from the start." And the obvious, maddening question is: then why didn't you say so when it mattered? Usually the answer is that more than one person had that feeling, and none of them said it out loud, because in the meeting where the plan was being approved, raising a doubt felt like an attack on the plan, or on the person who proposed it.
The image is a room full of people nodding along to a plan half of them privately doubt. And the fix is not more courage or a better culture. It is a single, almost absurd change to the question being asked, which is what makes this one of the most useful things behavioural science has to offer anyone who runs meetings.
What the premortem actually is
The cognitive psychologist Gary Klein popularised a technique he calls the premortem. In a normal review, you ask a team what could go wrong, and people answer cautiously, because naming a risk sounds like doubting the plan. Klein changed one thing: the tense. Instead of asking what might go wrong, you tell the team to imagine it is months from now and the project has already failed, completely and visibly, and then ask each person to write down why.
It draws on research by Deborah Mitchell, Jay Russo and Nancy Pennington into what they called prospective hindsight: imagining that an event has already happened, and looking back to explain it, helps people generate noticeably more reasons for the outcome than asking whether it might happen. Klein built this into a practical method, and reports that assuming a failure and explaining it surfaces around a third more reasons than a standard risk review.[1] One honest caveat from the original research: prospective hindsight produces more reasons, but they tend to be concrete and episodic, so it is "seeing more," not automatically "seeing better." Still, more named risks is real value, because a risk you can name in advance is one you can still act on. And Klein flags a crucial detail: the fastest way to wreck a premortem is to run it with the most senior people in the room, whose presence quietly collapses the honesty the whole thing depends on.
The doubts were there all along
The standard way to get more honesty in a meeting is to ask for it: tell people to speak up, to be braver, to challenge the plan. It almost never works, because it leaves the thing causing the silence untouched.
The premortem does not ask anyone to be braver. It changes the structure of the question so that honesty no longer carries a cost. Once everyone has agreed, as a premise, that the plan has failed, explaining why is no longer criticism; it is just describing what happened. The past tense gives permission that the cautious "what could go wrong?" withholds. The person who said nothing in the normal review will, in a premortem, tell you exactly where the cracks are, not because they found new courage, but because the structure made the warning safe to say. The doubts were always there. The design simply removed the cost of voicing them.
This is the difference between motivation and design in miniature. Motivation works on the person, asking them to overcome the room. Design changes the room so there is nothing to overcome.
Turn your instinct for progress into a method
The Behavioural Design Method gives you tools to find the friction in any situation and redesign the path. For your organisation, your team, or your own work.
The science: prospective hindsight and decision design
The principle underneath the premortem is prospective hindsight, but the deeper lesson is about where unspoken doubts actually come from. We tend to explain them as a failure of character, people are too timid, the culture is too cautious, and so we reach for fixes aimed at the person. The premortem locates the problem somewhere else entirely: in the structure of the situation. In a normal risk review, naming a problem is socially expensive, because it reads as doubting the plan or the colleague who championed it, so even people who clearly see the risk stay quiet. The silence is produced by the design of the meeting, not by a shortage of integrity in the people.
Shift the tense and you change the economics of speaking. By stipulating failure and asking for the explanation, the premortem makes naming a risk costless, even expected, and the same people who would have stayed silent now compete to name what went wrong. The unspoken risks were never about brave or timid people. They were about a meeting structured so that honesty carried a price, and the elegant move was not to demand more honesty but to redesign the situation so honesty was free.
Through a Behavioural Design lens
It is worth slowing down on the premortem, because it shows how getting a behaviour you want often means designing the whole sequence that leads to it, not just asking for it.
Start with the person. What does someone in that approval meeting actually want? To do good work, to be seen as a constructive team member, not to be the one who torpedoed a plan everyone else seemed happy with. Notice that staying silent is not a failure of wanting to help; it is a rational response to a real cost. The forces here are social: what might push someone to speak is their genuine insight, but what holds them back is the price of looking negative, of doubting a colleague, of breaking the room's apparent consensus. Reading the silence by the forces acting on people rather than their courage is what we call the Influence Framework at SUE, and it points away from the person and straight at the structure of the meeting.
Now the fix, and honesty in a meeting is not one moment but a small sequence, each step of which can fail. First you have to get people genuinely engaged, not just present but actually willing to look for problems, which the dramatic "the project has failed" premise does by making it a puzzle rather than a confession. Then you have to convert that engagement into the actual behaviour, the risks named out loud, which the past-tense framing makes safe enough to do. Then people's contributions have to be received and taken seriously, confirmed rather than waved away, or they will not do it again. And finally it has to become a habit, a normal part of how the team plans, so the honesty keeps coming. Klein's design quietly handles the whole sequence: the premise catches people's engagement, the tense converts it into spoken risks, having everyone write before they share confirms that every voice counts, and keeping the senior person quiet protects it so it can continue. That sequence, catching engagement, converting it to action, confirming the choice, and continuing it until it is normal, is what we call the 4C Influence Flow at SUE, and the premortem works because it clears every step, not just the first.
The lesson travels to any honesty or candour you are trying to get from people. You do not ask people to be braver, you change the question and the room so the honesty costs nothing, across the whole sequence, not just at the moment you happen to ask for it.
What this means in practice
The premortem is a meeting technique, but the underlying move is one of the most useful you have, starting with your own decisions. When you are about to commit to something, your own mind protects the plan you have grown attached to, quietly filtering out the doubts. Run a private premortem: imagine it is a year on and the decision has clearly failed, and write down why. You will surface risks your optimism had hidden from you, while you can still do something about them.
For anyone leading people, this reframes how you get honesty. The instinct, when a team will not voice its doubts, is to push for more candour, to talk about psychological safety, to ask people to be braver. Far more effective is to change the situation so candour is free. Shift the tense: do not ask what could go wrong, tell the group the thing has already failed and ask why. Have people write before they speak, so the first confident voice does not set the ceiling. And get yourself, the most senior person, to go last or leave the room, because your presence is the single biggest thing collapsing the honesty you say you want.
And for the organisation, this is the difference between a culture programme that exhorts people to challenge and a decision process that is structurally honest. The first leans on individual courage and fades; the second changes the situation and works regardless of who is in the room. The question is not how do we get people to speak up more, but what about the way we run decisions is making honesty expensive, and how do we redesign that.
What you can design this week
The move works on your own decisions, a team you lead, or any meeting where you need the truth. Three ways to start:
Change the tense, not the people. Before committing to a plan, do not ask what could go wrong. Tell the group to assume it is a year on and the thing has clearly failed, then have everyone write down why, alone, before anyone speaks. The past tense gives permission the conditional withholds.
Let people write before they talk. Independent, written answers first, shared round-robin after. This stops the first confident voice from setting the ceiling, and it means the quietest person's risk lands with the same weight as the loudest.
Get the most senior person to leave, or go last. If the boss speaks first, the premortem dies. Either run it without them, or have them stay silent until everyone else has emptied their list. The aim is a room where the warning costs nothing to say.
The doubts were always in the room. The standard meeting was built, often by accident, to keep them unspoken. Change the question and the room so the warning costs nothing, and you hear the risks early, while you can still act on them, instead of hearing "I knew it" when it is already too late.
If you want to learn how to design decisions and meetings that surface people's real doubts in time, that is exactly the kind of work our Behavioural Design training is built around.
Start designing for behaviour, not hoping for it
The SUE Behavioural Design Method teaches you to find the friction, redesign the path, and make the right behaviour the easiest option. In two days live or at your own pace online.
Frequently asked questions
What is a premortem and how does it work?
A premortem is a meeting technique popularised by cognitive psychologist Gary Klein. Instead of asking 'what could go wrong?', you tell the group to imagine the project has already failed and ask each person to write down why. The past tense removes the social cost of naming a risk, making honesty safe without requiring anyone to be braver than usual. Klein reports it surfaces around a third more risks than a standard review.
Why do people stay silent in risk reviews?
In a standard risk review, naming a problem reads as doubting the plan or the colleague who championed it. Even people who clearly see the risk stay quiet because honesty carries a social cost. The silence is produced by the design of the meeting, not by a shortage of integrity. The premortem removes that cost by stipulating failure as a premise — explaining why is no longer criticism, it is just describing what happened.
What is prospective hindsight?
Prospective hindsight is the cognitive technique of imagining that an event has already happened and looking back to explain it. Research by Deborah Mitchell, Jay Russo and Nancy Pennington found this produces noticeably more reasons for an outcome than asking whether it might happen. Gary Klein built this into the premortem: by stipulating failure rather than hypothesising it, people generate more concrete, episodic risks.
1.5 minutes on influence
10,000+ readers · Free · Unsubscribe anytime