Eight-Step Process for Leading Change

Business Value-Oriented Principles Ltd.

Eight-Step Process for Leading Change

Published on: August 26, 2026 Edited on: August 26, 2026

Author: BVOP

The Eight-Step Process for Leading Change is a structured framework for planning and implementing organizational transformation, originally developed by Harvard Business School professor John Kotter. In project and program management, it helps move stakeholders, teams, and the broader organization from a current state to a desired future state when a project introduces significant new technology, processes, or structures. The framework is often applied alongside formal project delivery methods to sustain adoption.

Kotter's Framework for Leading Organizational Transformation

The Eight-Step Process for Leading Change is a structured framework for planning and implementing organizational transformation, originally developed by Harvard Business School professor John Kotter. In project and program management, it is used to move stakeholders, teams, and the broader organization from a current state to a desired future state when a project introduces significant new technology, processes, or structures. The framework is often applied alongside formal project delivery methods because technical delivery alone rarely produces lasting behavioral change.

Within project management, this concept occupies a different space than change control. Change control governs approved modifications to scope, schedule, cost, or quality baselines. The Eight-Step Process instead addresses the human and organizational side of a change, including leadership alignment, resistance, communication, and cultural reinforcement. A project may have excellent change control and still fail because people refuse to adopt the new way of working. That is the gap this framework is intended to close.

Summary of the Eight-Step Process for Leading Change

Key Concept	Summary
Kotter's Eight-Step Process	Kotter's Eight-Step Process for Leading Change is a structured, leadership-driven framework for planning and executing organization-wide transformation.
Project and Program Management Context	Within project and program management, the framework guides stakeholders, teams, and the broader organization from a current operating state to a desired future state when significant new technology, processes, or structures are introduced.
Iterative Application	Although often presented as a linear sequence, Kotter emphasized that successful change initiatives frequently revisit earlier steps as new information, risks, and stakeholder feedback emerge.
Core Methodology	The framework is a leadership-driven method that establishes a compelling case for change, mobilizes a coalition of influential sponsors and advocates, and systematically institutionalizes new behaviors within the organizational culture.
Development Rationale	Kotter developed the model after observing that many large corporate change efforts failed or underperformed despite having sound strategy and sufficient resources.
Adoption Imperative	As organizations recognized that project success increasingly depends on user adoption and behavioral change rather than technical delivery alone, the framework was integrated into mainstream project and program management practice.
Representative Applications	The framework has been widely applied in corporate restructuring, digital transformation, merger integration, public sector reform, and healthcare performance improvement initiatives.
True versus False Urgency	False urgency generates frantic activity that subsides once external pressure recedes, whereas true urgency builds a shared conviction that preserving the status quo carries greater risk than pursuing change.

What Is the Eight-Step Process for Leading Change?

The Eight-Step Process for Leading Change definition refers to John Kotter’s sequential model for leading large-scale organizational change, first published in his 1996 book Leading Change. The model describes eight stages that leaders move through to overcome inertia, build momentum, and make new behaviors stick. The steps are often presented as a linear sequence, but Kotter himself cautioned that successful change efforts frequently cycle back through earlier steps as new information emerges.

Definition and Core Meaning

The framework is defined as a leadership-driven method for transforming an organization by creating a compelling case for change, building a coalition of influential supporters, and systematically embedding new practices into the culture. It is not a project scheduling tool or a risk register. Its primary output is organizational readiness and adoption rather than a deliverable. In a project context, the eight steps typically run parallel to the technical work, starting before the project is fully planned and continuing after the project’s product is delivered.

The core meaning can be understood through a simple scenario. A company installs a new customer relationship management system. The software deploys on time and within budget. Yet sales teams continue using old spreadsheets because they never felt the urgency, were not involved in the design, and saw no reason to change. The Eight-Step Process exists precisely to prevent that outcome by treating behavior change as a discipline of its own, separate from technical implementation.

Origin and Context in Management

Kotter developed the model after observing that many large corporate change efforts failed despite having sound strategy and resources. His research highlighted recurring patterns in successful transformations, most notably the need for strong leadership rather than just strong management. The model gained traction in executive and organizational development circles, and it was later absorbed into project and program management practice as organizations recognized that project success increasingly depended on adoption rather than delivery alone.

Outside project management, the framework has been widely used in corporate restructuring, digital transformation, mergers, public sector reform, and healthcare improvement. Its credibility comes from that cross-industry exposure. However, project leaders often adapt the model because they operate within a defined timeline, budget, and governance structure that may not allow the full eight steps to unfold naturally over several years.

Key Insights on Change Leadership

Sequential change model: Kotter's Eight-Step Process distills recurring failure patterns in major change initiatives into a leadership-driven framework, first published in his 1996 book Leading Change.
Eight stages build momentum: The model sequences eight deliberate stages that leaders use to disrupt organizational inertia, generate visible momentum, and embed new behaviors until they become the accepted norm.
Steps repeat cyclically: Although the steps are typically presented in a linear order, Kotter explicitly warned that effective change efforts routinely revisit earlier stages as new insights and conditions surface.
Runs parallel to technical work: The eight steps run in parallel with technical project management, beginning before formal planning concludes and extending well beyond delivery to secure genuine behavioral adoption.
Widely applied framework: After observing that major initiatives failed even with sound strategy and adequate resources, Kotter developed this model, which now guides change efforts across corporate restructuring, digital transformation, mergers, public sector reform, and healthcare improvement.

Key Components of the Eight-Step Process

Understanding the key components of the Eight-Step Process requires treating each step as an enabler rather than a rigid phase gate. The eight components are creating urgency, forming a guiding coalition, developing a vision, communicating that vision, empowering broad action, generating short-term wins, consolidating gains, and anchoring new approaches in the culture. None of these steps is a standalone deliverable; they reinforce one another across the project lifecycle.

Step One: Establishing a Sense of Urgency

The first component involves creating a compelling case for why change must happen now. In project management, this often means translating a business case or market threat into language that resonates with the people who will have to change their daily routines. A common mistake is to generate fear and anxiety rather than genuine urgency. False urgency produces frantic activity that fades once pressure subsides, while true urgency creates a shared conviction that continuing with the status quo is riskier than changing.

Project sponsors and program managers play a central role here. They provide data, customer feedback, competitive analysis, or operational failure evidence to make the case tangible. The urgency message must be repeated in different forums and connected to individual work, not just corporate strategy. Without this step, later communication and empowerment efforts often stall because people see no reason to alter their behavior.

Step Two: Forming a Guiding Coalition

A guiding coalition is a group of influential people from across the organization who are committed to the change. The coalition needs sufficient power, expertise, credibility, and leadership to steer the effort. In a project setting, this is not the same as the project team. The project team delivers the technical outputs, while the guiding coalition manages the political and cultural conditions that allow those outputs to be accepted.

Coalition members are often drawn from senior management, operational units, technical functions, and sometimes informal opinion leaders. Their role includes removing obstacles, modeling new behaviors, and communicating consistently. A coalition that exists only on an organization chart will not be effective. Its members must actually work together, debate openly, and demonstrate visible support for the change.

Step Three: Developing a Vision and Strategy

The vision articulates a clear, desirable picture of the future state. It should be simple enough to explain in a few sentences but specific enough to guide decisions about resource allocation, process redesign, and capability building. In project management, the vision connects the project’s stated objectives to the larger purpose of the organization. A project charter may define scope, but the change vision defines the future that scope is meant to create.

Strategy refers to the broad approach for achieving that vision. It is not a detailed work breakdown structure or a Gantt chart. Those artifacts belong to the project plan. The strategy here answers questions about sequencing, sponsorship, capability building, and how the organization will overcome expected resistance. A vision without a credible strategy becomes wishful thinking, and a strategy without a vision becomes a collection of tasks.

Step Four: Communicating the Change Vision

Communication in this context is not a single announcement. It is a sustained campaign that uses multiple channels, repeats the core message, and links everyday decisions to the vision. The project manager and sponsor should model the behavior they want to see. Communication must also be two-way, allowing employees to ask questions, raise concerns, and hear those concerns acknowledged. A well-crafted vision that is poorly communicated has little more value than no vision at all.

In practice, project communication plans often focus on status updates, milestones, and risks. The Eight-Step Process adds a layer of communication aimed at understanding and emotional buy-in. People need to know what the change means for their role, what will stay the same, what will become easier, and what support they will receive. Dense slide decks and executive town halls are rarely sufficient by themselves.

Step Five: Empowering Broad-Based Action

Empowerment means removing obstacles that block people from acting on the vision. Those obstacles can include outdated policies, rigid hierarchies, missing skills, inadequate tools, or managers who actively resist the change. In a project environment, this step often exposes the limits of the project manager’s formal authority. The project manager may need to escalate structural barriers to the guiding coalition or sponsor so that frontline employees are not punished for adopting new behaviors.

Empowerment also involves providing training, coaching, and access to information. People cannot act on a vision they do not understand or lack the capability to implement. This is where the project’s change management and training workstreams intersect. It is not enough to train people on a new system; they also need the authority and confidence to change established workflows and challenge old assumptions.

Step Six: Generating Short-Term Wins

Short-term wins are visible, unambiguous improvements that occur early enough to build momentum and silence skeptics. In project terms, these are not necessarily early deliverables from the final product. They can be pilot results, process improvements, or small successes that demonstrate the change is feasible. The key is that the wins must be real, measurable, and clearly connected to the change effort, not manufactured or exaggerated.

Project managers often undervalue this step because they are focused on the final milestone. However, stakeholders lose confidence when months pass without visible evidence of progress. A carefully planned series of short-term wins maintains sponsorship, rewards early adopters, and creates a narrative of forward motion. Wins should also be celebrated in ways that reinforce the new behavior rather than simply rewarding effort.

Step Seven: Consolidating Gains and Producing More Change

The seventh component guards against premature victory celebrations. After initial wins, the natural temptation is to declare the change complete and ease pressure. Kotter’s model argues that this is one of the most dangerous moments in a transformation. Early wins create credibility that should be used to tackle larger, more deeply embedded problems, such as restructuring a function, changing performance measures, or replacing managers who continue to block progress.

In project management, this step often overlaps with the transition from project delivery to benefits realization. The technical installation may be finished, but the organizational change is not. Business processes may still be unstable, user adoption may be uneven, and old workarounds may persist. Consolidating gains means using the momentum from early successes to drive the next wave of improvement, not simply closing the project and walking away.

Step Eight: Anchoring New Approaches in the Culture

The final component involves making the new behaviors part of the organization’s taken-for-granted way of operating. Culture change does not happen through slogans or training alone. It happens when the new behavior is visibly valued, supported by leadership, reflected in performance reviews and reward systems, and embedded in hiring and promotion decisions. Until that occurs, the change remains fragile and can regress when key sponsors leave or new priorities emerge.

Project managers rarely control cultural systems directly, but they can influence them by documenting new norms, transferring ownership to operational leaders, and ensuring that success measures continue after project closure. If the new way of working is not anchored, the organization may drift back to old habits within months. The project deliverable may exist, but the expected benefits will not materialize.

The Eight-Step Process in Project Management Frameworks

The Eight-Step Process in PMBOK is not presented as a separate knowledge area, but its principles appear across several domains of project governance and leadership. PMI’s A Guide to the Project Management Body of Knowledge, Seventh Edition, includes the principle to enable change to achieve the envisioned future state. That principle recognizes that project teams must help stakeholders transition from current to future conditions. The Eight-Step Process provides one structured way to fulfill that principle.

Eight-Step Process and PMBOK

Within the PMBOK framework, the Eight-Step Process aligns most closely with stakeholder management, communications management, and the leadership skills expected of project managers. Traditional PMBOK process groups such as initiating, planning, executing, and monitoring and controlling do not include the eight steps as formal processes. Instead, the Kotter model is treated as a complementary organizational change management approach. PMI has published guidance acknowledging the role of models like Kotter’s in managing change, while keeping the PMBOK itself focused on project delivery processes.

Project managers using the PMBOK can sequence the eight steps alongside the project lifecycle. Urgency and coalition building often begin during initiating and planning. Communication, empowerment, and short-term wins run through execution. Consolidation and cultural anchoring extend into closing and post-project benefits realization. This alignment helps project managers see that adoption is not a separate activity to be bolted on at the end, but a continuous responsibility throughout the project.

Eight-Step Process and PRINCE2

PRINCE2 addresses change through its change theme, which focuses on issue management and change control. The change theme ensures that requested changes to a project’s products, scope, schedule, or costs are assessed and approved through a controlled process. This is not the same as the Eight-Step Process. PRINCE2 is largely silent on the human and cultural dimensions of organizational change, leaving those concerns to corporate, programme, or portfolio management.

In a PRINCE2 environment, the Eight-Step Process can sit above or beside the project. The project board and project manager manage technical change control, while senior management and the guiding coalition manage the broader adoption challenge. Many organizations using PRINCE2 for project delivery also use a Kotter-style approach at the programme level to prepare the business for the cumulative impact of multiple projects. The two frameworks are not competitors; they operate on different layers of the change problem.

Agile, Hybrid, and Predictive Environments

In predictive environments, the Eight-Step Process often follows a staged rollout, with change activities mapped to major milestones and phase gates. In agile environments, the framework applies less to product increments and more to the organizational transformation required for agile adoption itself. Agile principles embrace changing product requirements, but that is a different type of change from altering reporting lines, incentives, or deeply held work habits.

Hybrid environments combine predictive and agile delivery approaches, and they can benefit from using the Eight-Step Process at the program level while agile teams handle iterative product delivery. A common pattern is a program steering group acting as a guiding coalition, with communication and short-term wins tied to release timelines. The eight steps provide a stable change narrative even when the technical solution evolves frequently.

Key Insights on the Eight-Step Process

Not a formal PMBOK process: The Eight-Step Process does not constitute a distinct PMBOK knowledge area or formal process group; it functions as a cross-cutting governance and leadership framework that supports formal project management activities.
Supports PMI change principle: The PMBOK Seventh Edition explicitly calls on project teams to enable change, and the Eight-Step Process provides a deliberate, structured method for moving stakeholders from current conditions to future ones.
Aligns with stakeholder and communications: In PMBOK terms, the Eight-Step Process aligns most directly with stakeholder management, communications management, and the leadership behaviors project managers are expected to demonstrate when guiding organizational transitions.
Connects to closing and benefits: The emphasis on consolidation and cultural anchoring in the Eight-Step Process extends into closing activities and post-project benefits realization, directly linking change efforts to sustained delivery outcomes.
PRINCE2 omits change culture: PRINCE2 gives limited attention to the human and cultural dimensions of organizational change, assigning those concerns primarily to corporate, programme, or portfolio levels rather than addressing them within project delivery.

Purpose and Importance of the Eight-Step Process

The importance of the Eight-Step Process in project management lies in its ability to address the most common cause of project failure: resistance from the people expected to use the new solution. Projects do not fail only because of technology problems or budget overruns. They fail when business units continue with old practices, sponsors lose interest, or the organization never fully absorbs the change. The eight steps force attention on those human factors before they become critical risks.

Why Project Leaders Use the Framework

Project leaders use the framework because it provides a shared language for discussing adoption and resistance with sponsors and executives. It also gives structure to activities that are often treated as vague soft skills, such as communication, leadership, and coalition building. By naming each step, project managers can identify where a change effort is stuck. If people are not adopting a new system, the root cause may be a weak urgency message, an absent guiding coalition, or no meaningful short-term wins, each of which points to a different corrective action.

The model also helps sequence the emotional and political work of change. During initiation, the emphasis is on urgency and coalition. During execution, communication and empowerment dominate. Near the end, consolidation and cultural anchoring become more important. This rough sequence helps project teams avoid the mistake of starting with training before anyone understands why the change is happening.

Connection to Benefits Realization

Benefits realization is the process of ensuring that project outputs lead to measurable business value. The Eight-Step Process supports benefits realization because adoption is a precondition for most non-financial and financial benefits. A new workflow system produces no benefit if employees do not use it correctly. A restructured service model produces no benefit if customers still follow the old path. By embedding new behaviors into culture, the framework increases the probability that planned benefits will actually appear after the project ends.

In many organizations, benefits are measured months after project closure. The Eight-Step Process remains relevant during that post-project period. Steps seven and eight are especially important because they sustain momentum when the project team has disbanded and operational leaders must take over ownership of the change. Without that continuity, benefits can evaporate even when the project deliverable was technically successful.

Eight-Step Process vs Change Control and Related Concepts

The Eight-Step Process vs change control distinction is one of the most misunderstood aspects of project management. Change control is a governance discipline that evaluates requested modifications to approved project baselines. The Eight-Step Process is a leadership discipline that prepares an organization to adopt a new way of working. They share the word change but address fundamentally different problems, and confusing them can lead to serious gaps in either governance or adoption.

Organizational Change vs Project Change Control

Think of project change control as the gatekeeper for scope, schedule, and cost. When a stakeholder asks for an additional feature, the change control process determines whether that request should be approved, logged as an issue, or rejected. Organizational change, by contrast, concerns what happens after approval. Even when a change is technically sound, the organization may resist it because people fear the new process, lack skills, or do not trust leadership.

A project can have a flawless change control log and still suffer from low adoption. Conversely, a project can have high employee enthusiasm but poor change control, leading to uncontrolled scope growth and budget failure. Mature organizations separate these two functions. The project manager manages change control. The sponsor, program manager, or dedicated change manager often drives the Eight-Step Process. Both are necessary, but they are not interchangeable.

Relationship to ADKAR and Other Change Models

The Eight-Step Process is often compared with the ADKAR model, which focuses on individual change through awareness, desire, knowledge, ability, and reinforcement. ADKAR is a bottom-up view of change, while Kotter’s model is primarily a top-down organizational view. They can be used together. For example, Kotter’s communication steps build awareness and desire, while empowerment and training build knowledge and ability. Other models, such as Lewin’s unfreeze-change-refreeze model, offer simpler conceptual frameworks but lack the detailed operational steps found in Kotter’s work.

Project practitioners sometimes believe they must choose one model. In reality, the choice depends on the nature of the change. Large transformational programs often need the organizational breadth of the Eight-Step Process. Smaller process changes or individual role transitions may be better served by ADKAR. The important point is to use a deliberate framework rather than assuming that a well-written communication plan will automatically produce adoption.

Relationship to Stakeholder Engagement and Communication Management

Stakeholder engagement and communication management are PMBOK knowledge areas that directly support the Eight-Step Process. Stakeholder analysis identifies who will resist or support the change. Communication planning determines the channels and messages needed to sustain urgency and vision communication. The guiding coalition itself is a stakeholder engagement structure, populated by influential stakeholders who can shape opinion across the organization.

The eight steps add a narrative and sequencing layer to standard communication management. A project communication plan may specify weekly status updates, but it rarely addresses the emotional arc of change. By linking communication activities to urgency, vision, short-term wins, and cultural anchoring, the Eight-Step Process gives stakeholders a coherent story about where the organization is going and why their role matters.

Core Takeaways on Change Disciplines

Change control as governance discipline: Change control functions as the formal governance mechanism that evaluates proposed modifications against approved project baselines, ensuring scope, schedule, and cost decisions are deliberate, documented, and controlled.
Eight-Step Process drives adoption: The Eight-Step Process provides a structured leadership framework for building organizational readiness, addressing the emotional and behavioral barriers such as resistance, skill gaps, and eroded trust that governance controls cannot overcome.
Confusing them creates serious gaps: Confusing these disciplines creates complementary risks: weak change control allows scope and budget drift to go unchecked, while neglecting organizational change management leaves employee resistance and low adoption to undermine even technically sound projects.

BVOP Perspective on the Eight-Step Process

The BVOP perspective on change management emphasizes the invisible organizational damage that poorly handled change can create. Business Value-Oriented Project Management, or BVOPM, introduces the concept of process damage as harm that does not appear on a project dashboard but accumulates when employees are forced to work around confusing new systems or contradictory instructions. When the Eight-Step Process is applied without attention to this damage, urgency campaigns can easily slide into overwork and wasted effort.

Process Damage and Waste in Transformation

BVOPM treats urgency as useful only when it produces focused, value-driven action. If urgency creates anxiety, excessive overtime, or perfectionist rework, it generates waste. The framework categories of overwork, perfectionism, and rejected acceptable work are particularly relevant during steps five and six, where teams are expected to remove barriers and produce quick wins. A short-term win that burns out the team or requires unsustainable effort is not a genuine business value win.

BVOPM also tracks Business Value Points to detect whether a change initiative is actually moving the organization toward durable value or merely producing activity. A persistent decline in those points may signal that the change should be terminated or fundamentally reoriented. This mirrors the Eight-Step Process principle that change should be anchored in measurable new behavior, not just celebrated as a completed milestone.

Common Challenges, Pitfalls, and Misconceptions

Several common misconceptions about the Eight-Step Process persist in project environments. The first is that the eight steps are a simple checklist that can be executed once in sequence. In practice, change is iterative and messy. Urgency may need to be refreshed after a new competitor emerges. A guiding coalition may lose a key sponsor and require rebuilding. Communication must be repeated long after leaders feel bored with the message. Treating the model as a checklist often leads to superficial compliance rather than real transformation.

Misconceptions About the Model

Another misconception is that the framework is only for senior executives. Project managers and program managers frequently use the model to structure their own change management workstreams, even when they do not have formal authority over all stakeholders. They can frame urgency messages, help form cross-functional coalitions, and design communication activities that support the sponsor’s vision. The model does not require the project manager to become the chief executive; it requires the project team to work deliberately on adoption.

A third misconception is that the Eight-Step Process can replace project change control or risk management. It cannot. The model does not assess technical feasibility, budget impact, or schedule implications. It also does not provide a mechanism for logging and approving scope changes. Organizations that try to use it as a governance tool often lose control of the project baseline while believing they are managing change. That is a fundamental category error with costly consequences.

Implementation Pitfalls

The most common implementation pitfall is skipping urgency and moving directly to communication or training. When people do not understand why a change is necessary, they interpret training as an imposition. Another pitfall is allowing the guiding coalition to become a ceremonial body that meets but makes no decisions. Coalition members must be given real responsibilities, such as removing barriers or championing the change in their areas.

Declaring victory too early is also a persistent problem. The project may deliver on time, and the steering committee may celebrate, but adoption may still be fragile. If the cultural anchoring step is skipped, old habits return quickly. Finally, the model can be overkill for small, low-impact changes. Applying all eight steps to a minor process adjustment creates bureaucratic waste and damages the credibility of change management. The framework is best reserved for changes that require significant shifts in behavior, structure, or identity.

Key Takeaways on Eight-Step Pitfalls

Urgency demands periodic renewal: Urgency fades as daily operational pressures return, so leaders must deliberately reconnect the change effort to a current threat, such as a competitor's new offering that reshapes the strategic case for action.
Coalitions require active rebuilding: A guiding coalition often depends on a few critical sponsors, and losing one can stall progress; the team must rebuild the coalition with equal or greater authority to preserve momentum and credibility.
Communication outlasts leader fatigue: The change message must be repeated long after leaders have grown tired of it, because consistent repetition is what moves stakeholders from initial awareness to genuine adoption.
Checklist use blocks real transformation: Treating the Eight-Step Process as a checklist produces surface-level compliance rather than the deeper shifts in behavior, systems, and mindset that sustainable transformation actually requires.
No substitute for project governance: The Eight-Step Process complements but does not replace project change control or risk management, and using it as a governance substitute often allows scope, schedule, or budget baselines to drift.

Evolution and Current Thinking

The current thinking on Kotter’s Eight-Step Process has moved away from a strictly linear interpretation toward a view of the steps as an ongoing set of leadership capabilities. Modern organizations face continuous change driven by technology, regulation, and competitive pressure. Waiting to complete all eight steps before starting another change is no longer realistic. Instead, leaders are expected to operate several of the steps simultaneously across different parts of the organization.

Debates and Critiques

Some scholars and practitioners argue that the model is too top-down and places excessive faith in a guiding coalition of senior leaders. In highly decentralized or expert-driven organizations, such as research institutions or professional service firms, mandated change can produce passive resistance rather than commitment. Others note that the model was built for large-scale transformations and may not scale down well to department-level projects. There is also debate about whether culture change can be deliberately anchored through the final step, or whether culture emerges from many small behavioral shifts over time.

Kotter himself updated his thinking in later work by proposing a dual operating system that combines traditional hierarchical structures with a more flexible network-based approach. That update reflects a broader shift in management thought toward viewing change as continuous rather than episodic. The original eight steps remain influential, but they are increasingly treated as accelerators rather than gates in a phased methodology.

Current Application in Projects and Programs

Many organizations now embed the Eight-Step Process within their project and program management offices as a standard change management framework. The model is used in project charters to define the case for urgency, in stakeholder plans to identify coalition members, and in benefits dashboards to track short-term wins and cultural adoption indicators. Some project management offices combine Kotter’s model with agile delivery, using release cadences to test change messages and collect feedback before scaling.

The most durable insight from the framework is that technical delivery and behavioral adoption are separate but connected disciplines. A project manager can deliver every deliverable on time and still fail if the organization does not change. The Eight-Step Process does not eliminate that risk, but it makes the risk visible, nameable, and actionable. That is why it remains a foundational reference point for anyone managing projects, programs, or portfolios where people must change how they work.

Understanding the Concept More Deeply

Eight-Step Process for Leading Change vs. Change Control

The Eight-Step Process for Leading Change is commonly confused with change control because both use the word change and both appear in project environments. Change control is a governance discipline that manages approved modifications to baselines for scope, schedule, cost, quality, or requirements. It records requests, assesses impacts, and ensures that changes to project deliverables or plans are authorized and traceable.

The Eight-Step Process for Leading Change, in contrast, targets the human and organizational side of transformation. It addresses why people resist, how leaders create urgency, how coalitions form, and how new behaviors become cultural norms. A project can have a perfect change control board and still deliver a product that nobody uses, underscoring the need for benefits realization.

For example, a team may formally approve a scope change to add new workflow features, but if sales staff continue using the old process because they were never convinced of the need, the change control log is complete while adoption has failed. The key difference is the object of control. Change control governs the change to project artifacts and plans.

The Eight-Step Process governs the change in people's behavior, beliefs, and routines. The two are complementary. A large enterprise system implementation often runs technical changes through change control while using Kotter's steps to prepare managers and end users.

Confusing them leads teams to believe that documented approval equals organizational acceptance, when in practice approval and adoption are separate outcomes.

Origins in Kotter's Study of Corporate Transformation Failures

The Eight-Step Process was introduced by John Kotter, a professor at Harvard Business School, in the mid-1990s. His thinking first reached a wide management audience through a 1995 Harvard Business Review article titled "Leading Change: Why Transformation Efforts Fail." The fuller model appeared in his 1996 book Leading Change. Kotter developed the framework to solve a specific problem.

He had observed that many large companies pursued major restructuring, quality improvement, or culture change programs with sound strategies and experienced executives, yet the transformations still failed or produced only temporary gains. The core failure was not strategy or resources; it was the inability to alter human behavior at scale, a missing success factor.

Kotter identified recurring errors, including allowing too much complacency, failing to build a sufficiently powerful guiding coalition, undercommunicating the vision, letting obstacles block progress, not creating short-term wins, declaring victory too soon, and neglecting to anchor new approaches in the culture. The eight steps correspond to remedies for these errors. In its original context, the model was intended primarily for senior leaders driving large corporate change.

Since then, its meaning has broadened. Project managers, program sponsors, and organizational change managers now use it as a readiness and adoption framework that runs alongside technical delivery. This shift does not change the model's core claim.

It still holds that transformation is a leadership and behavior challenge before it is a technical or administrative one.

Boundary Conditions and Limits of the Model

The Eight-Step Process is a powerful framework for planned, large-scale transformation, but it has boundary conditions. It assumes that change is episodic, meaning there is a current state, a desired future state, and enough time to move people through stages. It also assumes that leaders can influence the change through communication, coalition building, and reinforcement.

The model breaks down or becomes less applicable in several complex situations. First, emergency or crisis responses often cannot wait for a broad guiding coalition or a carefully communicated vision. A safety recall, cyber incident, or regulatory enforcement action may require immediate top-down compliance rather than voluntary adoption.

Second, small, routine, or continuous improvements do not need the full eight-step sequence. Applying the entire framework to a minor process tweak can create unnecessary overhead. Third, the model assumes that adoption depends at least partly on human choice.

If a change can be enforced through hard system constraints, such as removing the old software entirely, some behavioral steps become less central. Fourth, the model is less suited to highly fluid environments where the desired future state constantly shifts, as in some agile product organizations. Kotter's framework remains useful, but practitioners should treat it as a diagnostic lens, not a guarantee.

It applies most clearly when the change is significant, organization-wide, and dependent on sustained shifts in behavior.

Misreading the Steps as Linear, Top-Down, or Fear-Based

A common misinterpretation is that the Eight-Step Process must be executed as a strict, one-way sequence. Misinterpretation: once a step is completed, the leader moves to the next and never returns. Fact: Kotter explicitly cautioned that change efforts often cycle back.

As new information appears or resistance resurfaces, teams may need to revisit urgency, communication, or coalition membership. Another common misinterpretation is that the model is a project management methodology for controlling scope or schedule. Fact: it does not replace project planning, risk management, or change control.

It addresses adoption and leadership, and it runs parallel to technical delivery rather than governing the project baseline. A third misinterpretation is that creating a sense of urgency means manufacturing fear or presenting a false crisis. Fact: Kotter distinguished productive urgency from anxiety-driven panic.

The goal is to overcome complacency with an honest, compelling case for action, not to paralyze people with threats. A fourth misinterpretation is that the process is only for senior executives. While top-level sponsorship is critical, project managers, middle managers, and informal influencers often operate the day-to-day steps, such as removing obstacles, generating short-term wins, and reinforcing new behaviors.

These misreadings persist because the model is often summarized in diagrams and checklists. The diagrams simplify, but the full framework describes a leadership discipline that is iterative, behavioral, and distributed across the organization.