A framework becomes useful only after the organization understands what is changing, why it is changing, and where the main difficulty lies.
A new system, a process redesign, a cultural shift, and a new business direction create different requirements. Selecting a familiar model without diagnosing the situation can produce an organized plan that misses the real problem.
Identify the type and scale of change
Organizational change can be strategic, operational, cultural, technological, or a combination. These types often overlap. A technology launch may also alter workflows, skills, decision rights, customer communication, and performance expectations.
Strategic
A change in direction, market, business model, or long-term positioning.
Operational
A change in processes, procedures, roles, or day-to-day execution.
Cultural
A change in shared values, norms, assumptions, and expected behaviours.
Technological
A change involving tools, platforms, automation, data, or digital capability.
The next distinction is incremental versus transformational. Incremental change improves what already exists. Transformational change changes the operating logic, capabilities, culture, or business model.
If the current model still works and needs improvement, the change is likely incremental. If the current model is no longer sufficient and the organization must operate differently, the change is likely transformational.
Choose the change approach
Fits when the destination is clear and the path is mostly known. It uses structured implementation, milestones, roles, training, controls, and reinforcement.
Fits when the situation is complex and the solution must evolve through pilots, short cycles, feedback, experimentation, and adjustment.
Fits when the main barrier involves meaning, beliefs, identity, trust, or competing interpretations. It uses inquiry, participation, and co-creation.
A hybrid approach is often appropriate. A program may use planned change for governance and rollout, emergent change for pilots and adjustments, and dialogic change for trust, meaning, and cross-functional alignment.
Select the framework based on the main risk
Prepare, move, and stabilize
Use Lewin when old routines must loosen, a new practice must be introduced, and the new way must become stable through routines, norms, systems, and reinforcement.
Mobilize broad organizational change
Use Kotter when change crosses functions and requires urgency, leadership alignment, a guiding coalition, momentum, visible wins, and cultural reinforcement.
Diagnose and support adoption
Use ADKAR when success depends on people adopting a new process, system, behaviour, or communication journey through Awareness, Desire, Knowledge, Ability, and Reinforcement.
Lewin organizes movement from the current state to a stabilized new state. Kotter mobilizes and sustains broad organizational change. ADKAR diagnoses and supports adoption.
A practical selection sequence
- Define what will change, for whom, and why.
- Identify whether the main change is strategic, operational, cultural, technological, or a combination.
- Decide whether the change is incremental or transformational.
- Determine whether the situation is best approached as planned, emergent, dialogic, or hybrid.
- Identify the main risk: weak alignment, unclear direction, low adoption, resistance, cultural conflict, lack of capability, or failure to sustain.
- Select Lewin, Kotter, or ADKAR based on the main risk and level of change.
- Use the corresponding application guide to turn the framework into an action plan.
Move from diagnosis to action.
Complete the Change Approach and Framework Selection Guide first. Then use the Lewin, Kotter, or ADKAR Application Guide that best fits the change.
Explore all four practical guides →Final takeaway
The strongest choice begins with the type of change, the level of uncertainty, and the main implementation risk. The framework should then guide specific actions, owners, measures, and review points rather than simply label the project.