How to involve stakeholders in decisions without giving them a veto

Executive overview

Leaders often consult stakeholders informally, but fail to clarify what authority they're actually granting. That gap creates resentment: the person consulted assumes their input is a veto; the leader assumes it was just a courtesy.

The fix is to make the decision-making process explicit before discussing the decision itself — clarifying who decides, who is accountable for implementation, and exactly what role each stakeholder plays.

Absent that clarification, the individual is likely to assume their perspective is a veto.

Who to involve and how to choose

• Prioritise people directly impacted by the decision.
• Also include those who must influence or enrol others once a decision is made — they need to be on board to move things forward.
• Casting too wide a net creates the expectation that everyone is involved in everything.

The four levels of stakeholder authority

Explicitly tell each stakeholder which role they hold before the conversation begins:

1. View — you want to understand their perspective; it may not affect your decision at all.
2. Voice — their input will actively inform how you decide, though you retain final authority.
3. Vote — their input is counted alongside others; they have real influence over the outcome.
4. Veto — if they say no, you won't proceed.

• When seeking only a view, frame it as a theoretical exploration: "I'm making this call — can you tell me how you'd see this problem?" This signals it's cognitive input, not co-decision.
• The awkwardness of stating this explicitly is much smaller than the damage caused by leaving it implicit.

How to elicit richer input

• Don't stop at "what do you think?" — always follow with why.
• The source of someone's view matters: lived experience, a parallel situation, a spreadsheet, or a hunch are different kinds of data and should be weighted accordingly.
• Use the Five Whys: keep asking why to surface assumptions and experiences the stakeholder might otherwise hold back.
• Ask stakeholders to argue the contrary: "Tell me every reason we shouldn't do this." People often withhold counter-arguments to stay persuasive; forcing the exercise surfaces data they're already holding.
• More data doesn't guarantee a better decision — there is often more than one right answer, and certainty is rarely available.

Standardising decision-making as a team practice

• Restructure meeting agendas around decisions rather than status updates: each item is a question to answer, with the decision-maker named next to it.
• After each agenda item, confirm how the decision will be actioned and who is accountable.
• Shared accountability is what makes this stick: when any team member can say "wait — how are we making this call?", the discipline doesn't depend on the leader alone.
• Once it becomes muscle memory, teams stop needing the formal scaffolding — the expectation is baked into the culture.

Closing the loop with stakeholders

• At the end of the conversation, thank the stakeholder and restate how the decision will be made and what their role was.
• Reasserting the process counters years of ingrained assumptions about what being consulted means.
• This protects both parties: the stakeholder isn't blindsided; the leader retains authority without destroying engagement.

On values, morals, and decision-making

• Values are aspirational — who we want to be. Morals are non-negotiable — what we will not stand for.
• Making morals explicit in the workplace is appropriate and important, not dangerous.
• Understanding the source of your own sense of right and wrong, and engaging with it intentionally, improves the quality of difficult decisions.