70% of all change initiatives fail to achieve their goals. This often-cited figure from McKinsey research shows: change is hard -- not because of technology or strategy, but because of people. Those who neglect change management risk failed projects, frustrated employees, and wasted budgets.
This guide shows you how to systematically plan change processes, select the right models, and constructively overcome resistance. Whether it's a digitalization project, reorganization, or new software implementation -- with the right change management, resistance turns into acceptance.
What is Change Management?
Change Management (German: Veränderungsmanagement) is the structured approach to designing changes in organizations so that they are accepted by those affected and implemented sustainably. It's not just about processes and tools, but primarily about people and their reactions to change.
Change Management encompasses three core areas:
- Individual level: How do individual employees experience the change? What fears, questions, and needs do they have?
- Team level: How does collaboration change? What new roles and responsibilities emerge?
- Organizational level: Which structures, processes, and systems need to be adapted?
Project management deals with the "what" and "how" of a change (tasks, timeline, budget). Change management deals with the "who" -- the human side. Both belong together: a technically perfect project fails if those affected don't come along.
Why 70% of All Change Projects Fail
Before we talk about solutions, it's worth looking at the most common causes of failed change processes. Prosci research (benchmark study with over 6,000 projects) identifies five main reasons:
- Lack of leadership support (54%): If top management doesn't visibly support the change, employees don't take it seriously.
- Insufficient communication (43%): Those affected learn too late, too little, or not at all about what is changing and why.
- Inadequate involvement (39%): Changes are mandated "from above" without asking or involving those affected.
- Excessive speed (35%): Change takes time -- if pushed through too quickly, overwhelm and resistance arise.
- No clear vision (32%): If no one can explain what the change is good for, motivation to participate is lacking.
"People don't resist change. They resist being changed." -- Peter Senge
The 3 Most Important Change Management Models
In practice, three models have proven particularly effective. Each has its strengths -- and depending on the situation, you can combine elements from several models.
1. Lewin's 3-Phase Model
Kurt Lewin's model is the simplest and oldest change model. It divides change into three phases:
- Unfreeze: Question existing structures and behaviors, create willingness to change.
- Change: Introduce and test new processes, structures, or behaviors.
- Refreeze: Stabilize the new behaviors and integrate them into daily routine.
Ideal for: Manageable, clearly defined changes with a clear target state.
2. Kotter's 8-Step Model
John Kotter's model is the most well-known and detailed framework for change management. The eight steps:
- Create a sense of urgency: Why must we change now?
- Build a guiding coalition: Win influential supporters
- Form a strategic vision and initiatives: Where do we want to go and how do we get there?
- Enlist a volunteer army: Spread the message across all channels
- Enable action by removing barriers: Eliminate structural obstacles
- Generate short-term wins: Make quick wins visible
- Sustain acceleration: Use momentum to initiate further changes
- Institute change: Make new behaviors the norm
Ideal for: Major transformation projects (digitalization, reorganization, cultural change).
3. The ADKAR Model (Prosci)
The ADKAR model focuses on the individual level and describes five prerequisites that each person must go through:
- Awareness: Awareness that a change is necessary
- Desire: Desire to support the change
- Knowledge: Knowledge of how to implement the change
- Ability: Ability to apply new behaviors and processes
- Reinforcement: Reinforcement to sustainably anchor the change
Ideal for: Projects where individual behavior is decisive (software implementation, process changes).
| Criterion | Lewin | Kotter | ADKAR |
|---|---|---|---|
| Complexity | Simple (3 Phases) | Comprehensive (8 Steps) | Medium (5 Elements) |
| Focus | Organization | Leadership & Organization | Individual |
| Strength | Easy to understand | Very structured | Measurable & diagnostic |
| Weakness | Too simplified | Can seem rigid | Ignores group dynamics |
| Best for | Small changes | Major transformations | Software/Process changes |
7 Success Factors for Effective Change Management
Regardless of the chosen model, there are seven factors that determine success or failure:
- Visible leadership commitment: The executive board must not only approve the change but actively live it. A CEO who uses the new software themselves sends a stronger signal than any email.
- Clear, repeated communication: Rule: People need to hear a message 5-7 times before they internalize it. Use various channels (Town Halls, newsletters, team meetings, personal conversations).
- Turn those affected into participants: Involve key users, team leaders, and works councils early on. Those who can help shape the change will support it.
- Make quick wins visible: Show measurable successes within the first 30-60 days. This motivates and disarms skeptics.
- Plan sufficient time and resources: Change management is not a side project. Plan dedicated roles, budget, and time.
- Take resistance seriously: Resistance is a normal signal that people are perceiving the change. Don't ignore it -- use it as feedback.
- Ensure sustainability: Change is not finished with the go-live. Plan at least 3-6 months of follow-up support.
Implementing Change Management in 5 Phases
The following structure combines elements from Kotter and ADKAR into a pragmatic 5-phase approach that you can directly integrate into your project plan:
Phase 1: Analysis and Preparation (Week 1-2)
- Analyze and document the need for change
- Conduct a stakeholder analysis: Who is affected? Who has influence?
- Change Impact Assessment: Which areas are affected and to what extent?
- Identify risks: What resistance is to be expected?
- Assemble the change team and clarify roles
Phase 2: Vision and Communication (Week 2-4)
- Formulate the change vision: What will improve? What stays the same?
- Create a communication plan (channels, frequency, target groups)
- Brief leaders as change ambassadors
- Initial information to all affected parties (Town Hall, All-Hands)
Phase 3: Enablement and Piloting (Week 4-8)
- Develop and conduct training concept
- Identify and support pilot group
- Set up feedback channels (surveys, office hours, FAQ)
- Identify and communicate quick wins
Phase 4: Rollout and Support (Week 8-16)
- Gradual rollout (not everything at once)
- Change agents in each team as points of contact
- Regular pulse checks: How is the transition going?
- Actively manage and document resistance
Phase 5: Anchoring and Optimization (from Week 16)
- Measure and communicate successes
- Conduct Lessons Learned
- Update processes and training materials
- Follow-up and continuous improvement
Recognizing and Overcoming Resistance
Resistance is not an enemy -- it is a natural part of every change process. The question is not whether resistance will occur, but how you deal with it.
The 4 Most Common Types of Resistance
| Type | Cause | Expression | Strategy |
|---|---|---|---|
| Rational | Lack of information | "I don't understand why..." | Explain, provide data, transparency |
| Emotional | Fear of loss | "This will never work" | Listen, take fears seriously, provide reassurance |
| Political | Loss of power | Passive blockade, avoidance | Offer new roles, inclusion |
| Cultural | "That's how it's always been" | Insistence on old ways | Show quick wins, create role models |
Conduct an anonymous survey before the change project: "What concerns do you have regarding the planned change?" The answers give you a map of the resistance before it becomes a problem.
How AI Supports Change Management
Artificial intelligence can accelerate and improve the change management process on several levels:
- Automatic Stakeholder Recognition: AI tools like PathHub AI automatically identify all stakeholders affected by the change -- including often forgotten groups like works councils, data protection officers, or external partners.
- Risk Recognition: AI analyzes the project context and recognizes potential resistance and risks before they occur. Example: For an IT migration, the AI automatically warns of change fatigue if other projects are running in parallel.
- Create Change Roadmap: Instead of weeks of planning, AI generates a complete action plan with change-relevant phases, communication milestones, and training blocks.
- Communication Planning: AI suggests target group-specific communication measures -- different messages for leadership than for operational teams.
Checklist: Your Change Management Roadmap
Use this checklist as a starting point for your next change project:
- Change vision formulated in 2-3 sentences
- C-level sponsor identified and committed
- Stakeholder analysis conducted (all affected parties identified)
- Change impact assessment created (who is affected and to what extent)
- Communication plan with channels, frequency, and target groups
- Managers briefed as change ambassadors
- Training concept developed and scheduled
- Change agents / key users named in each affected team
- Feedback channels set up (surveys, office hours)
- Quick wins identified and anchored in the plan
- Resistance management strategy defined
- Success metrics established (how do we measure success?)
- Follow-up phase (3-6 months) scheduled
- Lessons Learned appointment in the calendar