Core Concepts: The IAD Framework (Institutional Analysis and Development)
The action arena
The core unit of analysis is the action arena — any situation where people interact under a shared set of rules to produce outcomes. A council meeting, a ward committee, a Budget Committee deputation, or your own group’s strategy session are all action arenas.
Three inputs that shape an action arena
- Rules-in-use — not the law on paper, but what’s actually operative:
- Boundary rules — who’s allowed in
- Choice rules — what actions are permitted
- Aggregation rules — how individual choices combine into a group decision
- Information rules — who has to disclose what
- Payoff rules — who bears costs/benefits
- Scope rules — where the arena’s authority stops
- Biophysical/material conditions — the nature of what’s actually at stake. A fixed pot of capital budget behaves differently than a renewable service like waste collection.
- Community attributes — shared norms, trust, history of working together.
Outcomes and feedback
Outcomes get evaluated (efficient? fair? accountable?) and can feed back to change the rules — this feedback loop is why institutions evolve instead of staying frozen.
Three nested levels of rules
- Operational — day-to-day choices (a bylaw, a permit, a budget line item).
- Collective-choice — rules about how operational rules get made or changed (how Council sets policy; the strong-mayor budget-amendment window is a collective-choice rule).
- Constitutional — rules about who’s even eligible to participate in collective-choice — who gets to decide how decision-making power is allocated in the first place.
How this ties files 01 and 02 together
Elinor’s 8 principles (file 01) are specific rule configurations within a single action arena. Vincent’s polycentricity (file 02) is what you get when multiple arenas overlap or nest, tied together by a shared constitutional layer. Same vocabulary, different zoom level.
Applying the levels to your context
At the operational level, facing an individual resident, a governance-restructuring trend can genuinely point toward fewer decision venues and less redundancy — the thing principle 8 and the 1961 anti-consolidationist argument warn against. Don’t soften that if it’s true.
But the more useful diagnosis usually isn’t “mono vs. poly outcome” — it’s who controls the constitutional-level process deciding that outcome. If that’s a higher authority acting top-down with no collective-choice mechanism for the residents it affects, that’s the actual strategic target: not reversing the restructuring, but getting a voice into how the new rules get written before they harden — because once constitutional-level rules (rules about how rules get made) are set, whether operational-level subsidiarity exists inside them is still unwritten.