Skip to content

Separation of Powers

Why It Matters

Concentrating power creates both agency problems (rulers pursue their interests, not the ruled's) and knowledge problems (no single actor has all relevant information). Separation forces negotiation, which aggregates information and limits unilateral action. The systematic error it corrects: assuming that whoever implements policy should also design it, or that unitary decision-making is always more efficient than divided authority.

The Key Move

For any institutional design, identify the stages of decision-making: initiation (who proposes?), deliberation (who debates?), approval (who decides?), implementation (who executes?), review (who checks?). Assign these to different actors with different selection mechanisms, constituencies, and time horizons. The more consequential the decision, the more you want these separated.

Classic Application

U.S. Constitution's legislative-executive-judicial separation. Congress proposes laws, the President can veto (creating a negotiation point), courts can review (creating a legitimacy check). The structure makes rapid change difficult, which is the point - it prevents both tyranny and mob rule. The specific allocation is less important than the principle: slice decision-making so no faction can unilaterally impose its will.

Surprising Application

Software architecture and API design. Separate data (state), business logic (rules), and presentation (interface). Separate read from write authority. This isn't just technical modularity - it's applying separation of powers. The database can't unilaterally change business rules; the interface can't bypass validation. Each layer is a veto point that prevents errors from cascading. The reasoning is identical: divide authority to reduce failure modes.

Failure Modes

  • Over-separation leading to gridlock: too many veto points means nothing gets done. The tool assumes some action is better than perfect stasis, which isn't always true.

  • Separation without independence: if the "separated" powers are controlled by the same faction, you get the costs (complexity, delay) without the benefits (checking, information aggregation).

  • Ignoring informal power: formal separation means nothing if one branch has de facto dominance through custom, resource control, or popular legitimacy.

Go Deeper

  • Federalist Papers #47-51 (Madison) - original theoretical justification
  • Tsebelis, Veto Players - formal treatment of how veto points affect policy stability