3.4 Enterprise Change Sequencing and Readiness
Key Takeaways
- Change sequencing translates strategy into phases that respect readiness, capacity, dependencies, and stakeholder impact; named models include Lewin, Kotter, ADKAR, and Bridges.
- Readiness must be assessed across leaders, managers, employees, systems, policies, data, and operational timing — not employee sentiment alone.
- ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) shows that individual adoption is a sequence; skipping a step stalls the change.
- Strong SCP answers avoid 'big-bang' rollouts when sponsorship, capability, or operational capacity is missing, and use decision-quality pilots instead of vague trials.
Sequencing Change So It Can Be Absorbed
A strategic change plan converts executive intent into adoption. At SCP level the question is not only what should change but how the organization can absorb the change without damaging service, trust, compliance, or performance. Sequencing is the discipline of ordering work to respect dependencies and create learning before risk grows too large.
Several named frameworks underpin senior change work, and the exam expects you to recognize them:
| Model | Structure | Best used for |
|---|---|---|
| Lewin | Unfreeze → Change → Refreeze | A simple frame for destabilizing the status quo and locking in the new state |
| Kotter (8 steps) | Urgency → Coalition → Vision → Communicate → Empower → Short-term wins → Consolidate → Anchor | Complex, high-stakes enterprise transformation |
| ADKAR | Awareness, Desire, Knowledge, Ability, Reinforcement | Designing communication and training at the individual adoption level |
| Bridges' Transition | Ending → Neutral Zone → New Beginning | Managing the psychological transition, not just the structural change |
Lewin gives the macro frame; Kotter elaborates it into steps; ADKAR works at the individual; Bridges addresses emotion. Mature plans blend them — Kotter to structure the timeline, ADKAR to design enablement, Bridges to support people through loss.
Assessing Readiness Broadly
Readiness must be assessed across more than employee sentiment. Leaders must be aligned, managers must know which decisions they can make, systems must support the new process, policies must not contradict the change, and the business calendar must let people pay attention. A change launched during a peak operating period can fail for reasons unrelated to its strategic quality.
| Readiness area | Questions to ask | SCP risk if ignored |
|---|---|---|
| Leadership | Are sponsors aligned and visible? | Mixed messages and weak accountability |
| Management | Can managers explain and implement it? | Local inconsistency and avoidable resistance |
| Operations | Does timing fit capacity and demand? | Service disruption or change fatigue |
| Systems | Do tools and data support the process? | Manual workarounds and unreliable metrics |
| Policy | Are rules and incentives consistent? | Confusion, fairness concerns, compliance exposure |
In ADKAR terms, sentiment is only Desire; readiness also requires Knowledge (managers trained), Ability (systems and tools in place), and Reinforcement (incentives realigned). Assessing only one element is a frequent distractor in exam scenarios.
A Practical Sequencing Model and the Role of Pilots
A disciplined sequencing model includes:
- Define the business outcome and nonnegotiable constraints.
- Identify stakeholders, decision rights, and sponsor actions.
- Assess readiness across people, process, technology, policy, and capacity.
- Pilot or phase where learning can reduce risk.
- Communicate with managers before broad employee messaging.
- Monitor adoption, escalate barriers, and adjust without casually changing the core purpose.
Pilots are useful when they test assumptions. A pilot needs criteria, measures, and a decision point; it should never become a way to avoid a difficult enterprise decision. In exam choices, a well-designed pilot beats a vague trial because it generates evidence leaders can act on — and it produces Kotter's short-term wins.
Sequencing also requires attention to informal adoption. Employees may understand the official message but follow the behavior managers actually reward. If the performance system, staffing model, or executive attention still reinforces the old behavior, communication alone will not produce the new outcome — the refreeze never happens.
Avoiding the Big-Bang Trap
When comparing answers, be cautious about options that announce a large change before preparing managers or resolving governance. Announcement creates expectations; if the organization cannot answer basic questions, early communication erodes trust rather than building momentum.
The senior leader preserves urgency while managing absorption. The best plan identifies what must happen now, what can be phased, what must be monitored, and what would trigger escalation — turning change into a governed business process rather than a one-time HR event.
Worked senior SJI reasoning
Leadership wants to deploy a new enterprise talent process company-wide during the busiest operating quarter. A tactical answer schedules the rollout as requested to meet the deadline. The Advanced HR Professional answer recognizes a readiness-and-timing failure: peak quarter starves the change of Ability (manager bandwidth) and risks service disruption.
The senior recommendation is to surface the timing conflict to the sponsor with evidence, propose a phased pilot in one ready business unit to generate short-term wins, prepare managers first, and sequence the broad rollout after peak — preserving the strategic intent while protecting the business. The credited choice manages absorption, not just announcement.
Change Fatigue, the Transition Curve, and Reinforcement
Enterprise leaders frequently underestimate change saturation — the cumulative load of concurrent initiatives competing for the same managers and employees. When too many changes run at once, even well-designed efforts fail because the organization lacks the Ability (in ADKAR terms) to absorb more. A senior HR leader maintains a change portfolio view, sequences initiatives against capacity, and is willing to recommend pausing or staggering a lower-priority change to protect a strategic one.
The Kübler-Ross change curve (denial, anger, bargaining, depression, acceptance) and Bridges' Transition Model both remind the senior leader that people experience a psychological dip even when the structural change is sound. Productivity often falls before it recovers. Planning for this dip — extra support in the neutral zone, realistic timelines, and patience with the curve — distinguishes a strategic plan from an optimistic one.
Reinforcement: the step most often skipped
- Realign incentives and metrics so they reward the new behavior, not the old.
- Audit informal signals — what managers actually praise and escalate.
- Sustain sponsor attention past the launch so the change does not quietly decay.
- Measure adoption, not just deployment; a deployed system that no one uses has not changed anything.
Lewin's refreeze, Kotter's anchor in the culture, and ADKAR's Reinforcement all name the same truth: change that is not reinforced reverts. SHRM-SCP scenarios that end at "go-live" are a trap — the credited senior answer extends the plan to reinforcement and measurement so the new state actually sticks.
A company wants to roll out a new enterprise talent process during its busiest operating period. What should HR recommend first?
In the ADKAR model, an employee understands the change and wants it but cannot yet perform the new task. Which element is missing?
Why is manager readiness critical before broad employee communication?