methodatlas
Method guideSystems Thinking

System Archetypes

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityHigh
Time90-180 min
Participants3-10
FormatWorkshop
MaturityCanonical
Plan System Archetypes
01

Prerequisite

What needs to be finished first

Complete firstBounded subject

The scope and purpose of System Archetypes are stated as a concrete question.

Without scope, archetype diagnosis becomes arbitrary.
Complete firstAccess to relevant perspectives

Behaviour over time, causal variables and delays, past interventions and domain decision makers are available.

Without these perspectives, central claims in archetype diagnosis remain unsupported.
02

Preparation

What needs to be ready before start

Materials

Behaviour over time, causal variables and delays, past interventions, shared workspace, source links, and decision log.

People / roles

System owner · domain actors · facilitator experienced in loops

Pre-read

Collect Behaviour over time, causal variables and delays, past interventions in advance and mark open assumptions.

Time needed

90 minutes

Setup

Prepare match behaviour over time to causal loops of a known archetype visibly and calibrate assessment terms before starting.

03

Core question

The one question this method answers

Which feedback archetype explains the pattern, and where can the structure change?

04

Flow

Phases with goal, actions, output and pitfall

Archetypes such as Fixes that Fail, Shifting the Burden, or Limits to Growth are hypotheses about loop structures. Observed behaviour must fit the archetype and use concrete variables.

archetype diagnosis

Fictional worked example

match behaviour over time to causal loops of a known archetype as a precise working structure with a fictional example.

archetype diagnosis
SubjectBehaviour patternArchetypeLoopsLeverage
archetype diagnosisWorked exampleBacklog falls briefly then rises higher.Shifting the Burden; alternative Fixes that Fail.Contractors reduce causal learning with delay.Cause feedback; share of recurring tickets.
  1. 1. Behaviour pattern

    archetype diagnosis
    Backlog falls briefly then rises higher.
  2. 2. Archetype

    archetype diagnosis
    Shifting the Burden; alternative Fixes that Fail.
  3. 3. Loops

    archetype diagnosis
    Contractors reduce causal learning with delay.
  4. 4. Leverage

    archetype diagnosis
    Cause feedback; share of recurring tickets.

The example demonstrates the domain logic of System Archetypes; worksheets remain blank.

The Systems Thinker: Systems Archetypes

  1. 1

    Plot pattern

    Plot pattern

    Goal

    Produce behaviour curves so the core question “Which feedback archetype explains the pattern, and where can the structure change?” can be answered with stronger support.

    Inputs for this step

    • Behaviour over time
    • causal variables and delays
    • past interventions

    Actions

    • Plot key variables as behaviour over time.
    • Record source, rationale, and open uncertainty directly in behaviour curves.

    Output

    behaviour curves

    behaviour curves · source · uncertainty · next decision

    Quality check

    Are horizon and measures consistent?

    Pitfall

    An archetype is chosen for a similar story without checking loops and behaviour over time. Operationalise variables, check loop polarities, and test at least one competing explanation.

    Timing: 10–20 minutes

  2. 2

    Select candidates

    Select candidates

    Goal

    Produce candidate comparison so the core question “Which feedback archetype explains the pattern, and where can the structure change?” can be answered with stronger support.

    Inputs for this step

    • behaviour curves
    • causal variables and delays
    • past interventions

    Actions

    • Compare two candidate archetypes by loop structure.
    • Record source, rationale, and open uncertainty directly in candidate comparison.

    Output

    candidate comparison

    candidate comparison · source · uncertainty · next decision

    Quality check

    Does every loop fit the real mechanism?

    Pitfall

    An archetype is chosen for a similar story without checking loops and behaviour over time. Operationalise variables, check loop polarities, and test at least one competing explanation.

    Timing: 10–20 minutes

  3. 3

    Validate loops

    Validate loops

    Goal

    Produce validated loop map so the core question “Which feedback archetype explains the pattern, and where can the structure change?” can be answered with stronger support.

    Inputs for this step

    • candidate comparison
    • causal variables and delays
    • past interventions

    Actions

    • Validate polarity, delay, and evidence with actors.
    • Record source, rationale, and open uncertainty directly in validated loop map.

    Output

    validated loop map

    validated loop map · source · uncertainty · next decision

    Quality check

    Does the structure explain the time pattern?

    Pitfall

    An archetype is chosen for a similar story without checking loops and behaviour over time. Operationalise variables, check loop polarities, and test at least one competing explanation.

    Timing: 10–20 minutes

  4. 4

    Change structure

    Change structure

    Goal

    Produce intervention hypothesis so the core question “Which feedback archetype explains the pattern, and where can the structure change?” can be answered with stronger support.

    Inputs for this step

    • validated loop map
    • causal variables and delays
    • past interventions

    Actions

    • Design a fundamental intervention and leading indicator.
    • Record source, rationale, and open uncertainty directly in intervention hypothesis.

    Output

    intervention hypothesis

    intervention hypothesis · source · uncertainty · next decision

    Quality check

    Does the action target the loop rather than the symptom?

    Pitfall

    An archetype is chosen for a similar story without checking loops and behaviour over time. Operationalise variables, check loop polarities, and test at least one competing explanation.

    Timing: 10–20 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

System Archetypes · wiederkehrende Systemmuster erkennenBeobachtete Symptome mit Archetypen vergleichen, Loop-Struktur skizzieren und passende Hebel ableiten
System ArchetypesDas Visual zeigt eine wiederkehrende Beobachtung, passende Archetypenkarten, eine Loop-Struktur und daraus abgeleitete Hebel.Wiederkehrende Dynamiken als Muster erkennenSystem Archetypes übersetzen Symptome in bekannte Loop-Strukturen mit typischen Hebeln.BeobachtungSymptom kehrt trotz MaßnahmenwiederLimits to GrowthWachstum trifft BegrenzungFixes that FailLösung erzeugt NebenfolgeShifting BurdenSymptomlösung verdrängt Ursacheausgewählter ArchetypSymptomQuick FixUrsache+ kurzfristigDelay-HebelUrsache adressieren, Delay sichtbarmachenMustervergleichenLoop und Verzögerungzeichnennicht beim Symptomstoppen
Form

Versioned archetype diagnosis with date, sources, owners, and next review.

Versioning / ownership

Retain date, source, assumption state, and decision for every version of archetype diagnosis.

Tool alternatives
  • archetype diagnosis as board or document
  • Source and evidence register
  • Decision and action log

system-archetypes-working-template.md

Plan System Archetypes around its domain steps and the concrete decision question.

System Archetypes: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Full workshop Time: 90 minutes

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Behaviour over time, causal variables and delays, past interventions, shared workspace, source links, and decision log.
  • Roles: System owner · domain actors · facilitator experienced in loops
  • Advance information: Collect Behaviour over time, causal variables and delays, past interventions in advance and mark open assumptions.
  • Overall time needed: 90 minutes
  • Setup: Prepare match behaviour over time to causal loops of a known archetype visibly and calibrate assessment terms before starting.

Prepare for the work steps

Plot pattern: Plot pattern

  • Behaviour over time
  • causal variables and delays
  • past interventions

Select candidates: Select candidates

  • behaviour curves
  • causal variables and delays
  • past interventions

Validate loops: Validate loops

  • candidate comparison
  • causal variables and delays
  • past interventions

Change structure: Change structure

  • validated loop map
  • causal variables and delays
  • past interventions

archetype diagnosis

SubjectVariable · curve · horizonName · matching structure · alternativeVariables · polarity · delayStructural change · indicator
archetype diagnosis
  • archetype diagnosis: Worked example

Enter only real input, sources, and decisions.

The Systems Thinker: Systems Archetypes

Plot pattern: Plot pattern

Expected artifact: behaviour curves

behaviour curves · source · uncertainty · next decision

Entry:

...

  • Are horizon and measures consistent?

Select candidates: Select candidates

Expected artifact: candidate comparison

candidate comparison · source · uncertainty · next decision

Entry:

...

  • Does every loop fit the real mechanism?

Validate loops: Validate loops

Expected artifact: validated loop map

validated loop map · source · uncertainty · next decision

Entry:

...

  • Does the structure explain the time pattern?

Change structure: Change structure

Expected artifact: intervention hypothesis

intervention hypothesis · source · uncertainty · next decision

Entry:

...

  • Does the action target the loop rather than the symptom?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/system-archetypes/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

system-archetypes-beispiel.md

Concrete filled scenario, fictional example

Archetype: Shifting the Burden. Symptomatic solution: contractors reduce backlog temporarily. Fundamental solution: remove product causes. Side effect: Product receives less causal knowledge, weakening the fundamental solution. Leverage: cause feedback and dedicated engineering capacity.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Plot patternAn archetype is chosen for a similar story without checking loops and behaviour over time.View in phase
  2. Select candidatesAn archetype is chosen for a similar story without checking loops and behaviour over time.View in phase
  3. Validate loopsAn archetype is chosen for a similar story without checking loops and behaviour over time.View in phase
  4. Change structureAn archetype is chosen for a similar story without checking loops and behaviour over time.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

archetype diagnosis answers the core question with traceable evidence or explicitly marked uncertainty.
Owners, next actions, and review dates are named for open points.

Method after Systems Thinking Community. The method comes from systems thinking, system dynamics, or adjacent organizational practice. Curated with 1 sources.

Sources: The Systems Thinker: Systems Archetypes

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.