Start with the case for change
A change paper begins with a clear statement of why the organization must change and what the change will be. Cover three points: the trigger (a market shift, a performance gap, new technology, a merger), the desired future state, and the gap between the two. Support the gap with data, such as falling customer retention or slow decision cycles.
Distinguish the type of change, because it determines the approach.
| Type | Description | Example |
|---|---|---|
| Incremental | Gradual improvements within the current model | Process improvement in a call center |
| Transformational | Fundamental change in strategy, structure or culture | A retailer moving from stores to online |
| Planned | Deliberate, managed from the top | Introducing a new ERP system |
| Emergent | Arises from continuous adaptation at many levels | Teams adopting new tools informally |
Lewin's three-stage model
Kurt Lewin described change as unfreeze, change, refreeze. It is simple and a good way to frame the paper, though it can sound too linear for a modern organization.
| Stage | Goal | Actions |
|---|---|---|
| Unfreeze | Create readiness by loosening current beliefs and habits | Share data on the need; show the cost of staying still; involve staff early |
| Change | Move to new behaviors and structures | Train, pilot, clarify roles, adjust processes and systems |
| Refreeze | Make the new way stick | Reward new behaviors, update policies, embed in performance reviews and onboarding |
Lewin's force field analysis lists driving forces (pushing toward change) and restraining forces (pushing against) and scores them. Strategy is to strengthen drivers and, more importantly, reduce restraints, because pushing harder on drivers often raises resistance.
Kotter's eight steps
John Kotter's model is more detailed and widely used in MBA courses. It stresses urgency, coalition and communication.
| Step | What it means | Failure if skipped |
|---|---|---|
| 1. Create urgency | Show why change cannot wait | Complacency; no one acts |
| 2. Build a guiding coalition | Assemble influential leaders | No credibility; change seen as one person's idea |
| 3. Form a vision | Describe a clear, simple future | Confusion and scattered effort |
| 4. Communicate the vision | Repeat it in many forms and by example | People do not understand or believe it |
| 5. Remove obstacles | Change systems, structures and blockers | Willing people are stopped by old rules |
| 6. Create short-term wins | Show visible progress in 6 to 12 months | Momentum fades |
| 7. Build on the change | Do not declare victory early | Old habits return |
| 8. Anchor in culture | Link the change to how things are done here | Gains reverse when leaders move on |
Do not just list the steps. Apply each to your case and say which were done well, which were missed and what happened as a result.
ADKAR: the individual view
Organizations change only when individuals do. The ADKAR model, from Prosci, describes five outcomes a person needs in order: Awareness of the need, Desire to take part, Knowledge of how to change, Ability to carry out the new behaviors and Reinforcement to sustain them. It is a diagnostic tool: find where people are stuck.
ADKAR diagnosis (hypothetical, a new scheduling system)
A survey of 80 staff finds: 90 percent aware of the reason for the change; 55 percent want to use the system; 70 percent know how; 40 percent can do it confidently. Desire and Ability are the weak links.
The fix is different for each: address desire by explaining what is in it for staff and responding to concerns; address ability with hands-on practice and floor support rather than a longer presentation.
Understand resistance instead of fighting it
Resistance is information. People resist for reasons that usually make sense from their position.
| Source | What it sounds like | Response |
|---|---|---|
| Fear of loss | I will lose status or my job | Be honest about impact; offer retraining and clear paths |
| Lack of trust | We were told this last time and nothing changed | Show visible, consistent action and keep promises |
| Poor understanding | I do not see why this is needed | Share data and listen to concerns |
| Disagreement | This will not work | Take the feedback seriously; it may improve the plan |
| Change fatigue | Another initiative | Limit simultaneous changes; show how this one connects |
Working on this assignment now? Get a price for help with your paper.
Get an instant quoteA worked change plan: a new inventory system
A hypothetical regional retailer with 80 store employees is replacing its manual stock system with a new one. The plan below shows how the models turn into actions.
| Group | Impact | Likely concern | Action |
|---|---|---|---|
| Store managers (12) | High: daily routines change | Loss of control, workload during switch | Involve in design; super-user role; protected training time |
| Stock clerks (30) | High: new tasks and tools | Skills, job security | Hands-on practice; clear message that roles continue; peer coaches |
| Buyers (6) | Medium: new data and reports | Trust in the numbers | Parallel run for two months; reconcile differences openly |
| Head office finance | Medium | Reporting changes | Early look at reports; agreed definitions |
Communication runs on a timeline. Weeks 1 to 2: why change, with data on stock-outs; weeks 3 to 6: demonstrations and a question forum; weeks 7 to 8: practice in a pilot store; week 9: go-live in the pilot; weeks 10 to 14: roll out in waves of three stores. The plan matches Kotter's steps (urgency, coalition, vision, communication, removing obstacles, short-term wins) and Lewin's stages.
Measuring readiness and adoption
Measure before and during the change, not just at the end.
| Measure | When | Example | Use |
|---|---|---|---|
| Readiness survey | Before launch | Average of 3.2 out of 5 on I understand why we are changing | Target communication where scores are low |
| Training completion | During | 76 of 80 trained by week 8 (95 percent) | Follow up the gaps |
| Adoption rate | After go-live | 68 of 80 staff use the system daily (85 percent) | Find who is not using it and why |
| Business result | 3 to 6 months | Stock-outs fall from 6 percent to 3 percent of lines | Show the benefit and reinforce |
Adoption rate is users active divided by users expected, so 68 divided by 80 is 85 percent. Pair it with a result measure; a system can be widely used and still fail to deliver the benefit.
Why change fails: reading the symptoms
| Symptom | Likely cause | Response |
|---|---|---|
| People attend training but do not use the new process | Weak desire or poor fit with real work | Ask why; change the process or the incentives |
| Early wins, then slide back | Change not anchored; old rewards remain | Update measures, policies and onboarding |
| Rumors fill the gaps | Too little two-way communication | More frequent, honest updates; open forums |
| Middle managers stall | No role in the change; fear of losing authority | Give them ownership and development |
| Change team burns out | Too many simultaneous initiatives | Sequence and stop lower-value projects |
Writing about failure shows that you understand mechanisms. If your case already failed, use a model as a diagnosis: which Kotter step was skipped, and what evidence shows it?
Design the plan and measure it
| Element | What to include |
|---|---|
| Stakeholder map | Who is affected, how much, and how supportive; plan actions for each group |
| Communication plan | Audience, message, channel, sender and timing, using two-way channels |
| Training and support | What people need to be able to do, delivered when they need it |
| Governance | Sponsor, change team, decision rights and escalation |
| Measures | Leading indicators (training completion, adoption) and lagging results (productivity, customer satisfaction) |
| Reinforcement | Rewards, policies, and manager coaching that lock in the change |
Set specific targets, such as 85 percent of staff using the system within eight weeks and a 10 percent fall in scheduling errors within six months, and a review date. Mention risks and contingencies, such as a rollback plan if early results are poor.
- Choose a model for a reason Explain why Kotter or Lewin fits your case better than the alternative.
- Apply, do not describe Show how each step plays out in the organization.
- Cover people, not only process Resistance, communication and training make or break change.
- Measure outcomes Say how you will know the change worked.
If you want help with a change paper or project, you can order MBA assignment help.