Veto power without criteria is how slippage is born

Estimated reading time: 9 minutes

For transformation leaders who keep getting “blocked off-line” and want a clean way to surface veto criteria without triggering politics.

Silent vetoes happen when people feel responsible for risk but unsafe to own the “no” in public. So they block informally, after the meeting, without criteria. That is how slippage is born: work moves forward until it hits an invisible tripwire, then everyone rewinds. The fix is not more meetings. It is to separate veto rights from veto criteria. Keep the right to stop, but make the stop legible: define five veto categories, attach thresholds, require a short objection template, and set a decision SLA for what happens next. You remove politics by debating rules before decisions, and by forcing objections to be about evidence and thresholds, not personalities.

The moment you realize governance is not in the room

Last quarter I watched a steering committee “approve” a decision in under 20 minutes. It felt clean. Everyone nodded. The program team left relieved.

Two days later, the work stopped anyway.

Not because new facts emerged. Because someone with informal influence texted, “I’m not comfortable with this.” No criteria. No threshold. No alternative. Just a quiet stop that nobody wanted to challenge.

A silent veto is an unofficial block applied outside the forum, without explicit criteria or accountability. It often sounds polite. It is still a veto.

It creates the most expensive kind of slippage: the kind you only discover after you have spent money.

Why silent vetoes exist (and why they feel rational)

Most leaders try to fix this by tightening the process: more pre-reads, more “alignment,” more stakeholders in the meeting.

That usually makes it worse.

Silent vetoes exist because the organization has created a gap between felt responsibility and safe accountability.

Three drivers show up again and again:

1) Interpersonal risk beats operational speed

If saying “no” publicly creates backlash, politics, or reputational damage, people will route the veto through private channels. Research on psychological safety describes how interpersonal risk shapes whether people speak up or stay quiet.

2) “Risk owners” are asked to approve without a rulebook

Security, legal, brand, finance. These functions often carry real downside. When they are asked to “sign off” without thresholds, they protect themselves the only way they can: they slow it down, or stop it informally.

3) Informal networks are doing the work the formal model cannot

When formal governance is too blunt, people use informal influence to get precision. Social network research and practice show that informal networks shape how work actually gets done, often more than the org chart.

So the goal is not to eliminate informal influence. That is fantasy.

The goal is to prevent informal influence from being the only place where veto criteria exist.

Spot the patterns: 5 tells you’re in shadow governance

Use these as a quick diagnostic:

1. “Let’s take this offline” is the default, not the exception.
2. Objections are emotional but non-specific: “I’m not comfortable.”
3. Decisions are re-litigated after the forum.
4. “Surprise approvers” appear late, after months of work.
5. The same decision gets different answers depending on who asked.

If you see two or more repeatedly, you do not have a decision problem.

You have a criteria visibility problem.

The fix: separate veto rights from veto criteria

Here’s the disruptive claim: your organization may need veto power. But it does not need veto ambiguity.

A veto without criteria is not governance. It is latency.

Design rule: keep the right to stop, remove the right to be unclear.

That means two things:

1) Publish a Veto Criteria Catalog

Five categories is enough for most transformation programs:

• Security and privacy
• Legal and regulatory
• Brand and customer trust
• Financial exposure
• Operational resilience and safety

Each category needs thresholds that answer: “What triggers a stop?”

Not “what makes you nervous.” What crosses the line.

2) Require a short Silent Veto Objection Template

No template, no veto.

This is not bureaucracy. It is respect for everyone’s time.

It forces the objection to become legible, comparable, and actionable.

It also protects the objector. The debate becomes “does this meet the threshold?” not “why are you blocking us?”

How to surface criteria without triggering politics

This is where most leaders get it wrong.
They confront the person.

Do not do that.

Use mechanisms that make the room argue about rules, not individuals.

Mechanism 1: Pre-wire criteria, not outcomes

Before the meeting, ask veto-holders one question:

“What evidence or threshold would make this a clear yes, and what would make it a clear stop?”

You are not negotiating the decision. You are collecting criteria.

Mechanism 2: Use reversible vs irreversible decisions

If every decision feels irreversible, vetoes multiply.

A useful mental model is to classify decisions as reversible (“two-way door”) vs hard-to-reverse (“one-way door”). Amazon’s shareholder letters describe this logic explicitly.

For two-way door decisions, default to speed with monitoring. For one-way door decisions, require stronger evidence.

Mechanism 3: Install a decision SLA for vetoes

A veto is not an outcome. It is an event that must route somewhere.

Example SLA rules:

• If blocked, the objector must submit the template within 48 hours.
• The decision owner must respond with options within 5 business days.
• If unresolved, it escalates to a named decider within 10 business days.

The point is simple: a veto cannot be indefinite.

Mechanism 4: Force the veto into a mitigation choice

Most vetoes are not binary. They are conditional.

So make the objector choose which lane they are in:

• Stop: threshold exceeded, cannot proceed.
• Mitigate: proceed if controls are added.
• Monitor: proceed with logging and a rollback plan.

This turns “no” into engineering.

Mechanism 5: Review veto quality, not just outcomes

If every veto is treated as “politics,” people will hide them.

Instead, review vetoes for reasoning quality: clarity of threshold, evidence, and proportionality. The literature on organizational silence highlights how shared beliefs about the danger or futility of speaking up can form and persist.

You are building a system where speaking up is safe and useful, not heroic.

When this advice does NOT apply

Use common sense. There are cases where you should not try to “surface criteria” in public:

• Active incident response, breach, or safety event.
• Litigation hold or legal privilege constraints.
• M&A or material non-public information constraints.
• A real compliance requirement where the approver is missing by policy (fix the routing first).

Actions to do this week

1. Name your five veto categories and publish the blank catalog.
2. Add one rule to your steering committee charter: “No template, no veto.”
3. Set a simple veto SLA (48 hours to submit, 10 days to resolve or escalate).
4. Run a 30-minute pre-wire with Security, Legal, and Brand: “what are your stop thresholds?”
5. In the next meeting, replace “are we aligned?” with “which threshold applies?”

Your commerce transformation timeline slips because it is treated like a plan. It is a risk register with dates.

Facts that matter

• Psychological safety was empirically defined and measured in team settings by Amy Edmondson in Administrative Science Quarterly (1999).
• Morrison and Milliken’s Organizational Silence (Academy of Management Review, 2000) describes how silence can become a systemic barrier to change.
• Work on employee voice and silence synthesizes how and why people speak up or stay quiet, including dynamics that reinforce silence. (Morrison, 2003).
• Research and practice on informal networks argues that informal connections shape how work gets done beyond formal structure. (Cross and Parker, The Hidden Power of Social Networks).
• The one-way vs two-way door decision model is described in Amazon shareholder communications, emphasizing lighter process for reversible decisions.

FAQ

How do I know if it’s a “silent veto” or a legitimate risk stop?

A legitimate stop references a rule, threshold, or evidence and routes to a defined decider. A silent veto stays vague and personal (“not comfortable”), appears off-line, and has no SLA to resolve. Your goal is not to shame the objector. It is to require the objection template so you can separate real risk from unpriced politics.

Won’t publishing veto criteria create loopholes or invite gaming?

Some gaming is possible, but ambiguity is worse. Criteria make tradeoffs explicit and allow you to design mitigations early. Keep thresholds high-level enough to avoid teaching people how to bypass controls, and focus on “what evidence is required” rather than “how to evade.” If needed, publish the categories and evidence requirements, and keep sensitive thresholds in controlled documents.

What if the veto-holder refuses to use the template?

Then you do not have a governance process problem. You have an executive sponsorship problem. The template is a commitment device: it forces accountability and comparability. Make it a steering committee rule and enforce it once. After one enforcement, compliance usually follows because the template protects everyone, including the veto-holder.

How do I implement this without making my steering committee heavier?

Do the opposite: shrink debate time by moving ambiguity out of the room. Pre-wire criteria with veto-holders, enforce the one-page objection template, and time-box unresolved vetoes with an escalation SLA. The meeting becomes a place to decide between options, not to discover hidden thresholds. Over time, teams design solutions that already fit the criteria, so fewer items escalate.

What’s the difference between a veto and an escalation?

A veto is “stop unless a condition changes,” based on a threshold. An escalation is “I need a higher-level tradeoff,” often because multiple criteria conflict (speed vs risk vs cost). Your routing should treat them differently: vetoes require the objection template; escalations require options with explicit tradeoffs and a decider.

Glossary

• Silent veto: An unofficial block applied outside the formal forum without explicit criteria or accountability.
• Veto criteria: The measurable thresholds or explicit rules that justify stopping a decision.
• Decision SLA: A time-bound commitment for when a decision, escalation, or response must occur.
• Shadow governance: The informal decision system that overrides the formal one when rules are unclear.
• Two-way door decision: A reversible decision that should use a lighter process.

Executive Takeaways

• Keep veto power if you must, but remove veto ambiguity.
• Publish five veto categories and force thresholds into the open.
• No template, no veto: make objections legible and evidence-based.
• Add a veto SLA so blocks cannot last forever.
• Debate rules before decisions, and you will trigger less politics.