Decision rights: RACI and who really holds the veto

A contested call needs one person who can close it — and everyone else given a named, honest kind of voice.

The idea

When a decision is contested, the failure mode is rarely a lack of opinions — it’s that no one knows who gets to decide. RACI names four kinds of stake in a decision: Responsible (does the work), Accountable (the single owner who makes the call), Consulted (gives input first), and Informed (told after).

The one rule that does most of the work: exactly one A. Two accountable owners is a standing deadlock. Zero is a decision that bounces forever. Give the rest a real but bounded voice — and demote most “must be consulted” claims to simply informed.

How it works

For one decision, walk every stakeholder into exactly one column. Start from the outcome, not the org chart: who signs off? is the A. Whose hands build it? are the R’s. Then be ruthless about the last two columns — a “consult” is a two-way conversation you owe them before deciding; an “inform” is a one-way note after. Most people who demand a seat only need to be informed.

DECISION: ship the redesigned pricing page

  stakeholder     role   meaning
  Product lead     A     one owner — makes the call, signs off
  Eng lead         R     responsible: builds it
  Design lead      R     responsible: designs it
  Legal            C     consulted once, before the call
  Data             I     informed after — sees the result

  rule: exactly one A  ·  at least one R  ·  keep C small  ·  the rest are I

Notice the A does not have to do the work, and the R’s do not get the final say. Separating “decides” from “does” is the whole point — it’s what lets a decision have one owner and many hands.

When to use it

Reach for RACI when…	The trade-off
A cross-functional decision has many strong opinions and no obvious owner.	Someone must accept being only C or I — that conversation is the hard part, not the grid.
Work keeps stalling because “we’re still aligning” with no one empowered to close it.	Overkill for small, reversible calls — don’t RACI a one-line copy change.
You need to make an implicit veto explicit before it ambushes you late.	The grid is a starting agreement, not a law — revisit it if the decision changes shape.

Watch out for

• Two A’s to keep the peace. Naming co-owners feels fair and reads as collaborative — then the first real disagreement has no tiebreaker. Pick one; give the other a loud C.
• Confusing A with R. The accountable owner is often not the person doing the work. A senior leader can be A while an engineer is R. Don’t default the A to whoever is busiest.
• Consulting everyone. When half the room is C, every choice becomes a meeting with all of them. Ask “does their input change the decision?” If not, they’re I.
• Silent I’s who wanted a veto. If you drop someone to Informed, say so out loud — a surprised stakeholder relitigates the whole thing later.
• Zero R’s. A crisp decision that no one is assigned to actually do is just a nicely-owned wish.

Worked example

An interviewer says: “Marketing, Legal, and Eng each think they can block the launch. It’s been slipping for weeks. What do you do?” A strong answer doesn’t promise to “get everyone aligned.” It names one A — say the product lead who owns the launch outcome — and states it plainly. Eng and design are R. Legal is C: their compliance read genuinely shapes the call, so they’re consulted before the decision, not after. Marketing, who wanted a veto over timing, is honestly told they’re C on messaging, I on the ship date. The unlock isn’t consensus; it’s that one person can now say “we ship” and the others know, in advance, exactly how their voice counted.