Stakeholder influence: who can stop your work and who hears it first

Most projects are not killed by an opponent. They are killed by someone who was never told, found out late, and had the standing to object. The objection is usually reasonable. It arrives at the worst possible moment because that was the first moment it could.

A stakeholder is anyone who can stop the work, anyone whose sign-off it needs, or anyone who must live with the result. Treat them as an audience for updates and you have already lost the argument you have not had yet.

What to take away

Who actually belongs on the map

Start from the work and ask four questions of it. Who can say no and make it stick? Whose approval, budget or people does it need? Whose week gets worse if it succeeds? Who gets blamed if it fails? Those four questions are the working core of stakeholder analysis, stripped of the grids.

Write down names, not departments. "Finance" is not a stakeholder. The person in finance who has to sign, and the person whose forecast your request breaks, are two stakeholders with opposite interests.

The list usually runs longer in one direction than the other. The people who have to live with the result are rarely in the room where it is discussed.

It also runs shorter. Half the names that come to mind would like to be consulted and cannot affect anything. Be polite to that group. Do not confuse them with the first.

The four roles, and what each one needs

Everyone on the map holds one of four positions, and the position decides what you owe them.

Public agencies have to make this distinction in the open. Their guidance on choosing the level of participation separates informing, consulting and sharing a decision, because the damage comes from promising one and delivering another.

The common error is spending effort in the wrong row. Deciders get a deck. Affected people get an announcement. Gatekeepers get discovered. Reverse it. Deciders need less than you think. Gatekeepers need to be found before they find you. The affected need to be told in person, early, by someone who can answer their questions.

What each person is really weighing

Three things sit behind every yes, and none of them is the business case.

The first is what this costs them personally. Your change may save money overall and still add a step to one person's day.

That person will oppose it with arguments about risk, timing and process, none of which is the real reason. Name the real cost to their face and you get a conversation.

Pretend it is not there and you get six weeks of objections that move each time you answer one.

The second is what they have to say to their own boss. Every person you convince has to convince someone else, from memory, in a sentence. If you cannot write that sentence for them, they will not manage it either. Building a case is mostly making it repeatable by someone who cares less than you do.

The third is timing. Some people need to be first because being first is part of the role. Some need to be told before a particular meeting, because learning it in the room makes them look uninformed in front of their team. Find out who must be told before whom, then follow that order even when it is inconvenient.

Sequence is content

Two people hear the same plan on the same day. One is told over coffee, before it is fixed, and asked what would make it work. The other reads it in a circulated document with a comment deadline. Same plan, opposite reactions, and the second reaction is not about the plan.

The order runs from the person with the strongest veto and the least warning to everyone else. Gatekeepers come early, because their conditions shape the design. Deciders come once those conditions are known, so the decision holds. Affected people hear before any announcement, in person where possible. Interested people last, honestly.

If two people each expect to be told first, ask one of them: who should hear this before you do? People answer that accurately, and the answer teaches you more about the organization than any chart.

The person who says nothing

The stakeholder to worry about is not the one arguing. Arguing is engagement. Worry about the one who has attended twice, asked nothing, and has the standing to slow things down without ever taking a position.

Silence from a person with a veto is usually one of three things. They have not worked out what it costs them. They have worked it out and are waiting to see if it goes away. Or they have decided and are choosing where to say so.

Go to them one to one and ask a narrow question: what part of this would you change? An open invitation to comment gets nothing back. A specific question gets either the objection or the assurance that there is none, and both are worth having before the meeting rather than during it.

Keeping the map alive

The map is wrong within a month. People change roles, a reorganization moves the veto, and a gatekeeper becomes a decider.

Before each significant step, re-read the names. Ask whether anyone's position changed and whether someone new appeared. Five minutes every few weeks is the whole cost. Projects surprised late almost always drew the map once and filed it.

The mechanics of asking any of these people for something they do not have to give are set out in influence without authority. If you are the one holding the authority, how people on this map filter what reaches you is described in leadership influence.

Common questions

Is this different from stakeholder management?

Management, as usually practiced, is a communications schedule: who gets which update, how often. That is a small part of it. The work described here happens before the decision, and its output is a decision that has already absorbed the objections rather than one that meets them afterwards.

What if I cannot get to a decider directly?

Then someone who can is your real first stakeholder, and the conversation with them is about what they would need in order to carry it. Write the sentence you want them to say. If they will not say it, you have learned something you needed to know.

How many people is too many?

If the map has more than about a dozen names, most of them are interested rather than involved. Sort again. The people who can stop the work are rarely more than a handful, and that handful is where the time goes.

Someone on the map is actively hostile. What then?

Find out whether the hostility is about the work or about how they were treated in a previous round. The second is more common and easier to address, because it can be acknowledged plainly.

Hostility about the work itself means their cost is real and you have offered nothing for it. That is a trade to be had or a signal to redesign.