In one line: What we see (events) sits on top of patterns, which are produced by structures, which are shaped by mental models. Lasting change works below the waterline.
Core idea
The iceberg model is a simple heuristic from systems thinking. Like an iceberg, with only a small part of its mass above water, a situation shows us only its events. Most of what generates them is hidden. The model asks us to step back from the event and look at the deeper levels that produce it.
flowchart TB E["Events<br/>what just happened? (react)"] --> P["Patterns and trends<br/>what has been happening over time? (anticipate)"] P --> S["Structures<br/>what causes the pattern? rules, incentives, flows, relationships (design)"] S --> M["Mental models<br/>what beliefs and assumptions keep the structure in place? (transform)"]
How it works
- Events: the visible incident, such as a missed deadline, a failed test, or a resignation. Responding here is reactive.
- Patterns: the same kind of event recurring, which you see by looking back over time. Responding here lets you anticipate.
- Structures: what produces the pattern: processes, incentives, organization, physical layout, information flows, feedback loops. Changing these is redesign.
- Mental models: the beliefs, values and assumptions that created the structures and keep them in place. Changing these is transformation, and it is the deepest and hardest form of change.
The levels map neatly onto other frameworks in this vault:
- Schein’s Levels of Culture (artifacts, espoused values, assumptions)
- Meadows’s Leverage Points, where paradigms are the strongest
- the way trust and Psychological Safety sit beneath visible team behavior
In practice
Applied to a recurring problem, such as the same kind of defect escaping test on every program, the model moves the conversation from blame (who missed it?) to patterns (this happens near every deadline), to structure (test time is what gets cut when schedules slip), to mental models (we believe schedule is visible and quality isn’t). Each level down offers more leverage and demands more courage.
Questions to ask yourself
- Which recent event am I treating as a one-off that is really part of a pattern?
- What structure keeps producing that pattern?
- Which shared assumption keeps the structure in place?
Connections
- Systems foundation: Thinking in Systems. Drawing the structure: Causal Loop Diagrams.
- Parallels: Levels of Culture, Logic of Appropriateness, Psychological Safety.
- Capabilities exercised: Inquiry, Vision.
Sources
- Course handout on the iceberg model of systems thinking; no public source.
- Meadows (2008) Thinking in Systems [1]