The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring.
Systems Thinking Analysis method
Iceberg Model
Moves from a concrete event through evidenced patterns to possible system structures and assumptions.
The Iceberg Model moves from a concrete event through evidenced patterns to possible system structures and assumptions.
Which conditions produce a recurring pattern, and which assumption keeps it in place?
- Participants
- 2-10
- Time
- 30–60 minutes for an initial group analysis; data review and intervention are separate.
Which conditions produce a recurring pattern, and which assumption keeps it in place?

Event
Observe a specific event
Describe a visible occurrence, when it happened, context and source without asserting a cause.
Patterns
Check patterns over time
Compare periods, distributions and counterexamples; state what recurs and what remains uncertain.
Structure
Investigate possible structures
Examine rules, incentives, resources, processes and relationships; distinguish findings from hypotheses.
Assumptions
Test assumptions and interventions
Ask which beliefs or goals sustain the structure; choose a bounded intervention and observation signal.
Update the work record when new evidence, changed constraints or the planned review changes an assumption.
A good fit when
Useful for recurring problems with multiple plausible causes and access to different perspectives. For an acute isolated incident, begin with incident analysis.
Ideal for
- Root-cause Exploration
- Organizational Change
- Leadership Reflection
Not good for
- Quantitative simulation
- Simple one-step fixes
Outputs

Shared, verifiable starting point
Description of a visible occurrence, when it happened, context and source without asserting a cause.

Evidenced or explicitly tentative trend
Comparison of periods, distributions, and counterexamples, with recurring and uncertain elements marked.

Structural hypotheses and evidence needs
Examination of rules, incentives, resources, processes, and relationships that may generate the pattern, with findings separated from hypotheses.

Intervention hypothesis with feedback
Beliefs or goals that sustain the structure, together with a bounded intervention and observation signal.
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.
First step
Choose an event and record source, period and system boundary.
Good to do first
Deep dive
Starting from concrete events or symptoms, the questioning goes deeper layer by layer. Patterns, structures, and mental models are separated from each other so it becomes clear at which level an intervention actually needs to start.
The Iceberg Model helps because it distinguishes between events, patterns, structures, and mental models, slowing down premature reaction to symptoms. Good use forces the team to work beneath the visible surface and fill every layer with observations or plausible mechanisms. This clarifies which deeper assumptions or structures carry a recurring problem and why mere reaction to events rarely suffices.
Start with a concrete visible event that evokes the same memory for everyone, then deliberately work one layer deeper. The decision gains substance once a pattern can no longer be explained by individual mistakes and structure becomes visible instead. Close with a shared reading of the deepest relevant layer and the points where further evidence is missing.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Iceberg Model: WorksheetPlan a session or initiative to match the actual scope of work.markdown
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
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.

Instead of Iceberg Model, when you want to make feedback loops, delays, and reinforcing loops in the system visible.

Traces developments over time and reveals turning points, patterns, and possible causes of a trend.

Moves relationships, patterns, and leverage toward a concrete result through "formulate current observations", "introduce archetype cards", and "discuss leverage and derive actions".

Makes an unclear problem situation visible with actors, tensions, and flows before premature solutions emerge.

Models stocks, inflows and outflows, and delays to understand dynamics, bottlenecks, and capacity.

Clarifies connections, patterns, and leverage points by collecting undesirable effects, formulating causal links, and deriving interventions.
Constraints and origin
Profile
- Method form
- Analysis method
- Participants
- 2-10
- Time
- 30-60 min
- Maturity
- Established
- Origin
- Systems Thinking Community


