Framework · Influence & change · 3 min read
Pre-meeting
Talk 1:1 with key people before an important meeting, use their input to improve your proposal, and walk in with no surprises and with allies.
- 1Pick people
Choose who can back or block it. Include the likely sceptic.
Usually two to four people - 2Talk 1:1
Share the draft and ask for input before the meeting.
"What's missing? What would worry you?" - 3Adjust
Change the proposal where they had a point. Tell them.
"I added your idea on ownership." - 4Walk in
No surprises, and allies ready to speak for it.
"We've talked about this; I support it."
After the meeting: send the decision and next steps in writing.
Use it when
- You are bringing an important proposal to a steering group, a leadership meeting or a design-system council.
- You expect one or two people to push back, and you want to hear their concerns before everyone else does.
- You find it hard to speak up in big meetings. The pre-meeting is a very introvert-friendly influence technique.
How to use it
- Pick the key people. Look at who will be in the room and who can block or back the decision. Use your Power-interest grid: start with high-power people and the likely sceptics. Output: a short list, usually two to four people.
- Talk to each one 1:1. Keep it short and informal, a call or a coffee. Share the draft and ask: "What's missing? What would worry you? What would make this work for your team?" Output: their concerns and ideas, in their words.
- Adjust the proposal. Use what you heard. Change the plan where they had a point, add answers to their worries, and tell them what you changed. Output: a better proposal that the key people have shaped.
- Walk in with no surprises. Everyone important has seen it. Let them know when it is on the agenda, and ask a supporter if they are willing to speak for it. Output: allies in the room and no surprise objections.
- Follow up in writing. After the meeting, send the summary, the decision and the next steps. Thank the people who helped shape it. Output: a written record and stronger relationships for next time.
Worked example
A UX lead on an internal operations platform plans to propose a shared research panel (a pool of users all teams can recruit from) at the monthly product leadership meeting.
| Who | What they said in the pre-meeting | What changed in the proposal |
|---|---|---|
| Head of product | "Good idea, but who owns it? Nobody has spare time." | Named one researcher as owner, two hours a week. |
| Domain lead, customs (sceptic) | "My users are officers on shifts. They won't join a panel." | Added short remote sessions that fit shift breaks. |
| Data protection contact | "Where is the user data stored?" | Added a storage plan reviewed with data protection. |
In the meeting, the head of product said "We've talked about this; I support it." The customs domain lead asked one question, which the proposal already answered. It was approved in ten minutes.
Watch out for
- Selling instead of asking. If you only present, you get polite nods and no real input. Ask what's missing and listen.
- Ignoring what you heard. If people give input and nothing changes, they feel used. Show them what you changed.
- Leaving out the sceptic. It is tempting to pre-meet only with friends. The sceptic is the one you most need to hear from.
- Pre-meeting as a secret deal. Don't promise different things to different people. Everyone should recognise the same proposal in the room.
Template
Copy this into your notes before an important meeting.
Meeting: Date:
Proposal (one line):
Key people Why they matter Their concern What I changed
1.
2.
3.
Questions to ask in each 1:1:
- What's missing?
- What would worry you about this?
- What would make it work for your team?
Who will speak for it in the room:
Follow-up sent on:
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.