One of the more unsettling things you notice after working across a significant number of organizations is how often the same dynamics appear in different contexts. A pattern of growth that hits an invisible ceiling. An initiative that generates short-term relief but makes the underlying problem worse. A competition between two teams or units that escalates until the cost of the competition exceeds the value of the resource being competed over. A shared resource that degrades because everyone uses it and no one maintains it.
These are not organizational accidents or failures of individual leadership. They are structural patterns — recurring configurations of feedback loops that produce predictable behavior in any system where they appear. Peter Senge and Jay Forrester''s work in the systems dynamics tradition named and documented these patterns as "archetypes." The practical value is significant: if you can recognize the archetype in your current situation, you know what is likely to happen next, what interventions have worked in similar structures, and what interventions have reliably failed.
This article covers the six archetypes most useful for organizational leaders: Fixes That Backfire, Shifting the Burden, Limits to Growth, Escalation, Success to the Successful, and Tragedy of the Commons. For each: the structural pattern, a concrete organizational example, the leverage point that addresses the archetype, and the common misdiagnosis that allows the archetype to continue unaddressed.
The objective is recognition, not diagrammatic fluency. Most of these archetypes can be identified from observation and experience without drawing a single causal loop diagram — but you need to know what you are looking for.
Fixes That Backfire
The structural pattern. A problem produces pressure. A quick fix is applied. The fix reduces the pressure and appears to resolve the problem. Over time, the fix produces side effects that restore the original problem — or produce a new problem that requires another quick fix. The organization becomes dependent on an escalating series of short-term fixes, each of which temporarily relieves pressure and each of which makes the underlying condition more entrenched.
The defining characteristic of Fixes That Backfire is the delay between the fix and its side effects. The fix works quickly; the side effects arrive slowly. Because the delay is long, the side effects are attributed to other causes, and the fix is applied again when the pressure returns.
Organizational example. A software development team is consistently missing delivery deadlines. The fix: reduce the time allocated to code review and automated testing to free up developer time for feature delivery. The short-term effect: more features ship in the current quarter. The delayed side effect: defect rates increase, customer-reported bugs multiply, and the team spends an increasing proportion of its time on hotfixes and rework. The original problem — missed delivery deadlines — returns, now amplified by the technical debt and quality problems produced by the fix. The team''s response: reduce testing further to free up more developer time.
This is the archetype in motion. Each application of the fix relieves pressure temporarily and makes the underlying condition worse. The team is treating the symptom (deadline pressure) and eroding the structural capacity (code quality and testing practice) that would eventually address the symptom at its source.
The leverage point. Fixes That Backfire is addressed by slowing down and examining what the fix is eroding. The leverage point is identifying the side effect and designing around it — either by choosing a different fix that does not erode the structural capacity, or by accepting a slower resolution of the pressure in exchange for not compounding the underlying problem. In the software example, the leverage point is treating code quality as a non-negotiable constraint on delivery decisions rather than a variable to be traded against delivery pressure.
The common misdiagnosis. The most common misdiagnosis of Fixes That Backfire is attributing the recurring problem to external factors or insufficient application of the fix. When the problem returns after a fix, the instinct is to apply more of the same fix — more cost cuts, more process, more headcount reduction — rather than asking whether the fix is producing the conditions that are recreating the problem.
Shifting the Burden
The structural pattern. A symptomatic problem generates pressure. There are two types of responses available: a symptomatic solution that relieves the pressure quickly, and a fundamental solution that addresses the structural source but takes longer, costs more, and is harder to implement. The symptomatic solution is applied. The pressure is relieved. The fundamental solution is deprioritized. Over time, the symptomatic solution becomes the organization''s standard response to the problem, and the organization''s capacity to implement the fundamental solution atrophies. The structural source of the problem remains or worsens, and the dependence on the symptomatic solution grows.
The archetype''s name comes from the observation that the burden of problem-solving has been shifted: from the fundamental solution to the symptomatic one. The organization is managing its symptoms rather than addressing its structural source.
Organizational example. A regional nonprofit repeatedly faces funding shortfalls. The symptomatic solution: appeals to major donors who respond reliably to personal outreach from the executive director. The pressure is relieved — the ED makes the calls, the donors give, the budget is balanced. The fundamental solution: developing a diversified, sustainable funding model with institutional grants, earned revenue, and a broad small-donor base. The fundamental solution is consistently deprioritized because the symptomatic solution works in the near term and because the ED''s time is finite. Over a decade, the organization''s relationship management with three major donors has become the entire funding model. The ED''s departure, or any one of those donors'' deaths or disengagement, produces a funding crisis with no diversified base to absorb it. The structural vulnerability has compounded.
The leverage point. Shifting the Burden is addressed by making the symptomatic solution visible as a symptomatic solution and deliberately protecting investment in the fundamental one — even when the fundamental solution is slower and the symptomatic solution is available and works. In the nonprofit example, this means capping the proportion of the budget that can be met through major donor appeals and allocating a defined portion of leadership time to fundamental infrastructure development, even in years when the symptomatic solution has handled the pressure.
The common misdiagnosis. Organizations in Shifting the Burden typically describe themselves as "pragmatic" and "resource-constrained." The symptomatic solution is framed as a rational response to real constraints. It usually is rational in the short term. The misdiagnosis is failing to see that the organization''s increasing competence at the symptomatic solution and decreasing capacity for the fundamental solution is itself a structural dynamic — not a series of reasonable short-term choices but an accumulating vulnerability.
Limits to Growth
The structural pattern. A growth-generating process produces results. Success reinforces investment in the growth-generating process, which produces more results. The reinforcing loop that drives growth is real. But as growth continues, it encounters a limiting condition — a resource, a market, a structural capacity — that constrains further growth. If the limiting condition is not identified and addressed, it produces a balancing feedback that slows and eventually reverses the growth. If the organization responds to slowing growth by pushing harder on the original growth-generating process, the limits are not addressed and eventually produce collapse rather than plateau.
Organizational example. A consulting firm grows rapidly through the quality of its delivery. Quality delivery generates referrals; referrals generate new engagements; new engagements generate more evidence of quality, which generates more referrals. The reinforcing loop is real and it has worked for years. At a certain scale, the limiting condition appears: the firm''s quality is produced by a specific cohort of senior consultants whose methods and judgment are deeply embedded in the delivery model. The scaling of the firm requires bringing in more junior staff who do not yet have those methods and that judgment. Delivery quality begins to decline — modestly at first, then more visibly. The response: push for more engagements, more referrals, more growth, to generate the revenue that will fund the senior consultants who will restore quality. The growth process is being pushed harder while the limiting condition — the delivery quality that the growth depends on — continues to erode.
The leverage point. Limits to Growth is addressed by identifying the limiting condition early and investing in it before it becomes a constraint. The leverage is not in pushing harder on the growth process but in strengthening the limit that will eventually constrain growth. In the consulting example, the investment is in the deliberate transfer of methods and judgment from senior to junior staff — mentorship, documented practice standards, apprenticeship models — before the quality decline is observable to clients.
The common misdiagnosis. The most dangerous misdiagnosis of Limits to Growth is treating the slowing of growth as a temporary plateau that more effort on the growth process will push through. This response intensifies the reinforcing loop and ignores the limiting condition, accelerating the erosion of the limit that will eventually produce the collapse. Growth that slows for structural reasons does not respond to harder effort on the same growth-generating process. It responds to investment in the constraint.
Escalation
The structural pattern. Two actors (teams, departments, organizations, individuals) each perceive the other''s actions as threats or competitive challenges. Each responds by escalating its own position. Each escalation is perceived by the other actor as a new threat, triggering further escalation. The escalation cycle amplifies until one actor withdraws, both actors exhaust their escalation capacity, or external intervention changes the dynamic. The defining feature is that neither actor''s escalation is irrational given their perception of the other''s behavior; the irrationality is in the dynamic itself.
Organizational example. Two business units in a large organization compete for shared IT resources. Unit A requests a larger allocation in the annual planning cycle; Unit B, perceiving this as a threat to its own roadmap, also increases its resource request. Both units'' requests are larger than they would have submitted in the absence of the other''s action. The IT budget is allocated proportionally to the request size, so both units have now established a new baseline for what a "competitive" resource request looks like. Next year, both request even more, escalating from their new baselines. Within three annual cycles, both units are submitting resource requests that are significantly larger than their actual capacity to absorb, IT is allocating resources on the basis of political positioning rather than genuine need, and the overall quality of IT resource allocation has declined for the organization as a whole.
The leverage point. Escalation archetypes are addressed by changing the structure of the interaction between the actors, not by negotiating with the actors within the existing structure. In the resource competition example, the leverage point is changing the allocation mechanism from a competitive bidding process to a needs-based assessment with objective criteria — removing the incentive for escalation by decoupling allocation from request size. Alternatively, making each unit''s requests visible to the other and requiring joint justification introduces transparency that reduces the escalation dynamic.
The common misdiagnosis. Escalation is frequently misdiagnosed as a conflict between individuals who need mediation or a cultural problem that needs values work. The interpersonal framing is understandable — people are visibly in conflict — but it does not address the structural dynamic. Mediating the specific conflict or running a values workshop does not change the incentive structure that produces the escalation. The escalation will recur in the next resource cycle or the next competitive situation because the structure that generates it has not been addressed.
Success to the Successful
The structural pattern. Two activities or actors compete for the same limited resource. Success by one produces increased resource allocation, which produces more success, which produces more resource allocation. The other''s relative resource disadvantage produces reduced performance, which produces reduced resource allocation, which produces further performance decline. The reinforcing loop amplifies an initial advantage — even a small one — into a dominant position. The structural feature is that the competition is decided not by the quality difference between the activities but by the accumulation of initial advantage.
Organizational example. A firm has two product lines competing for internal investment capital. Product Line A has a strong Q1, generating high revenue and a positive ROI narrative. Product Line B has a flat Q1 due to a product launch delay that is structural and temporary. Investment committee decisions in Q2 allocate incrementally more capital to Product Line A, which is performing, and incrementally less to Product Line B, which appears to be underperforming. Product Line A''s increased capital produces further performance improvement; Product Line B''s reduced capital slows its recovery. By Q3, Product Line A has built a performance record and resource base that makes the investment case for B increasingly difficult to make. By the end of the year, Product Line B is being discussed as a candidate for divestiture — not because it is fundamentally weaker but because its initial disadvantage was amplified through an investment allocation dynamic that rewards demonstrated success with the resources required to produce further success.
The leverage point. Success to the Successful is addressed by designing resource allocation mechanisms that evaluate potential rather than demonstrated performance, or by deliberately protecting resource floors for activities that have structural value that is not reflected in short-term performance. In the product line example, the leverage point is making the Q1 delay''s temporary cause explicit in the investment review, establishing a review horizon that is appropriate for the product development cycle, and protecting Product Line B''s minimum resource level across one full product cycle before drawing conclusions about its relative value.
The common misdiagnosis. This archetype is frequently experienced as a natural sorting process — "we''re just allocating resources to where they produce the most value." The misdiagnosis is failing to see that the allocation mechanism is shaping the performance outcomes it claims to be responding to. When resource allocation decisions produce the performance outcomes that then justify the resource allocation decisions, the organization is not evaluating performance objectively — it is operating a self-reinforcing cycle that amplifies initial advantage.
Tragedy of the Commons
The structural pattern. A shared resource is available to multiple actors. Each actor can use the shared resource to produce benefit for itself. The individual benefit of using the resource is immediate and accrues entirely to the individual actor. The cost of using the resource — its depletion — is shared across all actors and arrives slowly. Each individual actor, rationally maximizing its own benefit, uses the resource at a rate that produces individual benefit exceeding individual cost. The aggregate of rational individual decisions produces collective cost that exceeds collective benefit: the shared resource is depleted.
Organizational example. A professional services firm has a shared pool of senior advisors whose expertise can be requested for client engagements by any practice. Each practice leader rationally requests the senior advisors for their highest-priority engagements. The individual practice benefit — higher-quality delivery, stronger client relationships — is immediate and attributable. The shared cost — the senior advisors'' capacity for development work, knowledge documentation, mentoring, and firm-building activities — is distributed across all practices and arrives slowly in the form of declining advisor capacity and firm-level knowledge atrophy. Each practice leader is making rational resource decisions. The aggregate of those decisions is depleting the firm''s most critical shared resource.
The leverage point. Tragedy of the Commons is addressed by making the shared cost visible and attaching it to the individual actors making the consumption decisions. This can be done through explicit capacity accounting (senior advisors'' development time is tracked and protected), allocation governance (senior advisor time is a budgeted resource with explicit limits per practice), or by creating incentives for practices to invest in the shared resource (practices that produce senior advisors receive credit toward future access to them). The structural requirement is that the individual actors experience some proportion of the shared cost of their consumption decisions — not just the individual benefit.
The common misdiagnosis. Organizations in Tragedy of the Commons typically recognize the symptom — the shared resource is degrading — and respond with appeals to collective responsibility or cultural values. These responses ask individuals to voluntarily internalize a shared cost that the system''s structure externalizes to the collective. Appeals to collective responsibility work modestly in contexts where actors are closely identified with the collective and the shared cost is visible. They do not work reliably in organizational contexts where the actors are optimizing under competitive pressure and the shared cost arrives too slowly to be visible in real time. Structural governance of the shared resource is more reliable than appeals to voluntary restraint.
Using Archetypes in Practice
The value of archetypes is in recognition, not in naming. The goal is not to correctly identify that the organization is experiencing an instance of a specific archetype. The goal is to recognize the structural pattern early enough to choose a leverage-point intervention rather than a symptomatic one.
Archetypes are easiest to identify when you are looking for the defining feature of each: the recurring problem despite repeated symptomatic fixes (Fixes That Backfire), the symptomatic solution that is crowding out the fundamental one (Shifting the Burden), the growth that is slowing despite harder effort on the growth process (Limits to Growth), the escalation dynamic that is irrational in aggregate though rational in each step (Escalation), the initial advantage that is self-amplifying through resource allocation (Success to the Successful), the shared resource that is being rationally depleted (Tragedy of the Commons).
Most persistent organizational problems have one of these six structures underneath them. The diagnostic question is not "what happened recently that caused this?" but "what structural pattern is producing this behavior?" The answer usually points to a leverage point that is different from the intervention the organization is already applying — and usually more durable.