Session Brief: System Archetypes

Goal

Artifact: Archetyp-Zuordnung

Working Question

Which archetype best explains recurring symptoms, and which levers are typical for this archetype?

Context

Current observations with data (for example trend charts); known past solution attempts with result; Iceberg Model analysis if available; archetype cards as pre-read.

Setup

• Format: Method session
• Duration: 90-180 min
• Mode: Workshop
• Participants: One facilitator experienced in systems thinking; 3-10 participants with context on problem; scribe for levers and actions; optional coach for archetype deepening.
• Owner: One facilitator experienced in systems thinking
• Participation mode: Team round, shared work and alignment
• Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Archetyp-Zuordnung. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with archetype cards (Limits to Growth, Shifting the Burden, Tragedy of the Commons, Fixes that Fail, Success to the Successful, Drifting Goals, Escalation, Growth and Underinvestment); current observations or symptoms; Senge/Meadows reference; pens.

Preparation

Archetype cards on wall with short loop sketch and example. Section for observations. Section for identified archetype. Section for levers and actions. Rule: check several archetypes, do not latch onto first.

Agenda

1. Phase 1: Formulate observations (20-30 min) Owner: Facilitator Action: List concrete recurring symptoms. Data or evidence per symptom. Past solution attempts and their effect. Goal: at least 5 observations with timeline. Hint: Symptoms without data are anecdotal. Anyone without data is in speculation mode, not observation mode. First data, then archetype. Output: Archetyp-Zuordnung

2. Phase 2: Introduce archetype cards (20-30 min) Owner: Facilitator Action: Explain loop structure per archetype with example. Limits to Growth: growth creates own limit. Shifting the Burden: symptom solution weakens fundamental solution. Fixes that Fail: quick fix reinforces problem long-term. Etc. Hint: Every archetype has characteristic loop structure. If you cannot draw loops, you did not understand archetype. Sketch per archetype on wall. Output: Hebel-Liste

3. Phase 3: Check possible archetypes (30-40 min) Owner: Facilitator Action: Compare observations with 2-3 archetype candidates. Per candidate check: do loops fit, do delays fit, does it explain past solution attempts. Hint: Several archetypes are often active at once. Do not latch on early. Whoever chooses first plausible one often misses dominant one. Output: Archetyp-Zuordnung

4. Phase 4: Draw loops and delays (30-45 min) Owner: Facilitator Action: Draw chosen archetype explicitly for our case. Variables with real labels (for example "number of support tickets", "engineering capacity"). Mark delays. Hint: Generic archetype becomes concrete diagram. Delays are often key: quick effect short-term, counterintuitive effect long-term. Output: Hebel-Liste

5. Phase 5: Levers and actions (30-45 min) Owner: Owner Action: Typical levers per archetype (for example Shifting the Burden: strengthen fundamental solution, do not scale symptom solution). Actions with owner and deadline. Hint: Archetypes have textbook levers. If levers are ignored and symptom actions proposed instead, the archetype continues. Textbook levers as default. Output: Archetyp-Zuordnung

6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Archetyp-Zuordnung

Closeout

• Update result artifact: Archetyp-Zuordnung
• Define location, version, and review recipients.
• Define owner, next step, and review date.

Archetyp-Zuordnung: System Archetypes

Working Question

Which archetype best explains recurring symptoms, and which levers are typical for this archetype?

Context

Current observations with data (for example trend charts); known past solution attempts with result; Iceberg Model analysis if available; archetype cards as pre-read.

Participants

• Owner: One facilitator experienced in systems thinking
• Participants: One facilitator experienced in systems thinking; 3-10 participants with context on problem; scribe for levers and actions; optional coach for archetype deepening.

Input

Whiteboard or Miro board with archetype cards (Limits to Growth, Shifting the Burden, Tragedy of the Commons, Fixes that Fail, Success to the Successful, Drifting Goals, Escalation, Growth and Underinvestment); current observations or symptoms; Senge/Meadows reference; pens.

Template

System Archetypes Working Template

Goal

Standard patterns of recurring system dynamics such as Limits to Growth.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

• Archetype mapping:
• Leverage list:

Assumptions and open questions

• ...

Decision / next step

Owner, date, and success signal.

Completion Check

• Archetyp-Zuordnung is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

• Review result
• Mark open questions
• Schedule review or decision