Learn it → Apply it → Save as Skill
The shared resource nobody owns is the resource nobody protects. A commons is any resource several people can draw on where one person's use leaves less for everyone else. When no shared rule, price, or monitoring connects the private benefit of taking a bit more to its real cost, each person's individually sensible choice adds up to overuse, and the resource that made everyone better off starts to disappear for everyone, including the people who depleted it.
The Dr. Wallace's Favorite Mental Models is designed to turn useful ways of thinking into reusable tools. Each model gives you a fast visual overview, deeper interactive learning, practical application exercises and an AI-ready Markdown skill you can save for future use.
Instead of merely reading about mental models, you can gradually build your own AI skills library: a collection of portable reasoning skills that can help ChatGPT, Claude, Grok and other AI assistants apply the mental models you value.
Whoever takes one more fish, one more compute cycle, or one more grazing animal keeps the entire private benefit of that choice. The cost of a slightly smaller, slower-to-recover resource lands on everyone who shares it, spread so thin that no single user feels enough of it to stop. Repeat that math across every user, and a resource that could have supported everyone indefinitely collapses faster than any one person intended.
Important: this is not a story about greed or bad actors. The pattern shows up even when every single participant is behaving reasonably by their own local incentives; that is what makes it a structural problem rather than a discipline problem.
Most useful the moment several independent users draw on the same resource and no one is tracking the total, before you blame any single user.
The method checks whether private benefit and shared cost point in different directions before proposing a fix.
Name the shared resource and confirm it is rivalrous (one person's use leaves less for others) and hard to exclude people from.
Compare who captures the full private benefit of taking a bit more against who absorbs the shared cost. A wide gap predicts overuse.
Introduce a rule, quota, price, or monitoring step that brings the private cost of one more unit closer to its real shared cost.
Track the resource itself, not just compliance with the rule, and adjust the guardrail as conditions or group size change.
Open a use case to see what the model changes.
Each engineer benefits from pushing an ambiguous incident onto whoever else is on call, and quietly under-documenting fixes so the next fire is someone else's problem. No single engineer is being lazy; the rotation itself has no shared rule tying easy hand-offs to a visible cost, so the sloppiness compounds until the whole rotation is worse for everyone on it.
Every team writes whatever query solves its own problem fastest, and every team captures the full benefit of shipping quickly. No team owns the database's total load, so the cost of a slow, expensive query is invisible to the team that wrote it until the whole platform degrades for every team at once.
This is the model's original domain: each boat's extra catch is fully theirs, while the cost of a thinner breeding population is shared by every boat that fishes those waters next season. Without a quota, a season, or a monitored total, the incentive to take more now outruns the incentive to conserve for later.
Posting freely costs the poster nothing and might get a fast answer; reading through the resulting noise costs everyone else a little attention, repeated hundreds of times a day. No one intended to ruin the channel, but with no shared norm for what belongs there, the channel's usefulness as a shared resource erodes for the whole team.
Thousands of companies benefit fully from a free library while a handful of unpaid maintainers absorb the entire cost of triaging issues and reviewing patches. It is really closer to a funding shortfall than a depletion problem, but it shares the commons structure: benefit is dispersed, cost concentrates on whoever keeps the resource alive.
Leaving a mess or taking the closest spot saves the individual real time right now; cleaning up or parking further away costs that same individual time with no guarantee anyone reciprocates. With no visible rule or accountability, the facility degrades a little with each shortcut until it is unpleasant for everyone who uses it.
This is an illustrative example designed to teach the method.
Expand for the research and terminology behind the model, and how confident the field really is.
Economist William Forster Lloyd sketched the underlying scenario in an 1833 pamphlet, imagining herders sharing common pasture who each rationally add more cattle because the extra grazing benefit is fully theirs while the cost of a thinner pasture is shared by everyone. Biologist Garrett Hardin gave the pattern its name and its wide audience in a 1968 essay in the journal Science, titled "The Tragedy of the Commons," summarizing the mechanism in one widely quoted line: "freedom in a commons brings ruin to all."
The core mechanism, that an open-access resource with no shared accounting tends toward overuse, holds up well and is now standard in economics and environmental policy. Hardin's essay is narrower than the mechanism it describes, though: he framed privatization and government control as the only two remedies, and left out a third path that later research would document in detail, a community successfully governing a shared resource itself.
Political economist Elinor Ostrom spent decades documenting real commons that have been managed sustainably for centuries, including Swiss alpine grazing commons with records dating to 1517, without privatization or top-down government control. Her 1990 book Governing the Commons distilled these cases into design principles for durable self-governance: clear boundaries on the resource and its users, rules matched to local conditions, participation by users in making those rules, monitoring, graduated sanctions for rule-breaking, accessible conflict resolution, and recognized rights to organize. She won the 2009 Nobel Memorial Prize in Economic Sciences for this work, the first woman to receive it.
No, and this is the most common misreading of the model. "Commons" describes the resource type, shared and rivalrous; "tragedy" describes one specific failure mode, an open-access commons with no agreed rules, monitoring, or accountability. A great many commons, from community irrigation systems to well-run shared codebases, are stable and productive precisely because they are governed. The model predicts what happens in the absence of governance, not that governance is impossible.
Hardin's original essay offered just two remedies. Ostrom's research documents a well-evidenced third path, community self-governance, that fits many real situations better than either.
The pattern shows up even when every participant is behaving reasonably by their own local incentives. Treating it as a discipline problem, rather than a structural one, rarely produces a lasting fix.
Rules that work for a twelve-person team or a village-scale fishery often break down once the group grows into the thousands, because monitoring and trust get harder to sustain at scale.
A common-pool resource is rivalrous, one user's extra catch is catch someone else cannot have. A pure public good, like open-source code or broadcast signal, is not rivalrous in the same way, so a maintenance shortfall there is closer to an under-funding problem than a depletion problem, and calls for a different fix.
A quota or budget line with no monitoring or enforcement erodes almost as fast as having no rule at all; Ostrom's stable commons all pair rules with some form of visible tracking and consequence.
Fixing a commons is far easier before the resource is visibly degraded. Once trust between users and the resource itself have both eroded, recovery takes much longer than prevention would have.
several independent parties draw on the same resource, one party's use measurably reduces what is left for others, and no clear rule currently governs the total.
only two parties are involved and the resource can be cleanly divided or assigned to one owner; the full commons machinery over-complicates a deal that a direct agreement would settle.
the resource itself is fine and the real issue is one actor's misaligned incentives, not many independent users competing for a shared, shrinking pool.
This browser tool structures your thinking. It does not send your information anywhere or perform AI analysis.
Save as Skill converts the model into portable Markdown instructions that teach an AI when and how to apply the Tragedy of the Commons, what questions to ask, what evidence to seek, what mistakes to avoid and how to structure its reasoning.
Save the skills you find useful and organize them into your own reusable library. The Markdown is intentionally model-neutral, so it can be used wherever an AI system accepts uploaded files, project knowledge, custom instructions or reusable text context. Platform capabilities differ, so this is a portable skill file rather than a claim of one-click installation.
They are related but distinct, and often show up together. The free-rider problem describes people under-contributing to a public good while still benefiting from it, like skipping the group gift but still enjoying the party. The tragedy of the commons describes over-extraction from a rivalrous shared resource. The two frequently overlap, an underfunded open-source project is partly a free-rider problem, partly a maintenance commons, but the fix for each differs: a funding or contribution mechanism for free-riding, a usage limit or monitoring mechanism for overuse.
Pricing can work, a fishing quota or a metered utility bill both connect private use to a felt cost, but it is not automatic. A price set too low does not change behavior; a price set without matching monitoring can be evaded; and a price alone can shut out users who cannot pay without actually protecting the resource if enforcement is weak. Ostrom's research found that pricing is one workable tool among several, not a guaranteed fix on its own.
In brief: draw a clear boundary around the resource and who counts as a user; match rules to the resource's actual local conditions rather than importing a generic policy; let the users who are affected participate in setting the rules; monitor actual use, ideally by the users themselves; apply sanctions that start small and escalate with repeat violations; keep conflict resolution cheap and accessible; and make sure outside authorities recognize the group's right to organize its own rules in the first place.
Both extremes cause trouble, though in different ways. A group so small it cannot absorb one bad season, or so informal it has no real enforcement, can still slide into overuse despite good intentions. A group that grows into the thousands, or spans strangers with no ongoing relationship, tends to lose the monitoring and social accountability that make self-governance work, which is why very large or fully anonymous commons often end up needing formal rules, pricing, or outside enforcement instead.