By Ritvars Mētra, Founder of ReadinessCompassMany organisations produce readiness surveys. Few produce readiness decisions. A survey can ask all the right questions about awareness, confidence, capability, sponsorship, and training satisfaction. It can produce a dashboard with colour-coded scores, trend arrows, and neatly labelled charts. It can be reviewed in a steering committee, generate some nodding, and then quietly expire as the meeting moves to the next agenda item.
This is the gap between measurement and management. A readiness survey that does not change what leaders do is a diagnostic without a prescription. It tells the organisation something about itself and then politely declines to say what must happen next.
Why most readiness surveys fail to create action
The failure is usually not in the survey. It is in the connection between survey evidence and leadership decision-making. A survey may show that manager confidence is low in two regions. That is useful information. But useful information becomes useless if nobody asks: what will we do differently because of this? Who will act? By when? How will we know if the action worked?
A readiness survey should help leaders:
- identify where adoption risk is concentrated,
- understand whether managers can reinforce the change locally,
- spot capability and confidence gaps before they become operational problems,
- decide where to allocate hypercare, training, or sponsor attention,
- track whether readiness is improving as go-live approaches.
How to design surveys that create decisions
The design starts before the questions are written. It starts with the decisions the survey must enable. If the decision is “should we proceed with go-live?” the survey must test clarity, ability, confidence under real conditions, manager readiness, capacity, and unresolved blockers. If the decision is “where should we allocate floor-walker support?” the data must be segmented by user group, location, and process area.
The wording matters. Many surveys ask questions that create pleasant ambiguity: “I understand the change” or “I feel prepared.” A better question is anchored in behaviour: “I know which reports will be retired and which report I must use after go-live” or “I can complete the new customer handover process without using the old template.” Specificity creates accountability.
How to turn survey results into leadership actions
Converting results into action requires a disciplined approach: segment the results by audience, workstream, or business unit; identify the weakest readiness signals where capability, confidence, clarity, or reinforcement is lowest; translate each signal into a business risk—what will happen if this is not addressed before go-live; assign an owner and intervention—who will act, what they will do, and by when; recheck after the intervention—did the metric move? If not, escalate or redesign.
→
Readiness signal
→
Business risk
→
Leadership action
→
Outcome review
Example: readiness surveys create value when each weak signal is translated into an owned leadership action with a clear follow-up.
The metrics that matter for leadership decisions
Every readiness metric on a leadership dashboard needs three things: an accountable owner, a decision rule, and a review rhythm. Who acts when the metric moves? What decision does it inform? What happens when it stays red for two cycles? Without this discipline, the dashboard becomes a reporting ritual. McKinsey has documented that transformation programmes connecting readiness evidence to leadership decisions are more likely to deliver sustained results. Gartner research reinforces that change-ready organisations build adoption measurement into governance, not just communication and training.
Common mistakes in readiness measurement
The most common mistake is measuring too late. A survey two weeks before go-live can still guide hypercare, but it cannot reshape the adoption strategy. A second mistake is measuring activity instead of behaviour—training completion is not capability, communication reach is not understanding. A third mistake is using averages that hide weak spots. A fourth mistake is collecting data without acting on it, which teaches the organisation that surveys are decorative. A fifth mistake is treating the survey as the end of the readiness process rather than the beginning of a decision sequence.
A simple operating rhythm for adoption decisions
The final test is simple: after the readiness dashboard is reviewed, can you name the decisions made because of it? If a sponsor intervened, a training module was redesigned, a release was resequenced, or support was shifted to the right team, then the survey has done its job. If not, it was decorative. Readiness surveys should not exist to prove that change management is busy. They should help leaders see where adoption will break, decide what to do, and then check whether the action changed anything.