The veto architecture of any institution is more important than its approval architecture.
Asymmetric Power
Approval power and veto power are not symmetric. Approval power produces outcomes — when a proposal is approved, something happens. Veto power prevents outcomes — when a proposal is vetoed, nothing happens. This asymmetry makes veto power strategically more important than approval power in most institutional contexts, because preventing a bad outcome is usually easier and less costly than producing a good one, and because veto power is more durable than approval authority.
The approval architecture of an institution — who has the authority to formally approve which decisions — is documented and relatively visible. The veto architecture — who has the practical ability to block which outcomes, through formal objection, informal resistance, or passive non-cooperation — is undocumented, often invisible in advance, and more consequential for predicting what will and will not happen.
Types of Veto
Institutional veto power takes several forms. Formal veto authority is the most visible — the designated reviewer whose approval is required, the regulatory body whose sign-off must be obtained, the board whose opposition would be decisive. Formal veto authority is documented and therefore mappable before it matters.
Informal veto authority is harder to see in advance. It belongs to actors whose sustained opposition to a proposal would cause it to fail — not through formal objection but through the cumulative effect of skepticism, non-cooperation, or the quiet withdrawal of the resources and relationships that a proposal requires to advance. Informal veto power can be exercised without ever formally opposing anything, which makes it difficult to attribute and difficult to contest.
Structural veto authority resides not in any actor but in the design of the decision-making process. A process that requires unanimous agreement, that gives any affected party a formal review right, or that requires coordination across multiple institutional actors each with their own timeline and risk tolerance, has distributed veto power in a way that makes blocking easier than approving. The structure is the veto architecture, regardless of any individual actor's intentions.
Mapping the Veto Architecture
Veto architecture mapping requires asking a different question than the standard authority mapping question. The standard question is: who can approve this? The veto question is: whose sustained opposition would be sufficient to prevent this? These questions produce different answers and different maps.
The veto map should include actors who do not appear in the formal approval chain but whose interests are significantly affected by the proposal. Actors with significant stakes in an outcome who are not formally included in the decision process often have informal channels through which they can exercise blocking power — through relationships with formal decision-makers, through their ability to raise concerns with oversight bodies, or through their practical ability to withdraw cooperation from the implementation of an approved decision.
The Strategic Implication
Veto architecture awareness changes proposal design. A proposal designed with approval in mind emphasizes the reasons it should be approved. A proposal designed with veto architecture awareness addresses the concerns of veto players — real or potential — before they become blocking objections. The difference is between seeking permission and building tolerance.
Knowing who can say yes tells you where to go for approval. Knowing who can say no tells you what has to be true before you go anywhere.
Discussion