Change Management Frameworks for Process Redesign
A reference guide to the structured approaches used to manage organizational transitions, stakeholder resistance, and adoption of redesigned workflows.
Why Change Management Matters
Process redesign projects frequently fail not because the redesigned process is technically flawed but because the people who must operate the new process do not adopt it effectively. Resistance, misunderstanding, inadequate training, and lack of management reinforcement can all cause a technically sound redesign to produce disappointing results.
Change management addresses the human dimension of process transformation — the transition from an existing way of working to a new one. It involves communicating the reasons for change, preparing people for new roles and responsibilities, managing the anxiety and uncertainty that accompany disruption, and reinforcing the new behaviors until they become routine.
Organizations that integrate change management with their process redesign efforts consistently report higher adoption rates and faster return to target performance levels than those that treat technical redesign as sufficient on its own.
Kotter 8-Step Model
John Kotter's 8-Step model, developed through research on organizational transformation, describes a sequence of actions that effective change efforts tend to follow. The model emphasizes creating urgency before building structures, and anchoring change in culture before declaring success.
- Create a sense of urgency. Help people understand why the current state is unsustainable and why change is necessary now rather than later.
- Build a guiding coalition. Assemble a group of influential people with the authority and credibility to lead the change initiative.
- Form a strategic vision and initiatives. Develop a clear picture of what the changed state looks like and how it will be reached.
- Enlist a volunteer army. Build broad engagement beyond the core coalition — change succeeds when a critical mass of people are actively participating, not just complying.
- Enable action by removing barriers. Identify and address structural or systemic obstacles — policies, legacy systems, hierarchies — that prevent people from acting on the change.
- Generate short-term wins. Plan for and celebrate early victories that demonstrate progress and build credibility for the change effort.
- Sustain acceleration. Use momentum from early wins to drive further change before declaring the work complete.
- Institute change. Anchor the new ways of working in culture by connecting them to organizational identity and performance management systems.
Kotter's model is most appropriate for large-scale organizational transformations where cultural change is as important as process change.
ADKAR Model
ADKAR is an individual-focused change model developed by Prosci. The acronym represents five building blocks that an individual must progress through to successfully adopt a change:
- Awareness of the need for change
- Desire to support and participate in the change
- Knowledge of how to change (skills and information)
- Ability to implement new behaviors and practices
- Reinforcement to sustain the change
ADKAR's value is in its diagnostic application. If adoption is failing, mapping employees to the ADKAR model identifies where the gap lies. Resistance at the Awareness stage requires different interventions than resistance at the Ability or Reinforcement stage.
ADKAR is particularly useful for process redesign projects because it provides a structured framework for designing training, communication, and support activities that correspond to specific gaps in individual readiness.
Lewin Three-Stage Model
Kurt Lewin's model describes organizational change as a three-phase process using a freezing metaphor: Unfreeze, Change, Refreeze.
- Unfreeze. Prepare the organization to accept that change is necessary. This involves challenging the current equilibrium — making the case that the status quo is no longer acceptable — and creating psychological safety for transition.
- Change. Implement the new process, roles, or behaviors. This is the transition phase, characterized by uncertainty and the learning curve associated with new ways of working.
- Refreeze. Stabilize the organization in the new state. The new process becomes the new standard, is embedded in training and performance management, and replaces the old way of working as the default.
Lewin's model is simpler than Kotter or ADKAR and is most useful as a conceptual frame for communicating the change journey to leadership. Its limitation is that it does not provide the granular action steps that practitioner-facing frameworks like ADKAR do.
Managing Resistance
Resistance to process change is a predictable phenomenon, not a sign that the redesign is poorly conceived. Common sources of resistance include:
- Loss of familiar routines and the comfort associated with mastery of current processes
- Concerns about job security, especially when redesign involves automation or headcount changes
- Skepticism based on past change initiatives that were poorly managed or abandoned
- Disagreement with the direction or rationale for change
- Insufficient involvement in the redesign process, creating a sense of imposition
Effective responses to resistance include early and transparent communication about the reasons for change, involvement of frontline staff in redesign decisions, explicit acknowledgment of the difficulty of the transition, and consistent leadership behavior that models the new way of working.
Measuring Adoption
Adoption measurement determines whether people are actually using the new process rather than reverting to old habits. Relevant indicators include:
- Compliance rates — what percentage of process instances follow the new procedure
- Error rates and rework volumes — high rates often indicate that people lack confidence or skill in the new process
- Training completion rates across the affected population
- Manager observation and coaching logs
- Self-reported confidence assessments from frontline staff
Adoption measurement should be built into the project plan from the beginning, not added retroactively when adoption concerns arise. See the Performance Metrics guide for context on integrating adoption indicators into a broader metrics framework.