System Archetype Diagnosis¶
Match a recurring feedback pattern to a known system archetype so the likely failure mode and intervention family become visible.
The Diagnostic Story¶
Symptom: The same problem keeps returning after apparently reasonable fixes. Different stakeholders describe separate symptoms — firefighting cycles, stalled growth, escalating conflicts, degraded shared resources — that feel unrelated but are connected through delays, incentive loops, or shared constraints nobody has mapped. Each occurrence is treated as a local event or a personnel problem, so interventions target symptoms and the underlying pattern regenerates.
Pivot: Convert recurring symptoms into a tested feedback diagnosis: map the causal loops, compare them with known archetype templates, validate fit against observable behavior and time dynamics, then select leverage points and intervention families that target the feedback structure rather than the most visible symptom.
Resolution: Actors recognize the pattern as structural and recurring rather than as a fresh surprise. Intervention choices become matched to the actual feedback structure, delays, and incentives rather than to blame or surface events. The causal model becomes explicit and arguable, and monitoring can track whether the diagnosed pattern is weakening.
Reach for this when you hear…¶
[management consulting] “Every time we push on this it gets better for six months and then comes back worse — that is not a motivation problem, that is a balancing loop with a delay and we need to find the constraint.”
[public health policy] “We keep treating the presenting cases but the incidence rate is not falling because the feedback driving exposure has not changed.”
[software engineering] “Tech debt keeps accumulating because every sprint the urgent work crowds out the structural work — that is fixes that fail by design, not a prioritization failure.”
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.
Show the applicability expression
Applicability expression6 distinct conditions
groundedpartly groundedopen
6 conditions, all required.
6Required in every casenumbered 1–6
These hold no matter which pattern applies.
Recurring failed fixes · grounded
The same problem recurs after apparently reasonable fixes.
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. The narrower requirement in this condition set is: The same problem recurs after apparently reasonable fixes.
Connected stakeholder symptoms · grounded
Different stakeholders describe separate symptoms that appear connected through delay, incentive, resource, or dependency loops.
Their response changes incentives, capacity, trust, delay, resource availability, or expectations. The narrower requirement in this condition set is: Different stakeholders describe separate symptoms that appear connected through delay, incentive, resource, or dependency loops.
Whole-harming local optimization · grounded
Local optimization improves one part of the system while worsening the whole.
This is a load-bearing situation condition in the diagnostic expression. The condition is: Local optimization improves one part of the system while worsening the whole. If it does not hold, this particular condition set is incomplete.
Delayed relief reversal · grounded
Short-term relief is followed by delayed deterioration, relapse, escalation, or renewed constraint.
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. The narrower requirement in this condition set is: Short-term relief is followed by delayed deterioration, relapse, escalation, or renewed constraint.
Fragmented loop visibility · grounded
Actors disagree about causes because each sees only one segment of a circular causal structure.
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. The narrower requirement in this condition set is: Actors disagree about causes because each sees only one segment of a circular causal structure.
Recognizable system archetype · grounded
The system has enough recurring structure to compare against known archetypes rather than requiring a novel causal model from scratch.
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. The narrower requirement in this condition set is: The system has enough recurring structure to compare against known archetypes rather than requiring a novel causal model from scratch.
Coverage
6 of 6 conditions grounded.
Mechanisms / Implementations¶
- 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.
- 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.
- 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.
- Named Archetype Diagnoses: Limits-to-growth, shifting-the-burden, fixes-that-fail, tragedy-of-the-commons, escalation, and success-to-the-successful diagnoses are mechanism families under the parent pattern.
- 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.
- Archetype Fit Checklist: Tests a proposed system-archetype match against its evidence and its strongest rival before the label is allowed to guide action.
- 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.
- 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.
- 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.
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.
Shifting the Burden Diagnosis · subtype · recognized
Diagnoses situations where symptomatic relief crowds out or weakens fundamental corrective action.
Fixes That Fail Diagnosis · subtype · recognized
Diagnoses situations where a corrective action creates delayed side effects that recreate or worsen the original problem.
Tragedy of the Commons Diagnosis · subtype · recognized
Diagnoses situations where individually rational use of a shared resource degrades collective availability or quality.
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.
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.