How to run a change readiness assessment

Why readiness, not just engagement

Transformations rarely fail because the strategy was wrong. They fail because the organization couldn’t execute it — misalignment at the top, no capacity in the middle, and issues no one felt safe naming. An engagement survey won’t find those; it measures how people feel about work in general. A change readiness assessment measures something narrower and more useful: whether this organization can deliver this change, on this timeline.

Step 1 — Scope it to a decision

A readiness assessment is only as sharp as the change it is tied to. Before you ask anyone anything, be specific about three things:

• The change — what, concretely, is being asked of the organization?
• The population — whose readiness actually determines the outcome? It is often the middle layer, not just the leadership team.
• The timeline — a read taken six months out answers a different question than one taken two weeks before go-live.

Scoping to a decision is what separates a readiness assessment from a general survey.

Step 2 — Ask one open question, not forty

The instinct is to build a long questionnaire covering every dimension of change. Resist it. A forty-item survey tells you how people responded to your assumptions; it cannot tell you about the risk you didn’t think to ask about. One well-framed open question — “What will make it hard for us to deliver this change?” — lets respondents name the real obstacles in their own words. That is where the surprises live, and the surprises are the point.

Step 3 — Measure the five dimensions that predict delivery

However you collect input, read it against the five signals that consistently predict whether change lands:

• Alignment — do leaders and teams agree on what the change actually is, or only on the words? Red flag: the same initiative described five different ways.
• Capacity — is there room, in time and attention, to deliver it? Red flag: every team is already maxed out on prior initiatives.
• Candor — will people raise problems before it’s too late? Red flag: the issues surface only when named anonymously.
• Ownership — does someone feel responsible for the outcome? Red flag: everyone supports the change; no one owns it.
• Consensus gap — where does the front line see risk that leadership doesn’t? Red flag: a wide gap between how leaders and staff rate the same thing.

Step 4 — Score it, don’t just read it

Free-text comments alone are hard to act on. Have each respondent self-score the issues they raise — for sentiment (how negative or positive), personal influence (how much they can affect it), and perceived consensus(whether they think leadership sees it the same way). Now you can quantify the qualitative: which issues are most negative and most widely held, and where the consensus gap is widest. The pattern across responses is your readiness read.

Step 5 — Turn the read into a 100-day plan

A readiness assessment that ends in a report is a wasted one. Because respondents also propose actions, the output is already the start of a plan: the highest-consensus, highest-impact issues become your first priorities, and the proposed actions give you starting points that already carry buy-in. Sequence the first hundred days around the constraints the read surfaced — not the ones the strategy assumed.

Common mistakes

• Running it too late. A readiness read is most valuable before commitment, or in the first phase — not as a post-mortem.
• Sacrificing anonymity. The moment people suspect their answers are attributable, candor collapses and you measure politics, not readiness.
• Measuring feelings instead of capacity. “Are people happy?” is the wrong question. “Can we deliver this?” is the right one.
• Not acting. Asking the organization what will make the change hard and then doing nothing is worse than not asking.