The Iceberg Model is a systems thinking tool that helps uncover the root causes of problems by looking beyond immediate, visible events. It uses the metaphor of an iceberg to illustrate that events (the tip) are driven by deeper layers that are hidden below the surface.
In UX design, it means that instead of merely tackling immediate issues with short-term fixes, we should research and solve the underlying causes for long-term solutions.
ORIGIN
The Iceberg Model comes from systems thinking which is a field dedicated to explaining why everything is more complicated than it looks. It uses the simple metaphor of an iceberg, where only a tiny portion, the tip, is visible above water, while the complexity of the whole system lurks beneath the water line – quietly ruining your roadmap.
UX designers adopted the iceberg model after collectively realizing that “The problem we fixed yesterday is back. And now it brought friends.”
WHEN
Use the Iceberg Model when:
- You’ve “fixed” the same issue three times (and it’s still not fixed)
- Stakeholders say things like: “Can we just make the button bigger?”
- Your backlog feels like a graveyard of recurring problems
- You sense something deeper is wrong, but no one wants to talk about it
If your team is winning small battles but losing the war then you’re probably only staring at the tip of the iceberg.
WHY
What is visible to the eyes is rarely the real problem.
The Iceberg Model breaks problems into four levels:
- Events: “Something is off, I can see it, and I think there is an easy fix to it”
- Patterns: “Whatever I try, it keeps breaking”
- Structures: “This system is questionable, we should dig deeper”
- Mental Models: “Ah. Now I understand, that’s why we’re like this”
Most teams live at the event level, applying quick fixes like duct tape on a sinking ship. The real journey begins when you go deeper – and it’s a challenging journey because the problems are harder to see and harder to fix. Changes are harder to implement and the burden of explaining it to stakeholders is now on you. But, it’s the only way to get to the bottom of a problem and truly resolve it.
HOW
The recipe for fixing superficial problems sound easy: Start at the surface. Then resist the urge to stop there.
In reality, it’s a multi-step process where you’ll go through the following planes of the iceberg:
- Event (the tip): We are seeing an issue. Panic. Add a small fix. Ship. Celebrate.
- Patterns (below the surface): We start seeing a pattern behind the issue. It’s not just random chaos anymore.
- Structures (the system): What’s causing this pattern? Design meets reality. Reality is messy.
- Mental Models (the deep end): What beliefs created this system? Congrats, you’ve reached the bottom. It’s dark here. And slightly political.
Designers need to know that taking shortcuts may be fast, visible, and feel productive. But fixing structures and following mental models is the bread and butter of our jobs. It’s hard, requires effort and courage, and sometimes forces you to attend a meeting you don’t want to be part of. At the end of it, this work separates the good from the great.
PRO TIP
If your solution is: “Let’s tweak the UI”, then you’re most likely decorating the iceberg.
Instead, ask: “Why does this iceberg exist in the first place?”
(Warning: this may lead to existential product discussions.)
EXAMPLES
Example 1: The “Bad Button”
- Event: Nobody clicks it
- Pattern: Nobody clicks any buttons
- Structure: Too many competing actions
- Mental Model: “Let’s give users options!”
Fix: Remove 80% of the options. Pretend it was intentional.
Example 2: The “Confusing Map”
- Event: Users get lost
- Pattern: Zoom. Pan. Zoom. Panic. Repeat.
- Structure: Every layer is visible. At all times. Why not.
- Mental Model: “More data = more value”
Fix: Turns out, clarity is more valuable than everything everywhere all at once.
Example 3: The “Feature Nobody Uses”
- Event: Zero engagement
- Pattern: Also zero engagement on the last three features
- Structure: Hidden in a menu inside a menu inside a menu
- Mental Model: “Users will explore!”
Fix: Users do not explore. Users survive.
CONCLUSION
The Iceberg Model teaches us a simple truth: The problem you see is just the part that’s convenient to fix.
Everything else – the systems, the decisions, the beliefs – is sitting quietly below the surface, shaping your product like a mischievous sea monster.
Great designers don’t just fix what’s visible. They dive deeper, ask uncomfortable questions, and occasionally ruin a perfectly good meeting with: “But why are we doing it this way?”
