← All articles
Ethical Influence & Persuasion

How to Influence Stakeholders on a High-Stakes Decision

Why brilliant proposals die in boardrooms — and the sequenced approach that wins stakeholder support before the meeting ever starts.

The deck was flawless. Forty-two slides, every number triple-checked, every objection anticipated, every risk mapped to a mitigation. The executive presenting it had worked on the proposal for three months, and it showed — in the polish, in the precision, in the quiet confidence with which she walked the board through slide after slide.

Twenty minutes in, she had lost the room.

Not to a better argument. Nobody offered one. She lost it to folded arms, to a chairman glancing at his phone, to the one director who asked a question that had already been answered on slide nine — not because he hadn’t been listening, but because he was signalling something else entirely. The proposal was deferred “for further consultation”. It never came back.

Watch enough of these meetings and a pattern emerges, one that has almost nothing to do with the quality of the idea. The decision was not made in that room. It was made in the days and weeks before it — in corridor conversations, in private doubts never voiced, in the quiet arithmetic each stakeholder ran about what this proposal meant for them. The meeting was merely the ceremony at which a verdict, already reached, was announced.

Which points to the first and most important truth about stakeholder influence: if the meeting is the first time a stakeholder engages with your idea, you have already ceded the outcome to chance.

The brain that hears your proposal

Before a single fact of your business case gets weighed, three older, faster processes have already run in each stakeholder’s mind.

The first is a threat scan. Long before the prefrontal cortex evaluates your net present value, the limbic system has asked its own questions: does this change my standing, my resources, my certainty about the future, my control over my own domain? A proposal that is excellent for the organisation and quietly diminishing for a particular director is not, to that director’s brain, an excellent proposal. It is a threat wearing a spreadsheet.

The second is a defence of the status quo. In 1988, the economists William Samuelson and Richard Zeckhauser published a series of experiments and field studies showing what they named status quo bias — given a set of options, people disproportionately favour whatever is framed as the current arrangement, even when the alternatives are objectively stronger. The existing state of affairs carries an unearned advantage in every decision you will ever try to influence. Your proposal is not competing on a level field. It starts a goal down.

The third — and the one that ambushes the most capable executives — is reactance. The psychologist Jack Brehm demonstrated in 1966 that when people feel their freedom to choose is being constrained, they push back against the constraint itself, almost independently of the merits. Present a stakeholder with a finished, polished, forty-two-slide fait accompli, and the very completeness of it whispers: your input is not required here. Some part of them starts looking for reasons to say no — not because the idea is wrong, but because saying no is the only authorship left to them.

Perfect proposals provoke this constantly. The polish that took three months to achieve is precisely what tells the room the decision has already been made without them.

People support what they help to build

There is a well-known finding from behavioural economics that speaks directly to this. In 2012, Michael Norton, Daniel Mochon, and Dan Ariely published a series of experiments on what they called the IKEA effect: people who assembled a product themselves — a storage box, an origami figure — valued it significantly more highly than identical products assembled by someone else. Labour, it turns out, breeds love. We overvalue the things we have had a hand in making.

The implication for influence is almost embarrassingly practical. A stakeholder who has shaped a proposal — even modestly, even at the margins — is no longer evaluating your idea. They are defending theirs. The question they carry into the boardroom shifts from “should I let this happen?” to “how do we get this through?” — and that shift is worth more than any slide you will ever build.

The manipulative version of this is well known and rightly despised: the sham consultation, the feedback session held after the decision, the “input” that changes nothing. People detect it, usually quickly, and the trust it burns does not come back at the same price. The honest version requires something harder — going to stakeholders while the proposal is still genuinely wet, and being genuinely willing to let their hands leave marks in it.

The Sequenced Yes

Over the years I have distilled what actually works into a sequence with four moves. None of them is clever. All of them are work — which is why the executives who do them are rare, and disproportionately successful.

First, map the room. Before anything else, list every person whose support, silence, or resistance will shape the outcome. For each one, answer three questions honestly. What does this decision cost them — in status, certainty, autonomy, or resources? What would make it a win in their world, not yours? And who do they listen to? That last question matters more than any org chart: real influence runs through informal channels, and the person who sways your hardest sceptic is often not you.

Second, go one to one — and go early. High-stakes influence is retail, not wholesale. In a group, every stakeholder performs for every other stakeholder; positions harden in public because backing down has an audience. Alone, people can voice the real objection — which is frequently not the one they would ever raise in the boardroom. The finance director’s stated concern is capital allocation. His actual concern is that the last initiative like this made his team the shock absorber. You can only work with the real objection, and you will only hear it in private.

Third, co-author — genuinely. Bring the idea at eighty per cent, not a hundred. Say so plainly: this is where my thinking has got to, and there are parts of it you can see more clearly than I can. Then let them improve it. Some of what they suggest will make the proposal better — more often than proud authors expect. Some will be neutral, and you should take it anyway, because their fingerprints on the plan are the point. What you must never do is fake it. Reactance has a long memory, and a stakeholder who discovers their “input” was theatre will make you pay for it across every future decision.

Fourth, convene the ceremony. Only now does the meeting happen — and its job has changed. You are no longer trying to persuade a cold room; you are consolidating a warm one. The proposal arrives already carrying the marks of the people around the table. Objections have been heard, and visibly answered, before they were ever public. The meeting becomes what the best decision meetings always are: a moment where a group confirms, together and on the record, something they have each already privately decided.

The order of the conversations

One refinement separates practitioners from naturals, and it concerns sequence. Given eight stakeholders and limited weeks, who do you see first?

Instinct says: start with the hardest sceptic, because they are the biggest risk. Instinct is wrong. Start with your likely allies — not to collect easy yeses, but because those early conversations sharpen the proposal and arm you with something invaluable: the ability to say, honestly, “I’ve been discussing this with Thandi and Mark, and they raised two things that changed my thinking.” By the time you reach the sceptic, you arrive with a proposal already improved by people they respect, and with momentum they can sense. Social proof is not a boardroom trick; it is how humans in groups have always calibrated risk.

Then see the sceptic before the swing voters, not after. There are two reasons. First, if their objection is substantive, you want it early enough to act on — a real flaw discovered in week two is a gift; the same flaw announced in the boardroom is a defeat. Second, the respect of being consulted early, while the thing is still shapeable, is itself disarming. The stakeholder most people avoid until last knows exactly where they sit in everyone’s sequence, and it tells them precisely what their opinion is believed to be worth.

And when the map shows a genuine wall — a stakeholder who loses something real no matter how the proposal is shaped — do not choreograph around them. Name it, to their face: “This costs your division, and I’m not going to pretend otherwise. Here is why I still think it’s right, and here is what I can do about your side of it.” You will not always convert them. You will almost always neutralise the version of them that fights you in the dark, because opposition that has been honestly acknowledged tends to state its case and accept the verdict, while opposition that has been managed tends to go underground and wait.

The test that keeps it honest

Everything above can be done cynically, and you will meet people who do it that way — mapping the room like a battle plan, flattering their way to fingerprints, engineering consent. It works, for a while. Then it stops working forever, because organisations are small and memories are long.

The line between the two versions is one question, and it is the same question that governs every technique in this body of work: if this stakeholder could see exactly what you did and why, would they thank you for it? If you consulted them early because their perspective genuinely improved the decision — yes. If you sequenced the conversations so that every real concern was surfaced and dealt with rather than steamrollered — yes. If the whole choreography was designed to help a group of intelligent people reach a good decision without the distortions of public posturing and ambushed pride — then what you have done is not manipulation. It is leadership, applied at the level where decisions actually live.

The executive with the flawless deck learned this, as it happens. Eight months later she brought a different proposal to the same board — smaller deck, longer runway, six private conversations before the papers ever went out. One director had reshaped the implementation timeline. Another had insisted on a pilot, and got it. The meeting took twenty minutes, and most of it was the chairman summarising why the thing made sense.

Nobody in that room thought they had been influenced. Everybody had been — honestly, early, and one conversation at a time. That is what influence looks like when it is done properly: invisible in the moment, obvious in the outcome, and perfectly comfortable in the daylight.

David Watts

David Watts

Keynote speaker, NLP Master Practitioner, and author of Cracking The Influence Code.

Go Deeper

This is one thread of the Influence Code.

The complete system — the frameworks, the science, and the practice — is in the book, and on stage in David's keynotes.