Change Curve: How to Use It Without Predicting Employee Behavior

Decide what the Change Curve can—and cannot—help you decide

HR and transformation leaders need a way to discuss possible responses to change without turning a simplified model into a forecast of employee behavior. The Change Curve describes the typical emotional journey individuals may go through when faced with change, but that description does not tell you where a particular team is, what caused its response, or what will happen next. The practical risk is treating a label as a diagnosis: communication becomes generic, legitimate objections look like resistance, and support is chosen before the underlying barrier is understood.

Use the model as a provisional lens for one defined organizational question:

• What are people trying to understand? Look for questions about the business rationale, timing, role expectations, or consequences.
• What is making the change harder to act on? Separate uncertainty, missing capability, process friction, capacity constraints, and disagreement with the decision.
• What support choice follows from what you observe? Choose clarification, listening, training, manager enablement, process adjustment, or escalation only after naming the signal that supports it.

The decision is not whether a team has reached a particular stage. The decision is whether the model helps you ask better questions about a defined change, and whether those questions lead to proportionate organizational action.

Trace the Change Curve from grief model to workplace framework

The model’s history matters because its origin shapes the assumptions people may carry into workplace discussions. The Change Curve was initially developed by Elisabeth Kübler-Ross in 1969 to describe stages of grief in terminally ill patients, and its principles were later applied to personal and organizational change. That later application gave managers a familiar way to talk about reactions during a transition, but it also transferred a framework from one setting into another with different choices, incentives, relationships, and consequences.

A workplace transition is not the same situation as terminal illness. Employees may question the business case, ask for a different implementation route, negotiate timing, continue with existing practices, or identify a flaw in the proposed design. Those responses can contain useful information about the change itself, not merely an emotional obstacle to be moved through.

Use the history as an audit question: Which assumptions are you importing when you use the model? If the answer assumes that every person must pass through the same emotional sequence and eventually accept the proposed state, the framework is already too narrow for the decision. If the answer is that the model provides language for exploring possible reactions while leaving room for disagreement and revision, its use is more bounded.

Compare the workplace versions before interpreting a team response

Workplace versions of the Change Curve do not use one consistent set of stages: the selected sources describe six stages, four stages, and five stages. The labels, sequence, and implied destination can therefore change depending on the version placed in front of your team.

The versions include:

• Six stages: denial, self-criticism, confusion, acceptance, solutions, and commitment.
• Four stages: shock, anger, acceptance, and commitment.
• Five stages: a presentation of five natural emotional responses associated with the Kübler-Ross Change Curve.

These variants are not interchangeable. A label such as confusion invites different questions from a label such as anger. A sequence ending in commitment may suggest a stronger destination than a sequence that simply describes an initial response. A diagram may also compress several distinct experiences into one downward or upward movement.

Before using a version in a change plan, record three details:

1. The source and version: Identify the diagram or explanation your team is using and count its stages.
2. The meaning of each label: Define what the label is intended to describe and what it does not establish.
3. The decision attached to it: State whether the model will inform communication, listening, training, manager support, or another limited choice.

Do not ask employees to select their stage. Ask what they are experiencing, what they need to understand, and what is obstructing action. The version can shape your questions, but it should not determine the answer.

Translate stage language into observable organizational signals

Organizational signals are more useful than stage labels because signals can be examined against the change context. The model can help managers and leaders anticipate how individuals may react to change and provide targeted support and interventions, but a tentative interpretation still needs observable indications and direct listening.

Translate broad stage language into questions about work:

• Possible shock or denial: Are teams missing basic information, disputing what has been decided, or treating the change as optional because the message was unclear?
• Possible anger or self-criticism: Are objections focused on loss of expertise, workload, trust, decision rights, or the way the change was handled?
• Possible confusion: Do managers and employees understand the new priorities, roles, workflow, systems, and timing well enough to act?
• Possible acceptance: Are teams acknowledging the direction while still identifying conditions that must be resolved before adoption?
• Possible solutions or commitment: Are teams testing workable practices, raising implementation improvements, and taking ownership of the new way of working?

These are prompts, not classifications. The same observable behavior can have different causes. Silence may reflect agreement, uncertainty, low trust, lack of time, or a belief that speaking up will not change the decision. Repeated workarounds may signal inadequate training, a poor process design, conflicting incentives, or a deliberate choice to protect service quality.

Use a three-part note for each signal: what you observed, what explanations remain possible, and what question will distinguish among them. That structure prevents the curve from closing the inquiry too early. It also gives managers a practical basis for choosing a support response without telling employees how they feel.

Match communication and support to what the evidence shows

Communication and support should follow the signal you can describe, not the stage you have assigned. For business-level change messages, employees want to hear from someone at the top of the organization or their division. A senior sponsor should therefore explain the business reason, the decision being made, the risks of not changing, and what remains open for input when the message concerns enterprise direction.

A responsible response path has four parts:

1. Clarify the decision. State what is changing, why it is changing, when it takes effect, and what has not been decided. Avoid presenting a benefit as certain when the organization still needs to test it.
2. Create a listening route. Give teams a way to raise operational concerns, conflicting priorities, capability gaps, and unintended effects. Assign an owner to sort questions that need an answer from issues that require a design change.
3. Choose proportionate support. Use manager briefings, targeted learning, job aids, practice time, process clarification, or peer support when the signal points to a specific barrier. Do not prescribe emotional support as a substitute for fixing an impractical workflow.
4. Review and adjust. Set a date to examine unanswered questions, recurring workarounds, participation patterns, and adoption obstacles. Keep the model as a prompt for inquiry rather than a reason to dismiss contrary information.

The model can provide a roadmap for tailoring communication, training, and support to perceived employee or team responses, but the response must remain conditional. If the observed issue is a flawed decision, limited capacity, or conflicting incentives, better communication alone is not the remedy.

Keep the Change Curve distinct from implementation models

Implementation models answer a different question from a possible-response lens. Lewin’s change model has three stages—unfreezing, movement, and refreezing—and additional information is needed to adapt those general steps to specific situations.

The distinction is practical:

• A response lens helps you explore how a team may be experiencing a transition and what questions or support needs deserve attention.
• An implementation model helps you organize the work of preparing for, executing, and stabilizing a change.

Do not use the curve as a substitute for an implementation plan. A team may understand the reason for a change but lack the system access, decision rights, practice time, or manager capacity needed to implement it. Another team may understand the process and still challenge the direction because the proposed change creates a material operational problem.

Use the two kinds of model in sequence only when their roles are clear. First define the organizational change and the decision it requires. Then use a response lens to formulate questions about communication and support. Finally, use an implementation approach to assign work, ownership, timing, and review. The models can inform one another, but they should not be treated as one combined prediction of how employees will move.

Stress-test the model’s assumptions before using it

The model’s main risk appears when a flexible discussion aid becomes a universal explanation. A critical review states that the Change Curve presents a universal and linear view of emotional responses and a narrow interpretation of resistance to change. That framing can make a varied organizational response look like a predictable journey with one acceptable endpoint.

A separate critique argues that applying a model about coping with death to organizational change is problematic because organizational change often involves choices, including maintaining the status quo. Employees may challenge the decision, propose a different design, or identify consequences that leaders have not considered. Those responses should not be reduced automatically to reluctance that must be overcome.

The model also carries a risk of conceptual spillover. A systematic narrative review examined how Kübler-Ross’s five-stage model was presented on the internet; 72 websites were eligible for inclusion, and 44 of those websites, or 61.1%, addressed the model. The review states that the five-stage grief model has received significant criticism and that inaccurate portrayals may lead bereaved individuals to feel they are grieving incorrectly and may result in ineffectual support. That finding concerns grief-model portrayals, not a direct measure of workplace adoption, but it reinforces the need to label the framework carefully and avoid presenting it as a rule.

Run this stress test before adding the model to a change plan:

• Universality: Could the same change produce different responses across roles, locations, managers, or operating conditions?
• Linearity: Could a team revisit an earlier concern after new information, a system failure, or a change in scope?
• Resistance: What practical, ethical, or strategic information might disagreement contain?
• Destination: Is the organization allowing the proposed change to be questioned or redesigned?
• Actionability: Will the model produce a specific listening or support action, or merely a label?

If the framework narrows the questions, remove it from that decision. A simpler description of the observed work problem is more useful than a familiar diagram applied too literally.

Use D³-Org to decide whether the curve adds value

Use D³-Org as an audit of the Change Curve before it enters a change plan. Here, the three parts concern the model itself: identify the version and assumptions, test the inference invited by its labels, and set a boundary for any resulting use.

Audit the version and its assumptions

Start by naming the workplace account under review. One description uses denial, self-criticism, confusion, acceptance, solutions, and commitment. Another uses shock, anger, acceptance, and commitment. A third identifies five stages. These accounts do not establish one fixed workplace sequence, so record the version and its terms before interpreting an organizational signal. Do not combine labels from different accounts and present them as a single standard model.

The model’s history also matters. The Change Curve was initially developed by Elisabeth Kübler-Ross in 1969 to describe stages of grief in terminally ill patients, and its principles were later applied to personal and organizational change. That origin does not by itself show that a workplace team follows the same pattern. It is a reason to examine the assumptions being carried into the organizational use of the curve.

Test the inference invited by the labels

Separate an observation from the interpretation placed on it. Questions, participation patterns, workflow friction, and requests for more practice are organizational signals to examine; a stage label is an interpretation layered on top. Ask whether the chosen version helps frame a question about communication, listening, or support, or whether it replaces those questions with a category.

This distinction matters because a critical review describes the Change Curve as presenting a universal and linear view of emotional responses and a narrow interpretation of resistance to change. Organizational change can also involve choices, including maintaining the status quo. A team questioning a proposed change may therefore raise an issue about its rationale, process, or consequences; the curve alone does not establish which explanation applies. If a label is doing the explanatory work without further observation, reject that inference.

Set a boundary before using the model

Finish the audit by writing a limited use statement: name the version, the organizational observation, the question it may help examine, and the decision under review. Keep the use focused on possible communication, listening, or support needs. Do not turn a label into a prediction about what an employee will do, a requirement that every person pass through the stages, or a reason to treat acceptance as the only valid result.

Keep conceptual jobs separate. Lewin’s change model describes unfreezing, movement, and refreezing, and additional information is needed to adapt those general steps to specific situations. The Change Curve should not be asked to supply that implementation sequence merely because both models use stage language.

D³-Org earns a place only when this audit produces a clear version, a defensible organizational question, and a stated limit on inference. If it cannot do that, retain the observable signals and leave the curve out of that decision.

Recognize when organizational interpretation is not enough

Organizational interpretation has a boundary when the situation involves more than communication, adoption, capability, or process design. Stop using the model as the primary decision tool when you encounter:

• reported distress that is affecting the person’s ability to function;
• a safety concern or a credible risk of harm;
• serious impairment that requires more than workplace support;
• clinical symptoms or a request for mental-health assessment;
• employment, accommodation, disciplinary, privacy, or legal issues.

Route those matters through the relevant organizational safeguards and specialist pathway. Keep the change plan focused on what the organization can clarify, adjust, support, and review. Do not ask managers to interpret symptoms, assign a psychological stage, or use a change diagram to justify an employment decision.

This boundary also protects the change discussion itself. A team may need a clearer process, a safer escalation route, or a different business decision even when a person is receiving separate support. Keep those questions distinct so organizational action is not delayed by an inappropriate interpretation of the curve.

Audit the Change Curve Before It Shapes a Change Plan

A responsible use decision is straightforward: keep the model when it helps you examine observable signals and choose a proportionate communication or support response; set it aside when it labels employees, assumes a fixed sequence, or prevents legitimate disagreement with the change.

Before you use the framework, confirm four conditions:

1. You have named the organizational decision the discussion must support.
2. You have identified the version and defined its labels as tentative prompts.
3. You have separated observed signals from assumptions about emotion or motivation.
4. You have assigned owners for communication, listening, support, and review.

The result of this audit is a bounded planning choice: use the labels only where they sharpen a question about the change, and drop them when they obscure what the organization can observe. For questions involving individual mental health, safety, or legal suitability, a qualified professional should decide the appropriate response. Your organizational task is to make the change understandable, listen for information that can improve the design, and connect support to the barrier you can actually describe.

Practical questions leaders ask before using the Change Curve

Is the change curve an evidence-based prediction of how employees will respond?

No. It is a provisional discussion aid, not a validated forecast of individual or team behavior. Workplace versions use different stages, and critical reviews caution that the model can impose a universal, linear sequence. Test any interpretation against observable signals and direct listening.

Should employees be asked to identify which stage they are in?

Generally, no. Stage labels can narrow the conversation or make people feel categorized. Ask what they understand, what is obstructing action, what concerns they have, and what support would address the specific barrier. Record observations and alternative explanations instead of assigning a stage.

How should leaders respond when employees challenge the proposed change?

Treat the challenge as information to investigate, not automatic evidence of resistance. Clarify whether the concern involves the business rationale, workload, capability, process design, trust, or a practical risk. Keep a route for escalation and reconsider the design when the objection identifies a material problem; communication alone may not resolve it.

How is the change curve different from Lewin’s change model?

The change curve is used as a tentative lens for exploring possible responses and support needs. Lewin’s model—unfreezing, movement, and refreezing—organizes the broader implementation process. The first can inform questions about communication and support, while the second helps structure execution; neither should be treated as a prediction of how employees will move through change.

Can the change curve be used to diagnose an employee’s mental health?

No. Route those matters through the relevant specialist or organizational safeguard, while keeping the change plan focused on communication, process, capability, support, and implementation conditions.