Most organizational improvements fail not because the solution was wrong, but because the change behind it wasn’t managed well. That’s where the Kotter change model comes in, an 8-step framework developed by Harvard professor John Kotter that gives leaders a structured path from initial idea to lasting organizational transformation. Since its introduction in 1996, it has become one of the most widely referenced approaches to change management across industries.
At Lean Six Sigma Experts, we see this play out constantly. Organizations invest in process improvement initiatives, new workflows, waste reduction programs, efficiency overhauls, only to watch the gains erode within months. The technical methodology is sound, but without a disciplined approach to leading people through change, even the best-designed improvements stall. Kotter’s framework addresses exactly this gap, and it pairs naturally with Lean Six Sigma deployments where cultural buy-in determines whether improvements stick or fade.
This article breaks down all eight steps of Kotter’s model in detail, explains how each one functions in real business environments, and compares the framework to other change management theories. Whether you’re rolling out a company-wide continuous improvement program or managing a single departmental shift, you’ll walk away with a clear understanding of how to structure change so it actually holds. Let’s get into how the model works, step by step.
Why Kotter’s change model still matters
John Kotter didn’t build his framework in a vacuum. He spent years studying why major change efforts at large organizations kept failing, even when leaders had the right intentions, adequate budgets, and capable teams behind them. The pattern he found was consistent: organizations were skipping steps, underestimating resistance, and declaring victory too early. His 1996 book Leading Change translated those observations into a structured, repeatable approach that leaders could actually execute rather than just reference.
The failure rate that drove Kotter’s research
Kotter’s original research pointed to a stark reality: roughly 70% of large-scale change initiatives fail to achieve their intended goals. That number has been cited, tested, and challenged over the years, but the core insight holds. Organizations routinely underestimate how much deliberate leadership work change requires, and they pay for it in wasted time, eroded budgets, and broken employee trust.
Research consistently shows that failed change efforts share the same root causes: weak urgency, absent leadership coalitions, and premature celebrations of progress.
The reasons behind this failure rate are rarely technical. A new ERP system doesn’t fail because of a coding error. A lean manufacturing rollout doesn’t collapse because the toolset was wrong. These initiatives fail because people weren’t brought along in a way that made the change feel necessary, supported, and permanent. Kotter’s model addresses each of those human-side gaps directly and in a specific sequence.
Why the model stays relevant in modern organizations
Since 1996, the business environment has shifted significantly. Digital transformation, remote work restructuring, and faster market cycles have made organizational agility a genuine competitive requirement. You might wonder whether a framework from decades ago still applies today. It does, because the psychological and social dynamics of how people respond to change haven’t shifted alongside the technology.
Employees still resist changes they don’t understand. Leaders still underinvest in communication. Departments still protect existing workflows when they feel threatened. The kotter change model targets these behaviors at their root rather than working around them. That’s why organizations across industries, from healthcare systems to manufacturing plants to financial services firms, continue to apply it in active change deployments today.
What separates Kotter from generic change advice
Most generic change management advice tells you to communicate clearly, secure buy-in, and stay consistent. Those recommendations aren’t wrong, but they’re not specific enough to act on. The real value of Kotter’s model comes from its sequencing. Each step builds directly on the previous one, and skipping steps produces specific, predictable failure modes you can actually anticipate.
For example, launching a new process improvement initiative without first establishing urgency causes employees to treat it as another program of the month. Skipping the step of building a guiding coalition makes the initiative dependent on a single internal champion whose departure can end the whole effort. This level of specificity gives you something you can use in practice, not just in planning sessions. The model functions as both a diagnostic tool and an execution roadmap, which explains why it has remained a primary reference in change management for nearly three decades.
Kotter change model overview and key ideas
The kotter change model organizes change into eight sequential steps that move an organization from initial awareness through lasting transformation. Kotter built the model around a critical finding: change efforts fail when leaders treat the steps as optional or interchangeable. Each step creates the foundation the next one requires, which means the sequence itself is central to how the model works, not just a suggested order.
The structure of the eight steps
Kotter groups the eight steps into three broad phases. The first three steps focus on creating the climate for change, building enough urgency and leadership alignment to make the need for change feel real and immediate. Steps four through six shift attention to engaging the broader organization, removing obstacles, generating visible short-term wins, and keeping the effort from losing momentum midway through. The final two steps are about making new behaviors permanent by anchoring them in the organization’s culture and management practices.
The sequencing is not decorative. Skipping a step produces specific, predictable failure modes that Kotter identified across hundreds of major change efforts.
These three phases work together as a single connected arc. You can’t embed lasting culture change if your organization hasn’t yet built internal momentum or eliminated the barriers blocking new behaviors. Understanding the model as three connected phases rather than eight separate tasks helps you apply it more effectively in practice.
What Kotter means by transformation
Kotter uses the word transformation to mean something more specific than adopting new tools or updating processes. He defines it as a genuine shift in how people think and behave during their workday, not just what systems they’re technically required to use. A process change that employees follow under supervision but abandon when no one is watching isn’t a transformation. That’s compliance, and it won’t hold.
This distinction shapes the model’s consistent emphasis on vision, communication, and cultural reinforcement at every stage. Kotter’s framework pushes leaders to invest as much in the human side of change as in the operational side. When you apply this thinking to a process improvement program, you build the conditions where employees sustain the gains because they understand and own them, not because someone is managing them to comply.
The 8 steps explained with practical actions
The kotter change model gives you eight specific steps, each with a defined purpose and a concrete set of actions to complete it. Understanding what each step actually requires in practice, not just in theory, is how you get real traction from the framework. Here’s what each step means and what you should do when you’re in it.
Steps 1-3: Build urgency, coalition, and vision
Step 1, Create Urgency, requires you to surface the real data behind why change is necessary. Pull market performance numbers, customer satisfaction trends, or operational inefficiencies and present them to your leadership team before anyone else. Step 2, Build a Guiding Coalition, means assembling a cross-functional group of credible, influential leaders who actively champion the initiative. A single sponsor isn’t enough here. You need a visible group of people others trust.
Moving into Step 3, you develop and test your change vision before releasing it broadly. This vision should be clear enough that any employee can explain it in under two minutes. A vague vision produces vague behavior, and that gap surfaces in every downstream step of the model.
A change vision that requires a slide deck to explain is too complicated to drive consistent action across an organization.
Steps 4-6: Enable action and sustain momentum
Step 4, Communicate the Vision, means repeating the message through multiple channels: team meetings, written updates, and one-on-one conversations between managers and their direct reports. Step 5, Remove Obstacles, requires you to identify the specific systems, processes, or people blocking new behaviors and address them directly. This is where many organizations stall, because removing obstacles requires real authority and decisive action.
Generating short-term wins in Step 6 means planning visible, measurable improvements you can deliver within the first 90 days. These wins prove the initiative is working before full implementation is complete, and they rebuild confidence in teams that have watched previous efforts fall apart.
Steps 7-8: Lock in the gains
Step 7, Consolidate Gains, means using early successes as leverage to tackle larger, more complex changes. You build on what worked rather than declaring the effort finished. Step 8, Anchor Change in Culture, requires you to connect new behaviors explicitly to organizational results and ensure your hiring, promotion, and recognition practices reinforce what you’ve built. Without this final step, improvements erode as soon as leadership attention shifts elsewhere.
How to apply Kotter’s model in your organization
Applying the kotter change model in practice requires more than reading the steps and assigning owners. You need to treat the framework as a project with defined phases, deliberate milestones, and regular checkpoints that tell you whether the work at each step is genuinely complete before you advance.
Start with a diagnostic before step one
Before you formally launch the first step, run a quick diagnostic of your organization’s current state. Assess employee awareness of existing problems, identify which leaders carry genuine credibility across teams, and note any active resistance patterns that are already visible. This pre-work shapes how you approach urgency and coalition-building so you’re working with real conditions rather than assumptions.
Your diagnostic doesn’t need to be a formal study. A series of structured conversations with frontline managers and key department heads gives you enough signal to calibrate your approach. What you’re looking for is whether people already sense the need for change or whether you’ll need to do significant groundwork before step one even begins.
Assign step ownership to specific leaders
Each of the eight steps needs a named owner with decision-making authority, not just a team responsible for tasks. When step ownership is vague, progress on critical actions like removing obstacles or sustaining short-term wins gets deferred because no one has clear accountability.
Accountability gaps at the step level are one of the most common reasons change efforts lose momentum before they reach the consolidation phase.
Your guiding coalition from Step 2 is the natural place to distribute this ownership. Assign specific steps to specific coalition members based on their influence in the areas each step touches. The leader who controls the budget process, for example, is better positioned to own obstacle removal than someone without financial authority.
Build a timeline with built-in review points
Set realistic timeframes for each step and schedule explicit review points where your coalition assesses progress before moving forward. Treating the model as a linear checklist without reviews creates a false sense of advancement where you believe a step is complete while the underlying work remains unfinished.
A 90-day planning horizon works well for the first three steps. After that, extend your view based on the complexity of your initiative and the size of the organization you’re working through. Adjust the pace based on actual evidence, not projected timelines.
Roles, communication, and change governance
The kotter change model requires more than a strong strategy. It requires clear ownership, deliberate communication, and a [governance structure](https://leansixsigmaexperts.com/operational-excellence-strategy/) that keeps the effort accountable throughout its full duration. Without these three elements working together, even well-designed change initiatives drift, lose alignment, and fail to reach the consolidation phase.
Define roles before the initiative launches
Ambiguous roles are a consistent source of delays in change programs. Before your initiative moves past the urgency-building phase, you need to define specific responsibilities for each member of your guiding coalition and establish who has authority to make decisions at each stage.
A clear role structure typically includes a senior executive sponsor, a day-to-day program lead, functional change champions in each affected department, and a communication owner responsible for coordinating messaging across the organization. Documenting these roles and sharing them openly with your workforce signals that the initiative has real structure behind it, not just executive intent.
Build a communication rhythm that sustains momentum
Communication in a change initiative is an ongoing operating function, not a one-time announcement. You need to establish a regular cadence that delivers updates, celebrates visible progress, and addresses concerns before they turn into active resistance.
Silence during a change initiative is never neutral. Employees fill information gaps with assumptions, and those assumptions are almost always worse than the actual situation.
Your communication rhythm should include weekly updates from direct managers, monthly messages from senior leaders, and a consistent feedback channel where employees can raise concerns without navigating formal chains. The format matters less than the consistency. When people hear from leadership on a predictable schedule, they trust that the initiative is still active and that their questions will be addressed.
Governance keeps the effort on track
Change governance is the set of structures, meetings, and decision rights that prevent your initiative from becoming reactive. A basic governance framework includes a steering committee that reviews milestone progress monthly, a change lead with authority to escalate blockers, and a defined process for handling scope adjustments without disrupting the broader effort.
Your governance model doesn’t need to be complex to be effective. A simple checkpoint cadence with clear criteria for advancing between steps gives your coalition the structure to move forward with confidence rather than debating whether the previous step is truly complete.
Common failure points and how to avoid them
The kotter change model identifies eight steps for a reason: each one prevents a specific category of failure. In practice, most organizations don’t fail because they chose the wrong change approach. They fail because they execute the right approach with critical gaps in follow-through. Knowing where those gaps typically appear gives you a real advantage before your initiative runs into trouble.
Declaring victory too early
This is the most common and most damaging failure in structured change programs. A team hits a visible early win, leadership celebrates, and the attention that sustained momentum quietly shifts to other priorities. Within weeks, old behaviors start returning because the cultural reinforcement work was never completed.
Premature celebration is the single fastest way to undo genuine progress because it signals to the organization that the effort is finished when the hardest work still lies ahead.
To avoid this, you need to set explicit criteria for what "done" actually looks like before you begin. Document the behaviors, metrics, and structural changes that must be in place before the initiative is formally closed. Use your guiding coalition to enforce that standard, not just celebrate progress along the way.
Underestimating resistance
Resistance rarely announces itself directly. It shows up as slow adoption, workarounds, and passive non-participation from employees who never publicly opposed the initiative. Leaders who don’t account for this pattern end up misreading their implementation data and assuming progress that isn’t there.
Your best tool against this failure point is structured feedback loops built into your communication rhythm. Direct managers should be checking in with their teams on a weekly basis, not just passing along updates. When frontline resistance surfaces early, you have time to address root causes before they spread across the organization. Waiting until adoption numbers fall short gives you nothing to work with except damage control.
Weak or incomplete guiding coalition
A guiding coalition that exists on paper but doesn’t function as an active, visible leadership group gives your initiative the appearance of support without the substance. When employees don’t see coalition members reinforcing the change in their day-to-day decisions, they conclude that leadership isn’t truly committed.
Build your coalition around people with genuine organizational influence, not just formal authority. Credibility at the team level matters more than seniority on an org chart. Revisit coalition composition at each major phase transition and replace members who have disengaged rather than leaving gaps in your leadership coverage.
Kotter vs other change models like ADKAR
The kotter change model isn’t the only structured approach to change management, and knowing how it compares to alternatives helps you choose the right tool for your specific situation. ADKAR, developed by Prosci, is the most frequently cited alternative. Both frameworks address the human side of change, but they approach the problem from fundamentally different angles that make each one better suited to certain contexts.
How ADKAR approaches change differently
ADKAR stands for Awareness, Desire, Knowledge, Ability, and Reinforcement. Unlike Kotter’s organizational-level sequence, ADKAR focuses on the individual employee’s journey through change. It gives managers a way to diagnose exactly where a specific person is struggling and intervene at that point rather than applying the same solution across an entire workforce.
ADKAR treats change as an individual experience first, while Kotter treats it as an organizational challenge first; both views are accurate, just aimed at different scales.
This individual focus makes ADKAR especially useful when you’re rolling out a targeted technology adoption or a specific policy shift where you need to track progress person by person. It works well as a diagnostic tool during the later steps of Kotter’s model when you’re trying to understand why adoption isn’t reaching full coverage across your workforce.
Which model fits your situation
The most practical answer is that these two models aren’t competing with each other in most real deployments. Kotter gives you the organizational roadmap, the sequenced leadership actions that move a company from urgency to embedded culture change. ADKAR gives you the individual diagnostic tool that explains why certain employees or teams aren’t progressing at the expected rate.
When you’re leading a large-scale transformation across multiple departments or sites, Kotter’s sequential structure gives you the governance and momentum-building logic the effort requires. When your guiding coalition asks why a specific department isn’t adopting the new process, ADKAR gives you the language and framework to pinpoint the breakdown and address it directly. Using both together makes your change program more complete than either model delivers on its own. Other frameworks like McKinsey’s 7-S model focus more on organizational alignment than on the leadership sequence or individual readiness that Kotter and ADKAR respectively emphasize.
Using Kotter with Lean Six Sigma projects
Lean Six Sigma gives you the analytical tools to identify waste, reduce variation, and redesign processes. What it doesn’t provide on its own is the leadership framework to ensure people actually adopt and sustain the improved state. That’s the gap the kotter change model fills when you integrate it into a Lean Six Sigma deployment. The two approaches complement each other directly: one handles the technical rigor of process improvement, and the other handles the human work of making those improvements permanent.
Where the two frameworks connect
The connection between Kotter and Lean Six Sigma is most visible in how organizational resistance surfaces during both. In Lean Six Sigma projects, teams frequently complete thorough root cause analysis and solution design only to watch implementation stall because the affected workforce never genuinely bought into the change. Kotter’s steps 1 through 3, which focus on urgency, coalition-building, and vision clarity, directly address the conditions that allow that stall to happen. When you build a guiding coalition that includes respected frontline leaders before a Lean project even enters the Improve phase, you’re already reducing the resistance your team will face at implementation.
Integrating Kotter’s urgency and coalition steps before your Lean Six Sigma project reaches the Improve phase cuts downstream adoption resistance significantly.
Applying Kotter at the DMAIC phase level
DMAIC, which stands for Define, Measure, Analyze, Improve, and Control, maps naturally to Kotter’s step sequence when you treat each phase as both a technical and a change management milestone. During the Define phase, you build urgency and identify your coalition. During the Measure and Analyze phases, you develop your vision and communicate it to affected stakeholders. The Improve phase is where you remove obstacles, deliver short-term wins, and maintain momentum. The Control phase corresponds directly to Kotter’s final two steps, where you consolidate gains and anchor new behaviors in daily management routines rather than just project documentation.
Sustaining gains after project close
One of the most consistent failure modes in Lean Six Sigma deployments is a process regression that begins six to twelve months after the project is officially closed. Control plans exist on paper, but the cultural reinforcement work that makes people default to the new standard was never completed. Kotter’s Step 8 requires you to connect improved behaviors explicitly to organizational performance outcomes and ensure that your management systems, including reviews, recognition, and hiring standards, reflect the new way of working. When your Lean Six Sigma project closes with those structural reinforcements in place, you protect the financial and operational gains the team worked to achieve.
Final takeaways
The kotter change model gives you something most change advice doesn’t: a specific, sequenced path that accounts for how people actually respond to organizational shifts. Each of the eight steps builds directly on the one before it, and that sequence is what separates sustained transformation from short-lived compliance.
Your biggest risk in any change initiative isn’t a flawed solution. It’s skipping the steps that build urgency, align leadership, and embed new behaviors into how your organization actually operates day to day. When you pair Kotter’s framework with Lean Six Sigma methodology, you cover both the technical and human sides of improvement, which is where most programs fall short.
If you’re ready to bring both disciplines into your organization and want guidance on how to structure the work, our team at Lean Six Sigma Experts is here to help. Reach out to learn more about our consulting and training services and start building change that holds.