The Emotional Change Curve

Every change you make in the business has two timelines. The operational one, which you can plan. And the emotional one, which you cannot. The second is longer, and it is the one that decides whether the change survives.

The curve describes what happens to performance after a change lands. Things get worse before they get better. That dip is not evidence the decision was wrong. It is what change looks like from the inside, and owners who read it as failure tend to abandon good decisions about three weeks before they would have started working.

What the model is

The shape is borrowed from Elisabeth Kübler-Ross's work on grief and was adapted for organisational change. The labels vary between versions. The pattern does not. There is a stall when the change is announced, a period of resistance, a low point, then a climb as people experiment and adjust, finishing above the old level if the change was worth making.

Two things about the shape matter more than the stage names. The dip is real and measurable, not a mood. Output falls, errors rise, the capable people go quiet. And people enter the curve at different points and travel it at different speeds. You have been thinking about this change for months. Your team heard about it on Tuesday. You are at stage four feeling pleased with yourself while they are at stage one working out what it means for their Friday.

Why it matters to an owner

Because you are the one who will lose your nerve. Nobody else in the business has the authority to reverse the decision, so the risk sits entirely with you.

At the trough you will be presented with evidence. Jobs are slower. Someone is threatening to leave. A customer has noticed. Your operations manager, who never complains, tells you quietly that it is not working. All of that is true, and none of it tells you the decision was wrong. It tells you that you are at week five.

There is a genuine judgement to make here, and it is not "hold the line no matter what". The useful distinction is between people struggling with the new way and the new way not doing what it was meant to do. If your team are slow, frustrated and making mistakes with the new system, that is the curve. If the system itself cannot produce the report you bought it for, that is a design fault, and no amount of resilience fixes it. Ask which one you are looking at, in those words, and answer honestly.

Two groups dip harder than everyone else, and both are worth watching. Supervisors and middle managers get it from both directions: they have to sell a change they had no part in designing while absorbing the complaints from the people doing the work. If your operations manager is the most negative person in the building at week four, that is the position talking, not the person. And your longest-serving staff dip deepest, because they have the most invested in the old way and they were usually the ones who built it. Their resistance is not disloyalty, it is competence with nowhere to go.

The cost of reversing at the trough is higher than most owners price in. You do not simply go back to where you were. You teach everyone that if they hold out for six weeks, changes go away. The next one will be harder, and they will know it.

A worked example

Illustrative, to show the shape and the timing rather than to promise a result. A fourteen-person installations firm moves from paper job sheets to a job management app. The owner has been researching it for four months.

• Weeks 1 to 2. Announced at a team meeting, training booked. Nobody objects in the room. Two engineers carry on filling in paper as well, "just in case". Invoicing lag, which averaged 11 days, does not move.
• Weeks 3 to 5. Resistance arrives, not as argument but as friction. Photos not uploaded. Jobs closed with no notes. The office manager is re-typing what the app was bought to stop her re-typing. Invoicing lag stretches to 15 days because information now arrives in two places.
• Week 6. The trough. A long-serving engineer says he did not sign up for this. The owner has a bad Friday and seriously considers scrapping it.
• Weeks 7 to 10. The owner stops running training and starts running a ten-minute stand-up on Monday about what is not working. Three small changes come out of it, all suggested by the engineers. Two of them take five minutes to fix.
• Weeks 11 onwards. Invoicing lag settles at 4 days. That is roughly a week of turnover permanently released back into the bank account, and the arguments about what was agreed on site largely stop.

The change did not fail in week six. It was in week six. The only thing that separated this from the version where it gets quietly dropped was the owner knowing the shape of the graph.

How to apply it this week

1. Name where each person is, in writing. List everyone affected by your current change and put a number 1 to 5 against them. The spread will surprise you, and it tells you who needs what.
2. Publish the dip before it happens. Say plainly: "For about six weeks this will be slower and more annoying than what we do now. That is expected. Here is when it should improve." An owner who predicts the dip owns it. An owner who is surprised by it looks wrong.
3. Pick one number and watch it weekly. Invoicing lag, jobs per day, complaints, whatever the change was meant to move. Without it you are managing on mood, and mood at week five is always bad.
4. Book the week six conversation now. Put a meeting in the diary for the middle of the trough, before the trough arrives. It is much easier to hold a decision you scheduled a review of than one you are defending in the moment.
5. Ask, do not tell, at the low point. "What is the most annoying part of this?" gets you the three fixable things. "Why isn't everyone on board?" gets you silence.
6. Say out loud when you have climbed out. Most changes are never declared finished, so nobody gets the reward of having got through it. Mark it, briefly, with the number that moved.

The mistake most owners make

They treat the announcement as the change. The decision was made, the email was sent, the training happened, so the job is done. Everything after that gets filed as an attitude problem.

The second mistake, and the more expensive one, is letting the change die at the trough without ever saying so. Nobody announces the reversal. The old spreadsheet quietly comes back, the app licence gets cancelled at renewal, and the whole thing is never discussed. That is worse than deciding to stop, because there is no learning in it, only a business that now knows changes are optional.

The questions to sit with

• Out of 10, how confident are you that the resistance you are seeing is the curve rather than a fault in the plan? What would move that number?
• Where on the curve were you when you announced it, and where were they?
• Think of the last change you started and did not finish. What week did it die, and what did the team learn from watching that?
• What single number would tell you, honestly, whether the current change is working?

This sits at the centre of the Leading Change work. Most owners do not have a change problem, they have a week six problem. Knowing the shape of the curve is what lets you hold a good decision through the part where it feels like a bad one.