Learn it → Apply it → Save as Skill
Institutions tend to preserve the problem to which they are the solution. A department, vendor, program, or role that is funded to fix something has, built into its own survival, a quiet incentive to make sure the fixing never quite finishes.
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.
Before trusting a plan to "fix" something, ask who is currently paid, promoted, or made relevant by that problem staying unsolved. If the answer is the very entity proposing the fix, treat the plan with extra scrutiny — not automatic suspicion.
Important: a parasite that kills its host loses its home. An institution that fully solves its founding problem can lose its budget. Neither outcome requires conscious scheming — only a structure where survival and resolution pull in opposite directions.
Most useful when a well-funded effort to solve a persistent problem keeps running, keeps growing its budget, and keeps reporting progress — without the problem actually shrinking.
The principle names a pattern. These four steps turn it into something you can actually check.
Notice when a problem that funds or justifies a role, department, vendor, or program never quite gets solved despite dedicated resources and years of "progress."
Map who gets paid, promoted, re-elected, or kept relevant by the problem's continued existence — not just who claims to be solving it.
Ask "cui bono?" (who benefits?). Rule out plain incompetence or bureaucratic inertia first — Hanlon's Razor often explains more than self-interest does.
If the incentive really is misaligned, change the incentive, not just the plan: pay for outcomes, sunset the role, rotate the mandate, or add outside accountability.
Open a use case to see what the model changes about how you'd approach it.
Check whether the vendor's billing model rewards faster closure or more billable hours. If support time is billed hourly with no cap, the Shirky Principle predicts slow resolution even with no malice involved — the incentive alone explains the pattern. Consider fixed-fee or outcome-based contracts.
Separate "the cause is genuinely hard" from "the organization's funding model rewards ongoing awareness over measurable closure." Ask what would happen to the organization's budget and staff if the problem were 90% solved next year — if the honest answer is "shrink sharply," expect resistance to interim wins that look like completion.
Check whether the regulated industry or the regulating agency (or both) benefit more from managed complexity than from a simple fix. Complexity that is expensive to navigate often advantages whoever can already afford the navigation — sometimes the regulator's own budget depends on continued oversight demand.
Ask who owns the budget line for maintaining it versus who would own the (smaller) budget line after replacement. Internal teams sized around maintaining a painful system have a quiet stake in the pain continuing to justify their headcount — look for ownership that would shrink on success.
Distinguish a genuinely evolving risk landscape from a team whose relevance depends on a visible backlog of findings. A healthy signal is a program that is comfortable reporting "nothing significant this quarter" without treating it as a threat to its own existence.
Watch for advice that reliably concludes "you need more time with me" rather than "here is how to no longer need this service." A trustworthy advisor can describe the point at which you should not need them anymore — ask for it directly.
This is an illustrative example designed to teach the method, not a claim about any real organization.
Expand for the distinction between who named the principle and who developed the underlying observation.
Wired editor Kevin Kelly coined the name in a 2010 blog post, attributing the underlying observation to writer and NYU scholar Clay Shirky. Kelly stated the principle as: "Institutions will try to preserve the problem to which they are the solution."
Shirky developed the idea through talks, essays, and his book Cognitive Surplus (2010), writing about how institutions built to coordinate a solution can develop a structural stake in the coordination problem persisting, separate from any individual's conscious intent.
The principle has looser and stricter readings. A narrow reading implies deliberate self-preservation. A broader reading — "every entity tends to prolong the problem it is solving" — makes no claim about intent at all, describing a structural tendency that can arise from bureaucratic habit as easily as from scheming. Treat it as a tendency to investigate, not a universal law or an accusation.
Two companion ideas discipline the principle. Cui bono ("who benefits?") forces you to name a specific beneficiary and mechanism rather than gesture at vague self-interest. Hanlon's Razor ("never attribute to malice what is adequately explained by stupidity, inertia, or genuine difficulty") forces you to rule out simpler explanations before concluding an institution is preserving its problem on purpose.
Most institutional drag is habit, caution, or genuine difficulty, not scheming. Apply Hanlon's Razor before concluding self-interest.
Some problems — disease, poverty, deep security threats — are simply hard. Slow progress is not automatic proof of a preserved problem.
Using the principle to wave away any institution you already dislike, without naming who benefits and how, turns a diagnostic tool into a slogan.
Declaring self-interest without naming a specific beneficiary and mechanism is an assertion, not an analysis.
The useful response is usually to redesign the incentive — fund outcomes, not activity — not to eliminate the function and lose real capability.
Many institutions do solve themselves toward a smaller mandate — successful vaccination campaigns scale down, debt-collection agencies close accounts, task forces disband on schedule. The pattern is a tendency, not a law.
the evidence points to simple inertia, understaffing, or genuine complexity rather than any identifiable party benefiting from non-resolution.
you need a legal or financial finding of wrongdoing. The Shirky Principle is a diagnostic heuristic, not evidence of fraud or misconduct.
incentives are already well aligned with solving the problem and the real issue is simply poor planning or slow delivery.
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 Shirky Principle, what questions to ask, what evidence to seek, what mistakes to avoid, and how to structure its analysis.
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.
Kelly's formulation is about institutions, but the same logic can appear in a role or job function — a personal trainer, a tech-support contractor, a recurring advisor — whenever their income depends on an ongoing problem rather than its resolution. Scale the scrutiny to the size of the stake, not the size of the organization.
Corruption usually implies conscious, often illegal, self-dealing. The Shirky Principle describes a structural tendency that can produce the same outcome without anyone breaking a rule or even being aware of it — a budget that only grows when backlog grows will shape behavior over time even if no one involved ever decides to "preserve" anything.
Finding that the entity's funding, staffing, or relevance would hold steady or improve if the problem were fully solved. If success would not cost the entity anything, the structural incentive for preservation is absent, whatever other issues might remain.