What This Book Actually Teaches You
Most change management books read like corporate training videos stretched into 200 pages. Our Iceberg Is Melting By John Kotter is different because it wraps its framework inside a children's story about penguins. It sounds ridiculous. It works, but not for the reason people usually say. The book teaches the 8-Step Change Model that Kotter developed from decades of watching organizations fail at transformation. The story itself features a pigeon named Norman who delivers exposition, a penguin named Fred who resists everything, and an iceberg that represents the market environment changing around you. The framework comes out of that narrative without any obvious lecture sections.
Our Iceberg Is Melting By John Kotter
Here's how the 8 steps actually play out in a real company, not the sanitized version from the book. Step 1 is creating urgency. This means getting people to feel that the current situation is unsustainable. Not presenting data. Feeling it. I saw a VP at a mid-size logistics firm try this once by sharing a spreadsheet showing a 3% decline in quarterly revenue. Nobody moved. She came back two weeks later with three customer emails where people said they were switching suppliers, and suddenly the room changed temperature. That's the difference between intellectual understanding and genuine urgency. Step 2 is building the guiding coalition. This is not about assembling a committee. It's about finding five or six people who have informal influence across different parts of the organization and convincing them to work together before you announce anything. The common mistake is picking senior managers. Senior managers have titles, not necessarily influence. I learned this when a client asked me to help them pick a change coalition and they wanted to include their two most junior directors. I pushed back hard. Those two had zero social capital in the building. We replaced them with a mid-level operations lead and a senior IT person who everyone genuinely listened to. The initiative moved six weeks faster because of that swap alone.
Step 3 is creating a vision. A vision statement is not a poster you put in the breakroom. It's a simple explanation of what the future looks like and why it matters, delivered in language your least technical employee can repeat back to you. If you can't explain it in two sentences, you don't have a vision, you have a strategy document. Step 4 is communicating the vision. This step gets it wrong most often. People think communicating means sending an email and holding a town hall. It means repeating the message obsessively through every available channel for at least six months. I've seen this step fail because leaders used jargon in their all-hands meetings. "We're going to leverage synergies across verticals" is not communication. It's noise. Say what you mean in plain words. Step 5 is empowering action. This means removing obstacles. It means firing people who actively block progress, changing processes that are outdated, and giving teams the authority to make decisions without waiting for approval. If your people can't execute because bureaucracy gets in the way, no amount of motivation will fix it. I worked with a team trying to roll out a new CRM system who couldn't proceed because their procurement department required three separate approvals for any software modification over $500. The project stalled for four months. The fix was getting the CEO to bypass procurement for IT tools under $5,000. One signature, one policy change, project unblocked.
Step 6 is generating short-term wins. Pick visible, achievable milestones early and celebrate them publicly. This builds momentum. Without it, people start wondering if the whole thing is going anywhere. I've watched change initiatives die because leadership never marked any visible progress. After eight months of "we're in the early stages," everyone assumed it wasn't working and quietly returned to old habits. Step 7 is consolidating gains and producing more change. Don't declare victory after the first win. Use that momentum to tackle harder problems while people still believe in the process. This is where most organizations pivot too early and lose the gains they just made. Step 8 is anchoring change in culture. This means making the new behavior so normal that nobody remembers what it was like before. It takes 18 to 24 months typically. New hires need to absorb the change as the default state, not as something extra being asked of them.
There's a specific problem people hit with this model that isn't covered in the book. The 8 steps sound linear but in practice they overlap constantly. You might be doing step 4 (communicating) while still working on step 2 (building the coalition). People get confused when you ask them to follow steps sequentially. Tell them it's iterative from day one. That's how it actually works. Another counter-intuitive thing: this framework assumes a certain size and structure of organization. It works poorly in companies with fewer than 50 people because there's no hierarchy to navigate and the urgency happens automatically. It also doesn't translate well to contractor-heavy or gig-economy organizations where you can't build a stable guiding coalition. I tried adapting it for a platform company with 80% freelance workers and it completely fell apart. You can't anchor change in culture when your "culture" is a set of independent contractors logging in for three-month stints. The penguin story device in the book is intentional. It makes the concepts stick because they're wrapped in narrative. If you're using this in a corporate training setting, don't skip the story portions. People remember the pigeon Norman years later. They forget the bullet points. The format is part of the method.
One more thing nobody mentions: the book was written in 2004 and the examples assume a pre-smartphone, pre-remote-work workplace. Adapting it for hybrid teams requires adjusting how you think about visibility and communication. What looked like a strong visible win in 2004 might be invisible in a distributed environment. Make sure you account for that when you're applying these steps today.
