The Transformation Iceberg

Most change programmes fail quietly. The workshop happens, the deck circulates, everyone agrees — and six weeks later the organisation is doing exactly what it did before. Nobody resisted. It simply did not stick.

The Transformation Iceberg explains why, and it gives you somewhere specific to look.

Adapted from systems thinking, it describes how much change an organisation can sustain based on which level is actually being changed. At the top sit the visible outcomes of daily activity: better performance, more revenue, happier customers. Below the surface sit the layers that make those outcomes possible — and the deeper the level of the shift, the more durable the change.

The layers

Activities — what we do. The visible tip. Tasks, projects, initiatives, the things that show up in a status report. This is the only layer most change programmes touch.

Patterns, trends and behaviours — over time. What keeps happening. Not the one late delivery but the fact that delivery is always late; not the one difficult meeting but the fact that decisions never close. Patterns are visible if you look across time rather than at today.

Skills and systems — organisation structures and practices. What the organisation is actually able to do, and what it does consistently without anyone remembering to. Rarely seen, because systems are invisible when they work.

Values and character — worldview, mindsets, principles and beliefs. The mental models that shape how leaders and teams think about the work. Almost never discussed directly, and the layer that decides whether anything above it holds.

The rule the iceberg makes plain: the depth of the shift determines the durability of the change. Change an activity and you change this quarter. Change a belief and you change what the organisation does when nobody is watching.

Practices are the link

Between daily activity and embedded systems sit practices — the patterns, habits and behaviours people carry out in their work. Practices are shaped by culture and values, and they in turn shape the skills and systems the organisation relies on. The influence runs both ways.

This is why systems alone do not deliver outcomes. Suppose you want to improve customer service. You may well need new systems: faster response times, better tracking of issues, more effective communication. None of it lands unless people adopt new practices — prioritising service, using the new system consistently, actually seeking feedback. If they are resistant, or they lack the skills or the resources, the system will not produce the outcome. It will produce a dashboard.

The examples in the book are all practices protected by systems. Coke turns its recipe into a syrup and ships it to bottlers worldwide — a practice defended by a system, holding the taste identical in every market for a century. IKEA's flat pack, Apple's launch rhythm, Qantas's safety announcement: each is a behaviour made inevitable by structure.

Which practices in your business have been systemised, and which are still riding on one person's discipline?

Diagnosing a change that did not stick

Work downward, and stop at the first layer nobody touched.

1. Name what was supposed to change, at the activity level. What were people going to do differently?
2. Ask what pattern that activity had to break. If the new activity contradicts an established pattern, the pattern usually wins.
3. Ask which skill or system had to exist for it to be possible. People rarely refuse to do the possible; they quietly abandon the impossible.
4. Ask what the organisation would have had to believe for the change to make sense. This is the layer the answer is usually at.

A change programme that addressed only layer one was never a change programme. It was an announcement.

Designing change that holds

The same structure read upward becomes a design tool. Decide how durable the change needs to be, then work at that depth deliberately:

• A quarter's improvement — activities and patterns will carry it.
• A capability the business keeps — it has to reach skills and systems, or it leaves when the person does.
• A change in what the company is — it has to reach values and character, and that is slow, explicit work.

The mistake is not choosing a shallow layer. The mistake is choosing a shallow layer and expecting a deep result.

The questions to ask at each level

• What activities need focus, and how should we respond to the current situation?
• What patterns, trends or behaviours are occurring now and over time?
• What structures are influencing those patterns, trends and behaviours?
• How does what we believe, and the way we think, affect the structures we put in place?

Where it sits in the method

The Iceberg belongs to Leadership Question 4, the business model. A value proposition is a promise about value; the business model is the engine that produces it; practices are what turn that engine into something repeatable. The Iceberg is the reason the chain holds — or the diagnostic for where it broke.

A well-defined business model, the right metrics, a clear North Star, and systematic practices that sustain the value proposition. That is the foundation for growth that compounds instead of resetting.