methodatlas
Method guideSystems Thinking

Iceberg Model

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

ComplexityLow
Time30-60 min
Participants2-10
FormatWorkshop + async
MaturityEstablished
Plan the work
01

Prerequisite

What needs to be finished first

Complete firstClear working frame

Choose an event and record source, period and system boundary.

Without a bounded question or checkable evidence, the result will be unclear.
02

Preparation

What needs to be ready before start

Materials

Event evidence, time-series data where available, affected perspectives and a shared worksheet.

People / roles

Facilitator · affected domain roles · data owner; separate hypotheses from findings.

Pre-read

Choose materials, data access and participants to fit the research or decision question.

Time needed

30–60 minutes for an initial group analysis; data review and intervention are separate.

Setup

Open the method-specific structure. Fictional examples are for orientation only; keep the blank worksheet separate from actual findings.

03

Core question

The one question this method answers

Which conditions produce a recurring pattern, and which assumption keeps it in place?

04

Flow

Phases with goal, actions, output and pitfall

The Iceberg Model moves from a concrete event through evidenced patterns to possible system structures and assumptions.

Iceberg Model working record

Fictional example

The iceberg is a discussion frame; keep observations and causal hypotheses distinct.

Events

What happened, when, and according to which source?

18 late callbacks reported on a fictional Monday; the report covers one day.

Patterns

What is recurring across a stated period?

A fictional sample suggests post-holiday delays; data completeness needs checking.

System structures

Which rules, resources or relationships might produce the pattern?

Callback batching with unchanged staffing is a hypothesis to verify.

Mental models

Which belief or goal may sustain the structure?

“We can catch up tomorrow” is an assumption to examine, not a fact.

The iceberg is a discussion frame; keep observations and causal hypotheses distinct.

Introduction to Systems Thinking

  1. 1

    Event

    Observe a specific event

    Goal

    Record the event, date and source; separate observation from interpretation.

    Inputs for this step

    • Choose an event and record source, period and system boundary.
    • Event evidence, time-series data where available, affected perspectives and a shared worksheet.

    Actions

    • Describe a visible occurrence, when it happened, context and source without asserting a cause.
    • Record Shared, verifiable starting point with its evidence status, source or open verification need.

    Output

    Shared, verifiable starting point

    Shared, verifiable starting point

    Quality check

    Is direct observation separate from interpretation?

    Pitfall

    One incident is generalized into a rule. Add date, case and source; list interpretations separately.

    Timing: About 10–20 minutes; schedule data or clarification work separately.

  2. 2

    Patterns

    Check patterns over time

    Goal

    Describe a recurring trend only when the data support it.

    Inputs for this step

    • Shared, verifiable starting point
    • Event evidence, time-series data where available, affected perspectives and a shared worksheet.

    Actions

    • Compare periods, distributions and counterexamples; state what recurs and what remains uncertain.
    • Record Evidenced or explicitly tentative trend with its evidence status, source or open verification need.

    Output

    Evidenced or explicitly tentative trend

    Evidenced or explicitly tentative trend

    Quality check

    Does the evidence support a pattern claim?

    Pitfall

    A striking case is treated as a trend. Check population, comparison period and counterexamples.

    Timing: About 10–20 minutes; schedule data or clarification work separately.

  3. 3

    Structure

    Investigate possible structures

    Goal

    List plausible mechanisms with evidence gaps.

    Inputs for this step

    • Evidenced or explicitly tentative trend
    • Event evidence, time-series data where available, affected perspectives and a shared worksheet.

    Actions

    • Examine rules, incentives, resources, processes and relationships; distinguish findings from hypotheses.
    • Record Structural hypotheses and evidence needs with its evidence status, source or open verification need.

    Output

    Structural hypotheses and evidence needs

    Structural hypotheses and evidence needs

    Quality check

    Are mechanism and evidence status visible?

    Pitfall

    A plausible explanation is called proven. Add sources and counter-hypotheses; involve affected roles.

    Timing: About 10–20 minutes; schedule data or clarification work separately.

  4. 4

    Assumptions

    Test assumptions and interventions

    Goal

    Agree an intervention hypothesis and review signal.

    Inputs for this step

    • Structural hypotheses and evidence needs
    • Event evidence, time-series data where available, affected perspectives and a shared worksheet.

    Actions

    • Ask which beliefs or goals sustain the structure; choose a bounded intervention and observation signal.
    • Record Intervention hypothesis with feedback with its evidence status, source or open verification need.

    Output

    Intervention hypothesis with feedback

    Intervention hypothesis with feedback

    Quality check

    Is there a signal and review date?

    Pitfall

    The model is used to assign blame or rush a redesign. Involve affected people and track consequences.

    Timing: About 10–20 minutes; schedule data or clarification work separately.

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Iceberg Model · Systems ThinkingThink from visible events through patterns and structures to mental models below the surface
Iceberg ModelThe visual shows visible events above the waterline and, underneath, patterns, structures, and mental models.Look from the event to deeper system causesVisible incidents are only the tip; effective change happens deeper in the system.visiblebelow the surfaceEventsWhat happened?PatternsWhat repeats?StructuresWhich rules, incentives, or processes create the pattern?Mental ModelsWhich beliefs keep the structure stable?reactanticipateshape
Form

Versioned record of question, evidence, result, uncertainty, owners and next review date.

Versioning / ownership

Track date, scope, sources, assumptions and changes; assign an owner and review for ongoing practice or initiatives.

Tool alternatives
  • Paper and pens
  • Whiteboard or simple table

iceberg-model-working-template.md

Plan a session or initiative to match the actual scope of work.

Iceberg Model: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Prepare the full method Time: 30–60 minutes for an initial group analysis; data review and intervention are separate.

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

Preparation for this scope

Method setup

  • Materials: Event evidence, time-series data where available, affected perspectives and a shared worksheet.
  • Roles: Facilitator · affected domain roles · data owner; separate hypotheses from findings.
  • Advance information: Choose materials, data access and participants to fit the research or decision question.
  • Overall time needed: 30–60 minutes for an initial group analysis; data review and intervention are separate.
  • Setup: Open the method-specific structure. Fictional examples are for orientation only; keep the blank worksheet separate from actual findings.

Prepare for the work steps

Event: Observe a specific event

  • Choose an event and record source, period and system boundary.
  • Event evidence, time-series data where available, affected perspectives and a shared worksheet.

Patterns: Check patterns over time

  • Shared, verifiable starting point
  • Event evidence, time-series data where available, affected perspectives and a shared worksheet.

Structure: Investigate possible structures

  • Evidenced or explicitly tentative trend
  • Event evidence, time-series data where available, affected perspectives and a shared worksheet.

Assumptions: Test assumptions and interventions

  • Structural hypotheses and evidence needs
  • Event evidence, time-series data where available, affected perspectives and a shared worksheet.

Iceberg Model working record

Events

What happened, when, and according to which source?

...

Patterns

What is recurring across a stated period?

...

System structures

Which rules, resources or relationships might produce the pattern?

...

Mental models

Which belief or goal may sustain the structure?

...

Blank worksheet: prompts only; do not copy example data.

Introduction to Systems Thinking

Event: Observe a specific event

Expected artifact: Shared, verifiable starting point

Shared, verifiable starting point

Entry:

...

  • Is direct observation separate from interpretation?

Patterns: Check patterns over time

Expected artifact: Evidenced or explicitly tentative trend

Evidenced or explicitly tentative trend

Entry:

...

  • Does the evidence support a pattern claim?

Structure: Investigate possible structures

Expected artifact: Structural hypotheses and evidence needs

Structural hypotheses and evidence needs

Entry:

...

  • Are mechanism and evidence status visible?

Assumptions: Test assumptions and interventions

Expected artifact: Intervention hypothesis with feedback

Intervention hypothesis with feedback

Entry:

...

  • Is there a signal and review date?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/iceberg-model/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.

iceberg-model-beispiel.md

Concrete filled scenario, fictional example

Fictional example: callback service

Event: A team reports 18 late callbacks on Monday; this single report does not establish a cause.

Pattern hypothesis: A sample analysis suggests delays after holidays; completeness and period need checking.

Structure hypothesis: Callback tasks may be batched after holidays while staffing stays constant. Check roster and assignment rules.

Assumption: “We can clear the backlog the next day” is a hypothesis, not an established team belief.

Intervention: Trial triage before a holiday, then review callback age, backlog and team effort across comparable periods.

07

Pitfalls

Recognize symptoms and steer against them

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

  1. Observe a specific eventOne incident is generalized into a rule.View in phase
  2. Check patterns over timeA striking case is treated as a trend.View in phase
  3. Investigate possible structuresA plausible explanation is called proven.View in phase
  4. Test assumptions and interventionsThe model is used to assign blame or rush a redesign.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Without time-based evidence, do not claim a pattern. If participants cannot speak safely or ownership is unclear, arrange protected inquiry and facilitation first.

Where to go next?

Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points

Searches the suspected structure for effective points of leverage.

Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping

Delineates the system in which the found structure operates.

View in playbookUnderstand a Systemic Problem and Find LeverageMove from a recurring symptom to the underlying system structure and a concrete leverage point.

Finished the method guide?

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

Go to profileMore methods