Why I am writing about this
The first time I realized how powerful pre-meetings are was not for a product discussion, it was a career discussion.
I was proposed a role change that I didn't want. Instead, I had my eyes on the integration PM role, which was outside of my organization at the time.
There was a heated discussion of where I should go, and an alignment meeting planned. I was planning to go in and align.
Luckily, my mentor advised me to have a short meeting with the leader that I knew would make the last call. She said it's okay, just talk to him, discuss what's best for both you and the company.
And oh my god I am so happy I did.
Once I jumped on this pre-alignment meeting, I realized that if we hadn't spoken 1:1, I would have been pushed into a role I didn't want.
Just for the mere fact that other people on the call were all more inclined to have me there, rather than where I wanted to go.
I am happy I received that lesson from my mentor before things got out of hand. From then on I always look at who I need to talk to before the meeting.
Let's break down together how we can turn this knowledge into something that enables you to influence decisions.
Why do you need a pre-meeting
Before you get discouraged by the politics of running meetings before meetings, let's look at why meetings themselves are just not enough.
1. Groups hide what only one person knows
Researchers call these hidden profiles.
The pattern, across 65 studies and more than 3,000 groups: people discuss what everyone already knows.
The one fact that only one person holds usually never gets said.
And it gets worse with more people in the room, not better.
So your ten person review is not where the missing piece comes out.
It is where it stays hidden.
How the pre-meeting helps: one to one, there is nowhere to hide. The fact that would never survive a ten person agenda comes out in the first five minutes.
2. Silence is about relationships, not risk
Researchers asked 40 employees why they had not raised concerns upward.
The top reason was not fear of punishment.
It was fear of being labelled negative, and damaging a relationship they cared about.
Your architect is not quiet because the risk is small.
He is quiet because saying it in front of eleven people costs him something.
How the pre-meeting helps: in private, telling you the truth costs him nothing. No audience, no label.
3. Opinions harden before you present
This one changed how I think about timing.
Once one option starts to look like the winner, people bend everything that comes after to support it. Without noticing.
Researchers call it predecisional distortion. It is about twice as strong as the better known effect where we justify decisions after making them.
By the time your slide goes up, the room has already tilted.
You are not presenting to neutral people.
How the pre-meeting helps: you get there while the opinion is still forming, instead of after it has set.
4. Said out loud, it becomes a position
Once someone states an objection publicly, they defend it.
Research on escalation of commitment found that people who owned a decision kept backing it as it failed, far more than people who inherited the same one.
The driver is wanting to look consistent in front of others.
An objection in private is a question.
The same objection in a room is a stance.
Get to it while it is still a question.
How the pre-meeting helps: you hear it before it hardens into something they now have to win.
5. Being asked changes acceptance
People will back a decision they disagree with, if they believe the process was fair.
Three things make it feel fair:
→ You asked them
→ They know why you decided what you decided
→ They know what happens next
You do not have to give everyone what they want.
You have to give them a real chance to be heard, and then tell them what you did with it.
How the pre-meeting helps: the asking is the point. Even when you change nothing, they walk in having been heard.
Feeling weird about pre-meetings? How do you even have one?
There is no science on what a pre-meeting is supposed to look like.
Depending on the context and what feels natural to you, you can experiment with these formats:
→ A fifteen minute Teams call the day before the steering committee
→ "Quick sanity check before I send this round"
→ Standing at the coffee machine with the architect who always has one objection
→ Forwarding the slide to one person and asking what they would push back on
No deck. No agenda. One question.
What makes a pre-meeting work
The format is up to you. These five things are not.
1. Who
Keep the audience as small as possible. Preferably one person at a time.
Two people are worth your time:
→ The one who decides: the veto, or the approval
→ The one who will say something out loud in the room if you go quiet
That second one matters more than it sounds. In Asch's conformity studies, a single person breaking with the majority sharply reduced how much everyone else conformed.
One visible ally beats five silent ones.
2. When
Before the deck is finished.
If your slides are final, you are not asking, you are informing. People can tell the difference immediately.
3. How to frame it
Research on how managers sell issues upward found something useful: linking your issue to a goal that is already agreed works better than linking it to whatever else is currently on the agenda.
Not: "this competes with the migration."
Instead: "this is how we hit the availability target we already committed to."
4. What to ask
One question, and then stop talking:
"What would make you say no to this?"
Not "does this look okay." That gets you a yes that evaporates in the room.
5. Close the loop
Go back before the meeting and tell them what you changed because of what they said, or why you did not change it.
Skipping this is what turns a pre-meeting into a stitch-up.
A hypothetical example absolutely not based on my real experience
Your platform architect takes your proposal apart in front of everyone :(
How not to do it:
- You build the deck, polish it, and book the steering committee.
- You present. Your architect starts with a question, then another, then finds ten reasons this will not work and disassembles the whole thing in front of the room.
- No decision. You are told to go work it out together. The slot is gone and you are back in three weeks.
So you had the pre-meeting anyway.
You just had it after his objections turned into a public position he now has to defend.
Do this instead:
- Tuesday. Fifteen minutes with the architect, no deck. Two questions: what gaps or issues do you see in this, and then which of these are showstoppers?
- You get the same ten reasons, in private, where saying them costs him nothing. He calls two of them showstoppers. You fix one and flag the other.
- Thursday, the room discusses two open questions instead of ten objections. And he is the one saying "we looked at this together."
Is pre-alignment the best thing ever? NO.
A pre-meeting should make a decision better. It should not be the only way a decision can happen.
A study of eight companies found that heavy political behaviour among senior teams came from power sitting in too few hands, and it went together with worse company performance.
So if you cannot move anything without a pre-meeting first, that is not a skill you need to master.
That is a symptom. Worth observing the leadership dynamics, and where it is all coming from.
Additional resources
If you want the research itself, these three are free and readable:
→ Allen, Lehmann-Willenbrock and Landowski on pre-meeting talk
→ Kim and Mauborgne, "Fair Process: Managing the knowledge economy"
→ Milliken, Morrison and Hewlin on why people stay silent.
