← Theory & Methodology

Core Concepts: Elinor Ostrom’s Design Principles for Common-Pool Resources

Template layer — city-agnostic. Fill in your own local translations under each principle.

The problem this solves

Conventional wisdom said a shared resource has two possible fates: privatize it, or have the state regulate it — otherwise people overuse it until it collapses (the “tragedy of the commons”). Elinor Ostrom spent decades documenting a third option: communities governing shared resources themselves, successfully, for centuries, without private ownership or state control — if certain conditions hold. Those conditions are the eight design principles below.

What CPR means

CPR = common-pool resource. A resource that is:

• Rivalrous — one person’s use subtracts from what’s left for others.
• Non-excludable — hard to stop people from using it without heavy cost.

Classic examples: a fishery, a grazing pasture, an aquifer, an irrigation system. For a citizen-engagement group, the CPRs usually aren’t physical — they’re things like a ward/district’s council seat, its slice of the capital budget, planning/zoning approval capacity, and council’s own collective-choice authority. Anyone with a stake can draw on these; what one faction or project claims is less available to others. Identify your own local group’s specific CPRs before filling in the principles below — principle 1 (boundaries) is unanswerable without this.

The 8 design principles

Each stable commons Ostrom studied shared these features (from Governing the Commons, 1990; later formalized in the IAD framework, see the companion IAD template).

1. Clearly defined boundaries

Who may draw on the resource, and what the resource’s own boundaries are. How to apply: name your group’s membership boundary (which residents, which district) and the specific CPRs at stake (an open council seat, the local capital-plan slice, zoning approval capacity, any budget-authority mechanism worth tracking).

2. Congruence with local conditions

Rules matched to local conditions, not imposed uniformly. How to apply: identify what makes your specific district’s pressures different from a neighboring one (density, development type, demographics) — and the ask that follows (a mandated local consultation trigger, not a generic city-wide notice).

3. Collective-choice arrangements

Those affected by rules can participate in modifying them. How to apply: find your city’s own version of a council-vs-mayor (or council-vs-province) authority-narrowing mechanism — a budget-amendment window, a veto power, a delegated-authority bylaw. This is usually the strongest, most citable finding available; look for a moment where the body that’s supposed to check power voted to check itself less.

4. Monitoring

Monitors are accountable to the users, or are users themselves. How to apply: set up a rotating (not single-gatekeeper) team tracking whatever the relevant public body is (a transition board, a committee, a candidate race) and publish findings openly.

5. Graduated sanctions

Penalties scaled to the seriousness and context of the violation. Internally (see the constitution template): direct conversation → group discussion → removal, never a first-offense expulsion. Externally: find your jurisdiction’s actual accountability mechanism (an integrity commissioner, an ombudsman) and ask candidates whether they’d support it being genuinely enforced.

6. Conflict-resolution mechanisms

Rapid, low-cost means for resolving conflicts. Internally (see the constitution template): same-week discussion with a neutral member before anything escalates publicly. Externally: find your jurisdiction’s actual planning-dispute appeal path and assess who it really favors (residents, or whoever can afford a lawyer) — then ask for a cheaper local-mediation step before that path.

7. Minimal recognition of rights to organize

External authorities don’t challenge the group’s right to self-organize. How to apply: name any top-down, no-consultation process a higher authority (province/state) is running that affects your city — this usually mirrors the group’s own internal principle (no funder or candidate dictates the group’s internal governance either).

8. Nested enterprises

For larger systems, governance is organized in multiple layers — local units handle local matters, a coordinating layer handles only what genuinely can’t be handled locally. How to apply: this is usually the central strategic argument — defend real regional/city-wide coordination (water, transit — genuinely supra-local matters) while pushing subsidiarity for genuinely local matters (traffic calming, parks, zoning variances). Design your group’s own structure the same way: local cells feeding a coordinating body, ready to activate if neighboring districts join.

Note on wording

There are two canonical phrasings: the 1990 original (CPR-specific, from Governing the Commons) and the 2013 generalized version (Wilson, Ostrom & Cox, “Generalizing the core design principles for the efficacy of groups”) — same eight, reworded to apply to any cooperative group rather than natural-resource users specifically. This file uses the general sense of each principle; cite Governing the Commons (1990) as the primary source when precision matters.