System Archetype Diagnosis

Match a recurring feedback pattern to a known system archetype so the likely failure mode and intervention family become visible.

Version

v1 · 2026-08-24 · History

Solution archetype #

1051

Problem family

Representation, Classification & Model Misfit

Problem subfamily

Model Assumption, Regulation & Residual Refinement

Essence

System Archetype Diagnosis turns recurring system trouble into a structural diagnosis. Instead of asking only who made a mistake or which local fix was insufficient, it asks what feedback pattern keeps regenerating the behavior. The archetype is useful when a problem repeats across time, departments, policies, markets, or communities and the visible symptoms do not explain why ordinary fixes fail.

The key move is not simply naming a famous pattern. The key move is to map the loops, compare the map to known archetype templates, test whether the match actually fits, and then use the diagnosis to choose intervention families.

Compression statement

When a complex problem repeats despite local fixes, map the feedback loops, compare the structure to known system archetypes, validate the fit, and use the diagnosis to identify leverage points and intervention families.

Canonical formula: recurring symptoms + causal loop map + fit evidence + counterexample check -> archetype match -> leverage-point-informed intervention choice

When This Archetype Applies

Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.

Diagnostic problem

A system exhibits recurring behavior generated by a familiar feedback structure, but actors treat each occurrence as a local event, personality problem, resource shortage, or one-off failure. Because the feedback pattern remains unnamed, interventions target symptoms and the problem returns.

What this problem means

The structural problem is that actors experience events, while the system behaves through loops. People see a backlog, a conflict, a shortage, or a failure. They respond to that symptom. Their response changes incentives, capacity, trust, delay, resource availability, or expectations. Those changes then feed back into the original symptom, sometimes after enough delay that the connection is missed.

Without archetype diagnosis, each recurrence is treated as new. The organization keeps solving the apparent problem while preserving the structure that regenerates it.

Applicability expression6 distinct conditions

Recurring failed fixesandConnected stakeholder symptomsandWhole-harming local optimizationandDelayed relief reversalandFragmented loop visibilityandRecognizable system archetype

Algebraic1∧2∧3∧4∧5∧6

groundedpartly groundedopen

6 conditions, all required.

6Required in every casenumbered 1–6

These hold no matter which pattern applies.

1

Recurring failed fixes · grounded

The same problem recurs after apparently reasonable fixes. more

primeSystem Archetypes— Recurring configurations of reinforcing and balancing feedback loops that generate the same characteristic system behavior across different domains, enabling structural diagnosis instead of symptom-chasing.

and — also required

2

Connected stakeholder symptoms · grounded

Different stakeholders describe separate symptoms that appear connected through delay, incentive, resource, or dependency loops. more

primeSystem Archetypes— Recurring configurations of reinforcing and balancing feedback loops that generate the same characteristic system behavior across different domains, enabling structural diagnosis instead of symptom-chasing.

and — also required

3

Whole-harming local optimization · grounded

Local optimization improves one part of the system while worsening the whole. more

primeSystem Archetypes— Recurring configurations of reinforcing and balancing feedback loops that generate the same characteristic system behavior across different domains, enabling structural diagnosis instead of symptom-chasing.

and — also required

4

Delayed relief reversal · grounded

Short-term relief is followed by delayed deterioration, relapse, escalation, or renewed constraint. more

primeSystem Archetypes— Recurring configurations of reinforcing and balancing feedback loops that generate the same characteristic system behavior across different domains, enabling structural diagnosis instead of symptom-chasing.

and — also required

5

Fragmented loop visibility · grounded

Actors disagree about causes because each sees only one segment of a circular causal structure. more

primeSystem Archetypes— Recurring configurations of reinforcing and balancing feedback loops that generate the same characteristic system behavior across different domains, enabling structural diagnosis instead of symptom-chasing.

and — also required

6

Recognizable system archetype · grounded

The system has enough recurring structure to compare against known archetypes rather than requiring a novel causal model from scratch. more

primeSystem Archetypes— Recurring configurations of reinforcing and balancing feedback loops that generate the same characteristic system behavior across different domains, enabling structural diagnosis instead of symptom-chasing.

Coverage

6 of 6 conditions grounded.

Read the methodology · Download the trigger-logic data

When to Use This Archetype

Use this archetype when a system repeatedly returns to the same kind of problem after local correction. Typical clues include short-term fixes followed by relapse, growth that stalls against a constraint, escalation between actors, shared-resource degradation, or repeated surprise that the same problem appears in new places.

It is especially appropriate when the team needs a shared explanation before choosing an intervention. A diagnosis such as limits to growth, shifting the burden, fixes that fail, escalation, or tragedy of the commons can make hidden feedback visible, but the label must be earned by evidence.

Structural Problem

The structural problem is that actors experience events, while the system behaves through loops. People see a backlog, a conflict, a shortage, or a failure. They respond to that symptom. Their response changes incentives, capacity, trust, delay, resource availability, or expectations. Those changes then feed back into the original symptom, sometimes after enough delay that the connection is missed.

Without archetype diagnosis, each recurrence is treated as new. The organization keeps solving the apparent problem while preserving the structure that regenerates it.

Intervention Logic

The intervention begins by collecting the recurring symptoms and the time horizon over which they repeat. Then it maps causal relations, feedback loops, delays, constraints, incentives, and actors. The map is compared against candidate system archetypes, and the diagnosis remains provisional until pattern-fit evidence is stronger than the alternatives.

After the pattern is named, the work shifts to intervention choice. A limits-to-growth diagnosis suggests looking for the binding constraint. A shifting-the-burden diagnosis suggests reducing dependency on symptomatic relief while strengthening the fundamental solution. A fixes-that-fail diagnosis suggests examining delayed side effects of the fix itself. The diagnosis is only useful if it changes where and how the system is acted upon.

Key Components

System Archetype Diagnosis converts recurring trouble into a structural explanation through a sequence that begins with evidence and ends with action, with explicit guardrails against premature labeling. The Symptom Pattern gathers the repeated observable signs — overload, relapse, oscillation, escalation, stalled growth, unintended consequences — that suggest a deeper feedback structure rather than a one-time failure. The Causal Loop Map bridges those events to structure by showing how variables influence one another and where effects return to shape their own causes, distinguishing reinforcing loops, balancing loops, delays, constraints, and incentives. The Feedback Loop Boundary decides what belongs inside the diagnostic frame; if it is too narrow the analysis collapses into local blame, and if it is too broad the model becomes too vague to act on. These three components establish the empirical base before any pattern name is invoked.

The middle three components turn the mapped structure into a tested diagnosis rather than a slogan. The Archetype Match compares the local structure to known templates — limits to growth, shifting the burden, fixes that fail, escalation, tragedy of the commons — and records both what fits and what does not. The Pattern-Fit Evidence explains why the selected archetype is credible, drawing on loop relations, time patterns, delayed effects, repeated responses, stakeholder observations, and anomalous cases. The Counterexample Check is the main internal guardrail against overmatching: it asks what evidence would make the proposed archetype wrong, compares alternative archetypes, and looks for missing variables or boundary errors that could overturn the diagnosis.

The final three components ensure the diagnosis becomes intervention rather than interpretation. The Leverage Point identifies where action could change the feedback pattern — a rule, delay, incentive, information flow, capacity constraint, ownership boundary, or resource allocation — because a named archetype without leverage is only commentary. The Intervention Playbook connects the diagnosed pattern to response families, narrowing the field of plausible actions without replacing local design. The Monitoring Signal checks whether the diagnosed pattern is actually changing after intervention; if the expected feedback response does not appear, the diagnosis itself should be revised rather than the action redoubled.

Component	Description
Symptom Pattern ↗	A symptom pattern gathers the repeated observable signs that suggest a deeper structure. It may include recurring overload, relapse, oscillation, escalation, stalled growth, or unintended consequences. The symptom pattern is evidence, not the diagnosis itself.
Causal Loop Map ↗	A causal loop map shows how variables influence one another and where effects return to shape their own causes. It is the bridge between local events and structural explanation. A weak map merely lists events; a useful map reveals reinforcing loops, balancing loops, delays, constraints, and incentives.
Feedback Loop Boundary ↗	The feedback loop boundary defines what belongs inside the diagnostic frame. If the boundary is too narrow, the diagnosis becomes blame of local actors. If it is too broad, the model becomes too vague to act on. Boundary choice determines which variables can explain recurrence.
Archetype Match ↗	The archetype match compares the mapped structure to known system archetypes. It names the closest structural pattern only after the map, symptoms, delays, and outcomes fit. A match should also record what does not fit.
Pattern-Fit Evidence ↗	Pattern-fit evidence explains why the selected archetype is credible. It can include loop relations, time patterns, delayed effects, repeated responses, stakeholder observations, and anomalous cases. This component prevents diagnosis from becoming slogan use.
Counterexample Check ↗	The counterexample check asks what evidence would make the proposed archetype wrong. It compares alternative archetypes and looks for missing variables or boundary errors. This is the main internal guardrail against overmatching.
Leverage Point ↗	A leverage point identifies where intervention could change the feedback pattern. It might be a rule, delay, incentive, information flow, capacity constraint, ownership boundary, or resource allocation. Diagnosis without leverage points is only interpretation.
Intervention Playbook ↗	An intervention playbook connects the diagnosed pattern to response families. It does not replace local design; it narrows the field of plausible actions. The playbook remains a component here because the separate playbook candidate is still second-wave and merge-sensitive.
Monitoring Signal ↗	A monitoring signal checks whether the diagnosed pattern is actually changing after intervention. If the expected feedback response does not appear, the diagnosis should be revised.

Common Mechanisms

10 documented mechanisms across 4 implementation forms.

The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.

Analysis, Modeling & Optimization · 6 mechanisms

• Causal Loop Diagram — Draws the pressure behind a hazard, the feedback loops that regenerate it, and the delays between them, so a control can be aimed at the loop rather than the symptom it displaces.
• Escalation Archetype Mapping — Maps a runaway tit-for-tat between two parties as the Escalation archetype — two balancing loops coupled through relative position — so the rivalry can be diagnosed instead of fought.
• Fixes That Fail Diagnosis — Diagnoses a problem that keeps relapsing as Fixes That Fail — a quick fix whose delayed side effect quietly recreates the very symptom it relieved.
• Leverage Point Matrix — Ranks candidate places to intervene in the diagnosed loop by how much structural change each buys, so effort goes to high-leverage sites instead of the obvious low-leverage ones.
• Limits to Growth Diagnosis — Diagnoses stalled growth as Limits to Growth — a reinforcing engine running into a balancing constraint — and locates the binding limit that caps it.
• Shifting the Burden Diagnosis — Diagnoses a deepening reliance on a symptomatic quick fix as Shifting the Burden — where the easy relief crowds out and atrophies the fundamental solution.

Assessment, Review & Assurance · 2 mechanisms

• Archetype Fit Checklist — Tests a proposed system-archetype match against its evidence and its strongest rival before the label is allowed to guide action.
• Tragedy of the Commons Diagnosis — Diagnoses the degradation of a shared resource as Tragedy of the Commons — where individually rational use, summed across users, destroys the pool everyone depends on.

Communication, Facilitation & Learning · 1 mechanism

• Pattern Diagnosis Workshop — Convenes the people who each see one arc of a recurring problem to build a shared loop map and narrow to a provisional archetype together.

Representation, Specification & Plan · 1 mechanism

• System Archetype Template — A reusable pattern card — typical symptoms, loop skeleton, and intervention hints for one named archetype — used as the reference a live map is matched against.

Parameter / Tuning Dimensions

Important tuning dimensions include the diagnostic boundary, the time horizon, the granularity of variables, the required confidence threshold for naming an archetype, the number of alternative diagnoses preserved, and the level of evidence required before intervention.

Another major tuning dimension is action proximity. Some uses only create shared understanding. Stronger uses select interventions, redesign incentives, or change governance. The stronger the action, the more validation the diagnosis needs.

Invariants to Preserve

The diagnosis must preserve structural fit, causal traceability, stakeholder contestability, and intervention relevance. A named archetype should remain linked to observed behavior and loop evidence. Alternative explanations should not disappear just because one label is memorable.

The most important invariant is that the archetype name is not the solution. It is a map from recurring behavior to likely leverage points.

Target Outcomes

A successful diagnosis gives stakeholders a shared structural explanation of recurrence. It reduces blame-only narratives, exposes why symptom fixes fail, points toward leverage points, and makes intervention monitoring more meaningful.

The broader outcome is transferable learning. Once a team recognizes a recurring feedback trap in one domain, it can detect similar structures elsewhere without assuming the local details are identical.

Tradeoffs

The archetype trades speed of recognition against risk of overmatching. A familiar archetype can rapidly orient action, but it can also become a premature label. It trades abstraction against context: abstraction reveals transferable structure, while context preserves the local facts that make intervention safe.

It also trades shared language against premature consensus. A name helps people coordinate, but the same name can close debate too early if alternatives and counterexamples are not preserved.

Failure Modes

A common failure mode is archetype overmatching: a team chooses a familiar pattern because it sounds right. Another failure mode is diagnostic labeling without intervention, where the team names the trap but never identifies leverage points. A third is boundary blindness, where the map excludes the actors, delays, or incentives that actually explain recurrence.

Other risks include linearized loop maps, blame relabeling, stale archetype libraries, and recipe-following from intervention playbooks. Each risk can be reduced by requiring fit evidence, counterexample checks, stakeholder review, and post-intervention monitoring.

Neighbor Distinctions

System Archetype Diagnosis is distinct from Archetype Pattern Indexing. Indexing creates or retrieves a pattern library; diagnosis applies a pattern to a current recurring situation.

It is distinct from Reusable Pattern Application. Pattern application uses a known solution pattern; diagnosis first determines which feedback structure is creating the problem.

It is distinct from Archetype Overmatching Guardrail. The guardrail prevents false matching; diagnosis produces a tested match. This draft includes counterexample checks, but the parent function is still diagnosis.

It is distinct from Feedback Loop Redirection and Leverage Point Intervention. Those are downstream actions that may follow once the diagnosis identifies which structure to change.

Cross-Domain Examples

In city transportation, repeated congestion relief through new road capacity can fail if added capacity induces more demand. In a service organization, emergency escalation can relieve visible backlog while delaying the capacity-building needed to prevent future backlog. In environmental governance, individually rational extraction can degrade a shared resource. In team coordination, defensive approval checks can reinforce distrust and slow work.

The common structure is not the domain. The common structure is a recurring feedback pattern that local fixes fail to change.

Non-Examples

A one-time installation error is not System Archetype Diagnosis unless it recurs through a feedback structure. A catalog of archetypes is not this archetype; that is pattern indexing. A causal diagram that documents a linear process is not this archetype. A consultant applying the same archetype label to every case without evidence is an overmatching failure, not a valid use.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (4)

• Archetype: Recurring pattern.
• Feedback: Outputs influence inputs.
• Leverage Points: High-impact intervention points.
• Pattern Recognition: Identify regularities.

Also references 7 related abstractions

• Abstraction: Focus on core elements.
• Causality: Cause-effect relationships.
• Mental Model: Internal system representation.
• Overfitting: Poor generalization.
• Representation: Model complex ideas.
• Sensemaking: Interpret ambiguous situations.
• Systemic Fragmentation: Siloed subsystems.

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Limits to Growth Diagnosis · subtype · recognized

Diagnoses situations where a reinforcing improvement or growth loop encounters a balancing constraint that slows or reverses progress.

• Distinct from parent: The parent is the general process of matching feedback structures to archetypes; this variant uses one named feedback pattern as the diagnostic lens.
• Use when: Growth, adoption, improvement, demand, or scaling initially accelerates and then stalls; Actors respond by pushing harder on the growth engine while the limiting constraint remains under-addressed.
• Typical domains: product adoption, public services, organizational growth, ecology
• Common mechanisms: limits to growth diagnosis, causal loop diagram, leverage point matrix

Shifting the Burden Diagnosis · subtype · recognized

Diagnoses situations where symptomatic relief crowds out or weakens fundamental corrective action.

• Distinct from parent: The parent includes any recognized feedback archetype; this variant focuses on symptomatic dependence and eroding fundamental capacity.
• Use when: A quick fix repeatedly relieves pressure while the underlying cause persists; Dependence on the symptomatic fix makes the fundamental solution less likely over time.
• Typical domains: health services, organizational learning, public policy, maintenance
• Common mechanisms: shifting the burden diagnosis, archetype fit checklist

Fixes That Fail Diagnosis · subtype · recognized

Diagnoses situations where a corrective action creates delayed side effects that recreate or worsen the original problem.

• Distinct from parent: The parent names the general diagnostic method; this variant examines one recurring failure pattern involving delayed side effects.
• Use when: A solution appears to work locally or immediately but the problem keeps returning; Delayed consequences of the fix are plausibly feeding the original symptom.
• Typical domains: policy, medicine, operations, finance
• Common mechanisms: fixes that fail diagnosis, causal loop diagram

Tragedy of the Commons Diagnosis · subtype · recognized

Diagnoses situations where individually rational use of a shared resource degrades collective availability or quality.

• Distinct from parent: The parent can diagnose many feedback traps; this variant focuses on shared-resource depletion or crowding.
• Use when: Multiple actors draw from or impose costs on a shared resource without sufficient shared governance; Individual incentives reward extraction while collective damage accumulates or is delayed.
• Typical domains: environment, team attention, shared infrastructure, public health
• Common mechanisms: tragedy of the commons diagnosis, leverage point matrix

Archetype-Based Intervention Playbook · implementation variant · promote to full archetype candidate

Uses a diagnosed system archetype to select pattern-specific intervention families instead of responding ad hoc to symptoms.

• Distinct from parent: System Archetype Diagnosis determines the pattern; the playbook variant operationalizes response selection after the pattern is identified.
• Use when: The diagnosis is already credible enough that actors need to choose interventions matched to the feedback structure; The same named archetype recurs across cases and benefits from a curated response repertoire.
• Typical domains: organizational change, public policy, operations, community planning
• Common mechanisms: leverage point matrix, archetype fit checklist, pattern diagnosis workshop

Near names: Feedback Pattern Diagnosis, System Dynamics Archetype Diagnosis, Archetype Mapping, Recurring Feedback Trap Diagnosis.

Editorial Notes

Problem Classification

Classification: Representation, Classification & Model Misfit → Model Assumption, Regulation & Residual Refinement

Problem kernel: a recurring feedback pattern is mis-modeled as isolated local events

Rationale: A recurring feedback structure is modeled as isolated events, personalities, or one-off shortages, so symptom interventions repeatedly fail while residual behavior persists. Hidden-state visibility explains why the pattern is hard to see, and relation modeling supplies useful structure, but the earliest defect is continued action under a linear local model whose assumptions do not fit the observed recurrence.

Boundary considered: Representation, Classification & Model Misfit → Relation, Interaction & Multicausal Structure

Why this classification prevailed: Model-assumption failure concerns persisting with a model contradicted by recurring residual behavior; relation modeling concerns whether direction, interaction, feedback, and multicausal pathways are represented at all.

Review outcome: Adjudicated after independent review; high confidence.