A figure at a starting line, the track ahead marked with four coloured readiness gauges

TL;DR

What Is Change Readiness - and How Do You Assess It?

  • Change readiness is the state of the ground before a change effort begins - and the research says it is the strongest early predictor of whether the effort lands.
  • Conventional readiness surveys have a structural flaw: they are launched after the decision and answered with the programme in view.
  • A culture measured for its own sake - the collective language and behaviour of its people - contains the readiness picture before any change is named.
  • Read against Kotter's eight steps, the same cultural data shows which steps are ready now, which will need the most work, and where the effort will feel hardest.

Every failed transformation produces the same retrospective sentence: "we weren't ready". It is said as though readiness were unknowable in advance - weather that struck the programme rather than terrain it was launched across. But readiness is not weather. It is a property of the organisation that existed, in full, on the day the change was approved. The only question is whether anyone could see it.

What readiness actually is

What does change readiness mean?

Change readiness is the degree to which an organisation's people are prepared - practically and psychologically - to adopt a specific change. The research tradition, led by Armenakis and colleagues, defines it through beliefs: that change is needed, that this change is the right one, that the organisation can carry it, and that leadership is behind it. Readiness is not the same as agreement or enthusiasm; it is the state of the ground before the effort begins, and it decides how much of the effort arrives.

The foundational work is Armenakis, Harris and Mossholder's 1993 paper, which made a distinction the field still relies on: readiness is not the absence of resistance. Resistance is a reaction to a change under way; readiness is the precondition that determines what the reaction will be. Their research located it in beliefs - about the necessity of change, its appropriateness, the organisation's capacity, and leadership's commitment - and later work tied those beliefs to hard outcomes. It is the reason Kotter's first step is building urgency: urgency is readiness work, done before anything visible changes.

Notice, though, what those beliefs live in. An organisation does not hold beliefs; its people do, and they express them the only way beliefs are ever expressed - in language and behaviour. Which is the thread that runs through this whole series: culture is the collective language and behaviour of an organisation's people, and readiness is one of the things written in it.

Resistance is a reaction to a change under way. Readiness is the precondition that determines what the reaction will be.

The trouble with readiness surveys

How do you do a change readiness assessment?

Conventionally, through a survey about the proposed change - questions on perceived need, confidence in leadership, capacity and past change experience - combined with interviews and a review of workload and capability. The known weakness is that people answer with the programme in view, so the results measure presentation as much as readiness. The alternative is to read readiness from culture data collected for its own sake: the aggregated working preferences of the organisation's people show its appetite for the new, its trust formation speed, its delivery tempo and its definition of finished - the raw materials of readiness, measured without anyone performing for the survey.

The conventional assessment has three structural problems. It is timed wrong: commissioned after the decision, when the honest answer to "are we ready?" can no longer change the plan, only the communications. It is answered strategically: the questions arrive visibly attached to a programme, and everyone answering knows what the leadership hopes to hear - the same performance problem that undermines engagement surveys. And it is shallow by necessity: a survey about a specific change can only ask about attitudes to that change, not about the deeper working patterns that will actually decide its fate.

Compare what a culture measurement holds. When people answer sixty paired statements about how they actually work - with no change programme in sight and their individual results private to them - there is nothing to perform for. Aggregated, those preferences show the organisation's appetite for the familiar against the new, how quickly its people extend trust, how it makes decisions, what its tempo of delivery is and what it calls finished. That is not adjacent to readiness. That is readiness, measured at the level where change actually succeeds or fails: the daily behaviour of the people asked to change.

70% Kotter's estimate of change efforts that fail - with unreadiness at step 1, urgency, identified as the most common point of death Kotter, Harvard Business Review, 1995
1993 The year readiness was formally separated from resistance - as beliefs measurable before the change begins, not reactions to it Armenakis et al., Human Relations, 1993
75% Of management who must see the status quo as unacceptable before a change effort is safe to launch, by Kotter's own threshold Kotter, Leading Change, 1996

Reading readiness through eight lenses

Here the two halves of this series meet. Kotter's eight steps, read honestly, are not a sequence to execute but eight places where change dies - which makes them eight questions to ask of a measured culture. Each step draws on identifiable cultural ground, and a cultureMAP shows that ground directly.

Urgency lives in the culture's appetite for the new against its attachment to the proven - and a culture whose strengths are steadiness, organisation and precision can be complacent while looking conscientious, its reliability filtering out the very signals urgency needs. Coalition and communication live in how trust forms and agreement spreads: a culture of slow, careful commitment will not produce a guiding coalition in a fortnight, and Kotter's "communicate ten times more than you think" may need to be fifty in a culture where trust is extended cautiously. Vision lives in how the organisation works out what to do - a methodical, analytical culture will produce a rigorous forty-page strategy and mistake it for a five-minute story. Wins live in tempo and the local definition of "done": a culture that calls nothing finished until it is finished properly will struggle to produce the unambiguous twelve-month win the research says momentum requires. And anchoring lives in what the group produces through people - the same exacting standards that resist a new practice at first are what lock it in permanently once adopted.

Read that way, the readiness question stops being a single score and becomes a profile: which steps is this culture ready for now, and which will need deliberate work first? That is also the answer to the sequence problem the academic critique kept raising - the steps run in the order the culture can support, not the order the book lists them.

The steps run in the order the culture can support, not the order the book lists them.

When to assess - and the stage trap

When should you conduct a change readiness assessment?

Before the change is designed - not after it is announced. Assessing readiness after commitment turns the assessment into a communications exercise, and its findings arrive too late to shape the plan. Read the culture first and the sequence reverses: the readiness picture informs which changes are attempted, in what order, at what pace, and where the early resistance will sit. The most useful readiness assessment is one the organisation would have been running anyway - a standing cultural measurement, refreshed at least twice a year, that any proposed change can be read against on the day it is conceived.

What are the five stages of change readiness?

The five-stage language comes from Prochaska and DiClemente's transtheoretical model of individual behaviour change: precontemplation, contemplation, preparation, action and maintenance. It describes a person's journey, and it transfers to organisations only loosely - an organisation is not one mind moving through stages but a population of people at different stages simultaneously. That is precisely why population-level measurement matters: a readiness reading needs to show the distribution, not assume the organisation occupies a single stage.

The stage trap deserves the emphasis. Treating an organisation as one entity at one stage of readiness is the same compression error as typing a culture: it replaces a distribution with a point and loses exactly the information that matters. The organisation is never uniformly ready. Parts of it are ready now; parts will resist to the end; and the boundary between them - visible in aggregated preference data, invisible in a town hall - is where a change effort should concentrate its attention from day one.

"We weren't ready" should be the most preventable sentence in management. Readiness is not a mystery revealed by failure; it is a measurable property of a culture, sitting in the collective language and behaviour of its people, waiting to be read before the money is spent. The organisations that read it first get to have the retrospective nobody writes: the change that worked, because the plan was fitted to the culture rather than the culture blamed for the plan.

The companion pieces: the framework these lenses come from is examined in is Kotter's 8-step change model still relevant; what culture is made of is in organisational culture is language and behaviour; how the map is built is in why culture can be mapped. The instrument is Sariio AI.

Sources