How to get buy-in: the influence playbook

You have spent two weeks on a proposal. The slides are tight. The data is solid. You walk into the room, present your case, and the most senior person in the group asks a question you did not prepare for. Someone else raises a concern that seems to come from nowhere. The energy shifts. The meeting ends with “let’s revisit next quarter.”

Nothing wrong with the idea. Everything wrong with how it arrived.

Buy-in is not a presentation problem. It is a sequencing problem. The meeting is a ratification event, not a discovery event — and if you are still trying to convince people during the meeting, you have already lost.

This post is about the work that happens before the meeting.

Why meetings fail even when the idea is right

A meeting surfaces three things simultaneously: the proposal, people’s reactions to the proposal, and the social dynamics of the room. When those three elements collide in public for the first time, they interact unpredictably.

The senior engineer who has not heard this before will ask a basic clarifying question — which signals to the room that the idea is still half-baked. The VP whose budget is implicated will go quiet — which everyone reads as skepticism. The person who actually loves the idea will stay silent because they have not had a chance to process it yet and do not want to over-commit in public.

None of this is bad faith. It is just how rooms work. People need time to think, time to position, and time to understand how they are supposed to feel about a new thing. A meeting does not give them that time. A one-on-one conversation the week before does.

This is what pre-wiring means: you do not change the meeting. You change what people bring into it.

The influence map

The influence map is a tool for sequencing the pre-work. Before the meeting, you identify every person whose voice matters — either because they have formal authority over the decision, or because they have informal authority over the room’s energy. Then you work through them one by one, in a specific order, building support before anyone is in the same room.

The diagram above is the whole playbook in condensed form. The rest of this post is about executing each step without coming across as manipulative — because there is a real line here, and it matters.

Step 1: go to the loudest skeptic first

Every group has someone who is reliably difficult about new ideas. Not out of malice — usually because they have been burned before, or because they feel their domain is being encroached on, or because they have a legitimate concern that they have not figured out how to articulate yet.

That person is your first call.

The instinct is to go to your allies first, build momentum, and deal with the skeptic from a position of strength. This is backwards. In a meeting, the skeptic with a loud objection can reset the energy of the room in 90 seconds. If you have not already heard and addressed that objection, you are defending in public — which looks weak even if you are right.

Go to the skeptic privately, before anything else. Come in curious, not defensive.

“I wanted to talk through the proposal before the meeting because I suspect you’ll have thoughts, and I’d rather hear them now than be surprised.”

That framing does two things. It signals respect — you are treating them as someone whose opinion matters enough to seek out. And it removes the adversarial dynamic, because you are not presenting to them, you are consulting them.

Most of the time the concern is legitimate and addressable. Incorporate it. When the meeting happens, the skeptic has already shaped the proposal — they are no longer an opponent, they are a contributor. And if they raise the concern anyway, you can say honestly that you heard this feedback and here is how you addressed it. That is a very different dynamic from getting ambushed.

Occasionally the concern is not addressable, or the person is implacably opposed for reasons that have nothing to do with the proposal. At least you know that now. You can think about whether the decision-maker’s support is enough to proceed, rather than finding out in the meeting.

Step 2: activate your quiet supporters

There are almost certainly people who like your idea. They will not say so in the meeting unless you ask them to ahead of time.

This is not a personality flaw. It is rational behavior. Volunteering a strong opinion in a group setting has social costs — it can look like grandstanding, it can put you at odds with someone senior, and it burns capital that people prefer to save. So they stay quiet, nod vaguely, and offer you their support afterward over coffee, when it is useless.

The fix is explicit activation. Find two or three people who you know are broadly aligned and have the conversation:

“I wanted to get your read on this before we meet. I think you might have context that’s useful here — and honestly, if you agree it’s the right direction, it would help to have you say so when the question comes up.”

Most people will say yes. They just needed permission and a specific ask. Now they have a role in the meeting — not cheerleader, but someone with a considered view who is willing to voice it. That is all you need.

Step 3: frame for the decision-maker’s actual priorities

Here is where most smart people get this wrong.

You frame the proposal in terms of what matters to you — technical quality, user experience, engineering efficiency, whatever your discipline prizes. You assume the decision-maker shares those values because they should. They do not.

A VP of Sales looking at a new internal tooling proposal is thinking about one thing: does this slow down my team during quarter-end, or speed them up? A CFO evaluating a platform change is thinking about two things: what does this cost, and what is the downside risk if it fails? A CEO hearing about an organizational restructure is thinking about what story they have to tell the board.

Your job is to figure out what those priorities are — from conversations, from their recent public communications, from what you have seen them push back on — and then translate your proposal into that language.

This is not spin. The translation has to be accurate. If your proposal genuinely does not serve their priority, you have a different problem: you are pitching the wrong thing. But if it does serve their priority and you are presenting it in your language instead of theirs, you are losing for no reason.

The question to ask yourself before the decision-maker conversation: “What is the one thing this person is most worried about right now, and how does my proposal make that better or worse?”

If you cannot answer that question, you are not ready for the conversation yet.

Step 4: give them a way to shape it

This is the most underused move in the sequence.

People support things they had a hand in building. This is not a manipulation technique — it is a basic fact about how ownership works psychologically. When someone contributes an idea or a modification, they have skin in the outcome. They are invested in it succeeding.

In every pre-wiring conversation, leave something genuinely open. Not a cosmetic choice (“what should we call it?”) but a real decision (“I am torn between these two implementation approaches — which one fits better with how your team works?”).

When someone makes that call and you incorporate it, two things happen. First, the proposal improves — they have expertise you do not. Second, they walk into the meeting with partial ownership over what is being proposed. They are not evaluating your idea; they are presenting their contribution to a shared initiative.

The version of this that fails is when there is nothing genuinely open and you are just performing consultation. People can sense the difference between being asked and being processed. The former builds support; the latter builds resentment.

What pre-wiring is not

Pre-wiring is not lobbying. Lobbying is asking people to support something regardless of whether it is the right thing. Pre-wiring is making sure that when the decision is made, it is made with full information rather than surprise and defensive positioning.

It is not going around someone. You are talking to stakeholders, not behind decision-makers’ backs. If anything, you are talking to the decision-maker earlier — before the formal setting where their public position gets locked in.

And it is not manipulating the outcome. If your idea genuinely does not hold up — if the skeptic has a point that you cannot address, if the decision-maker’s priority makes the proposal irrelevant — pre-wiring surfaces that early. That is valuable. You would rather hear a no in a one-on-one conversation in week one than in a group meeting in week three.

The process does not rescue bad ideas. It gives good ideas a fair hearing.

The mistake that kills good ideas

Most people bring proposals to meetings cold. They believe the quality of the idea should be sufficient. It often is not, and not because the audience is irrational.

When someone hears a new idea for the first time in a group setting, they are simultaneously processing the content, reading the room’s reaction, deciding how to position themselves relative to both, and managing whatever else is on their mind that day. That is a lot of competing attention. The idea rarely wins that competition on first exposure.

By the time the meeting happens, every person in the room should have already formed a considered view — not a reflexive reaction, but an actual view. You want the meeting to be the moment when people state what they already believe, not the moment when they decide what they believe.

That shift — from a room discovering something together to a room confirming what they have individually concluded — is the whole game.

Do the pre-work. Go to the skeptic first. Activate the supporters. Frame for the decision-maker. Leave something real open.

The meeting ratifies. The work happens before it.