Ostrom's Design Principles

Thinking Tools4.4 Refining Ideas Into Practical SolutionsAlso known as Commons Design Principles

Originated by Elinor Ostrom (Governing the Commons, 1990).

Eight conditions, from clear boundaries and fitting rules to graduated sanctions and nested governance, that long-lived shared-resource arrangements tend to meet and failed ones tend to miss.

A shared pool of platform engineering hours, checked against the eight design principles

Fourteen product teams draw on one pool of platform engineers. Each principle is scored by how far the arrangement falls short of it, from 1 (met) to 5 (missing); the list puts the biggest gap first, the one to strengthen first. Rescore a principle after a fix and watch the verdict. Illustrative.

Clear boundaries: who may draw hours, and for what kind of work

Gap2

Rules fit local conditions: what a team gets matches what it puts in

Gap4

The teams who use the pool can change its rules

Gap4

Use is monitored by people answerable to the teams

Gap1

Penalties start small and grow with repeat overuse

Gap4

Disputes are settled quickly and cheaply

Gap5

Leadership and finance respect the rules the teams set

Gap2

Larger pools are nested, with local rules inside shared ones

Gap3

Average gap3.1

VerdictScore every row to see the verdict.Likely to lastThe arrangement meets most principles; keep watching the weakest.FrayingSeveral principles are weak; teams will start working around the pool. Fix the biggest gap first.Likely to failMost principles are missing: expect hoarding, quiet exits, and a call to split the pool.

Biggest gap first

  1. 5.0Disputes are settled quickly and cheaply
  2. 4.0Rules fit local conditions: what a team gets matches what it puts in
  3. 4.0The teams who use the pool can change its rules
  4. 4.0Penalties start small and grow with repeat overuse
  5. 3.0Larger pools are nested, with local rules inside shared ones
  6. 2.0Clear boundaries: who may draw hours, and for what kind of work
  7. 2.0Leadership and finance respect the rules the teams set
  8. 1.0Use is monitored by people answerable to the teams

An example

Two years ago, a software company pooled its platform engineers for fourteen product teams to share. By now the pool was fraying. Three teams had hired their own platform people, two others filed every request as urgent, and the platform lead spent Fridays settling arguments.

Before splitting it, a director scored how far the pool fell short of each of the eight design principles. Monitoring was strong, since every hour sat on a shared board, and boundaries and leadership's respect for the rules were close. The rest were weak. The teams that drew most contributed no budget, the rules had come from the technology office with no say from the teams, the only penalty was losing access, which nobody ever imposed, and disputes waited three weeks for the chief technology officer. That was the worst gap. The fix started there: a monthly meeting of team leads with authority over the rules, a two-day dispute window, and a small step-up in charges for teams that overran their share. Two of the three teams with their own hires folded them back in.

Why it works

Shared resources tend to be blamed on human nature when they fail: people overuse what nobody owns. The principles shift the question to design. Long-lived arrangements share recognizable features, and failing ones usually lack several, so a fraying pool is a set of specific gaps, each with its own repair.

The principles work as a set. Clear boundaries make monitoring possible, monitoring makes graduated penalties fair, and the right of users to change the rules is what keeps the rules fitting as conditions change. Cheap dispute settlement keeps small conflicts from becoming reasons to leave. Checking all eight against the arrangement shows which link in that chain is broken, which is usually more useful than the choice leadership reaches for first, between splitting the resource and centralizing it.

The thinking behind it

Elinor Ostrom Elinor Ostrom, an American political scientist, set out the principles in Governing the Commons (1990). From field studies of fisheries, forests, and irrigation systems, she showed that communities can govern shared resources without privatization or control by the state, and she distilled eight design principles that the long-lived arrangements tended to share and the failed ones tended to lack. In 2009 she became the first woman to receive the Nobel Memorial Prize in Economic Sciences. The principles describe tendencies across many cases; they are a diagnostic, and no single one guarantees success.

How to run it

  1. Confirm it is a shared resource. Check that many users draw on it, that one user's draw leaves less for others, and that excluding users is hard.
  2. Check the boundaries. Write down what the resource covers and who may use it; vague edges invite overuse.
  3. Check that the rules fit and can change. Ask whether what each user gets matches what they put in, and whether users have a say in the rules.
  4. Check monitoring, penalties, and disputes. Look for monitors answerable to users, penalties that start small, and a quick, cheap way to settle conflicts.
  5. Check how outside authority treats it. Ask whether leadership respects the users' own rules, and whether larger pools nest smaller ones.
  6. Score each principle's gap. Rate how far the arrangement falls short of each, from met to missing, with evidence for each score.
  7. Strengthen the biggest gap first. Fix the weakest principle, then rescore after a cycle before touching the next.

Where it goes wrong

The most common failure is skipping the check and choosing between privatizing and centralizing. Splitting the pool or handing it to one owner both remove the shared resource, and both cost the benefits that made pooling worth doing. Check the eight first.

The second is adding rules from the top. Rules written by leadership without the users' say tend not to fit local conditions and get worked around. If users are evading the rules, the gap is usually in who makes them.

The third is treating the list as a recipe. The principles describe what long-lived arrangements tended to share across many cases. Meeting all eight improves the odds and guarantees nothing, so watch how the users actually behave after each change.

When to use something else

  • Tragedy of the Commons. When the task is explaining why a shared resource is being overused, before designing any fix.
  • Mechanism Design. When the rules are being built from scratch and the question is which incentives make honest use the best strategy.
  • Power-Interest Grid. When the redesign needs support from the groups who will gain or lose, and their influence needs mapping.

Where it sits in SOLVE eX

Go to the source

  • Governing the Commons: The Evolution of Institutions for Collective Action, Cambridge University Press, 1990

Back to the catalog