Insights
The change curve describes how people’s morale and performance tend to move when something they rely on changes. Here is where it came from, how to read each stage and what leaders should do at each point to make the dip shorter and shallower.
By Christopher Fagan, Managing Partner, PEF Consulting Partners
Delivered for and alongside
















The change curve is a simple model of how people tend to react when something they rely on changes: an early drop in morale and performance, a low point, then a gradual climb as they test the new way and commit to it. Leaders use it to plan support for each stage rather than expecting instant acceptance.
It is one of the most borrowed ideas in change management and one of the most misused. Used well, it stops a programme panicking when performance dips after go live. Used badly, it becomes a way of labelling anyone who raises a fair concern as being in denial.
In this article
The model starts with Elisabeth Kübler Ross, a Swiss born psychiatrist who worked in the United States, and her 1969 book On Death and Dying. Drawing on conversations with terminally ill patients, she described five stages that people often went through: denial, anger, bargaining, depression and acceptance. The book was about dying, not about reorganisations or new finance systems.
Management trainers and consultants later borrowed the shape for organisational change, on the reasoning that losing a familiar job, team or way of working triggers a smaller version of the same reactions. The stages were redrawn as a curve, with time along the bottom and morale or performance up the side. That picture is what most people now mean by the Kübler Ross change curve.
It is worth being clear about what the model is: a heuristic, a useful way of thinking, not a law of human behaviour. Grief researchers have found little evidence that people move through fixed stages in a set order, and Kübler Ross herself, writing later with David Kessler in On Grief and Grieving (2005), said the stages were never meant to be a tidy sequence that everyone follows.
In practice people skip stages, loop back and sit in two at once. Treat the curve as a prompt for what to look for, not as a prediction of what will happen.
There is no single official version. Most organisational versions compress the original five stages into four or five phases, and the labels vary from one source to the next. The version below is the one we find most practical, because each stage calls for a different response from leaders.
The horizontal axis is time, and the vertical axis is usually labelled morale, competence or performance. The exact shape matters less than two practical points. Performance usually gets worse before it gets better, and different groups will be at different points on the curve at the same moment.
The emotional response to change is much easier to manage when you know what each stage looks like on the ground. The table maps each stage to the signs you are likely to see and the leadership response that tends to help. Copy it into your change plan and add a column for the groups you think are at each stage.
| Stage | Signs you will see and hear | What leaders should do |
|---|---|---|
| Shock and denial | Quiet briefings with few questions. Comments such as “this will never actually happen”. Business as usual carries on and few people read the updates. | Explain plainly what is changing, why, when, and what is not changing. Repeat it through line managers rather than relying on one announcement. Give dates and specifics rather than slogans. |
| Frustration and resistance | Pushback in meetings, challenges to the business case, requests for exceptions, informal groups forming against the change, talk of leaving. | Listen properly and log every objection. Fix the ones that expose real design problems and say so publicly. Be firm about what is not negotiable and explain why. |
| The low point | Output drops, errors and workarounds rise, help desk queues grow, people disengage or go quiet. | Put extra support where the work happens: floor walkers, quick fixes and a clear route to escalate. Protect the team from new demands. Do not reverse the decision because of a dip you could have predicted. |
| Exploration | Questions move from why to how. People share tips, ask for more advanced training and suggest improvements. | Give people room to experiment. Capture good workarounds and spread them. Recognise early adopters in front of their peers. |
| Acceptance and commitment | The new way is used without prompting, old spreadsheets and reports fall away, and people defend the new process to newcomers. | Switch off the old way for good. Hand ownership of improvements to the business. Record lessons learned and move support into business as usual. |
Take a hypothetical business with a finance team of 40 people replacing a finance system it has used for 15 years. The leadership team has known about the decision for six months by the time it is announced. Most of the finance team hear about it for the first time at an all staff briefing.
In the first few weeks the accounts payable team sit in shock and denial, and some assume the project will stall like the last one. The management accountants, who built most of the spreadsheets around the old system, move quickly into frustration. They question whether the new system can produce the reports they rely on.
Go live lands at the start of a quarter, and the first month end close on the new system is the low point. Close takes longer, reconciliations throw up errors, and two experienced people start talking about leaving. A director suggests running the old system in parallel for another six months.
A programme that understands the curve has planned for this. It has floor walkers in the finance office for the first two closes as part of a proper hypercare period, a daily fifteen minute call to clear issues, and a short list of fixes that can be made in days rather than weeks. It also holds the line on switching off the old system, because a long parallel run keeps everyone at the bottom of the curve for longer.
By the third close the questions have changed from why to how. By the sixth, the team is asking for reports the old system could never have produced. That is acceptance, and it is the moment to hand ownership of further improvements back to the finance team.
The model earns its place when it changes what you plan and budget for. Six steps make it practical.
The curve is most useful when a change has real personal impact: restructures, new roles, relocations, outsourcing, mergers and new core systems that change how people spend their day. It helps sponsors hold their nerve through the dip, and it gives line managers a shared language for what they are seeing.
It is much less useful for small changes with little personal impact, such as a new form or a reporting tweak, and for changes people actively asked for. It is no help as a timetable either, because nobody can promise that a team will reach acceptance by March.
Where the change curve stops being useful altogether is when it is used to explain away every objection. Resistance is sometimes the most valuable feedback a programme gets. If a team says the new process cannot handle a case they deal with every week, check before you file it under frustration.
The curve describes how people feel. It does not tell a leadership team what to do next, or explain why one particular person is stuck. That is why it works best alongside other models, each covering a different part of the problem.
For a broader view of how these pieces fit together, start with our guide to what change management is and how it works. It sets out the process end to end and where each model earns its keep.
The curve is not a separate workstream with its own slide deck. It should shape the plan, the support budget and the criteria for go live. A programme that expects the dip staffs up for it, while one that does not tends to read the dip as failure and make expensive decisions in a hurry.
Christopher Fagan has spent 19 years delivering systems and transformation. Finance system replacements, whether on Oracle, Microsoft Dynamics, NetSuite, Sage or SAP S/4HANA, are where the dip after go live is easiest to see and easiest to plan for. Our change management and adoption work builds this in from the start: we design and build alongside your team, so the people who have to live with the change help shape it rather than receiving a finished plan.
The change curve is a model of how people typically respond to significant change at work. Morale and performance tend to fall after a change is announced and introduced, reach a low point, then recover as people explore the new way and commit to it. Leaders use it to plan the right support at each stage instead of expecting instant acceptance.
Kübler Ross’s original five stages were denial, anger, bargaining, depression and acceptance, describing how terminally ill patients responded to their situation. Organisational versions usually adapt these into shock and denial, frustration and resistance, a low point, exploration, and acceptance and commitment. The labels vary between versions, but the shape is the same: a dip, then a recovery.
There is no standard timescale. It depends on how much the change affects someone’s daily work, how well it is explained and supported, and what else is changing at the same time. A minor process change might take weeks, while a restructure or a new core system can take months. Plan support around evidence of where groups actually are, not a fixed timetable.
Only loosely. It began as a description of how dying patients responded to their situation, and grief researchers have found little evidence that people pass through fixed stages in order. It is best treated as a heuristic: a useful prompt for what to look for and how to support people, rather than a scientific prediction of how anyone will behave.
Group people by how much the change affects them, estimate where each group is on the curve, and plan support for that stage: information during shock, listening during resistance, practical help at the low point and room to experiment during exploration. Check your estimates with pulse surveys and help desk data, and keep support in place until well after go live.
Related reading: What is change management?, The ADKAR model explained, Kotter’s 8 step change model and Change readiness assessment.
We help leadership teams plan the people side of system and organisational change, then stay with them through go live and the dip that follows. Tell us what is changing and we will give you a straight view of where the risks are.
Book a confidential conversation
Sources: Elisabeth Kübler Ross, On Death and Dying, 1969; Elisabeth Kübler Ross and David Kessler, On Grief and Grieving, 2005
Written by Christopher Fagan
Managing Partner, PEF Consulting Partners
Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.
Where next