Iceberg Model
The Iceberg Model says the event you can see is the smallest part of the problem - underneath it sit a repeating pattern, the structure that sustains that pattern, and the mental models that hold the structure in place.
Only the tip shows above the waterline, with pattern, structure and mental models stacked beneath it in that order.
Reach for this when…
- The same problem keeps recurring and fixing the latest instance never sticks.
- A team treats each incident as a one-off when it is clearly a pattern.
- You need to find the real leverage point, not just react to today's fire.
How to run it
- Name the visible event or problem.
- Ask what pattern of behaviour produces this event repeatedly.
- Ask what structure - incentives, flows, feedback loops - sustains that pattern.
- Ask what assumptions or beliefs underpin the structure.
- Identify the leverage point at the structural or mental-model level, not the event level.
A worked example
Situation. Lucia Fernandez ran a freight and warehousing firm in Montevideo, Uruguay, where late deliveries kept triggering fresh apologies to clients and fresh rotas, with no lasting fix.
Applied. Working down the iceberg, she traced the pattern (drivers routinely overloaded on Fridays) to a structure (a bonus scheme that rewarded number of loads, not on-time delivery) and the belief underneath it ('busy trucks are working trucks').
Result. She changed the bonus metric to on-time delivery. Friday overloading stopped within a month, without a single new rota.
The catch
The model is only as good as the honesty of the questions. Groups default to blaming the event or the person and stop before they reach structure, because structure often implicates the people running the meeting. It also assumes you can find one dominant pattern, when messy real situations often have several running at once.
If your action plan only addresses the event, you have described the iceberg without diving under it.
Origin: Systems thinking tradition (Donella Meadows, Peter Senge)