By Ritvars Mētra, Founder of ReadinessCompassThere is often a gap between how executives perceive readiness and how frontline employees experience it. Executives see strategy alignment, budget approval, milestone completion, and positive steering committee updates. Employees see disrupted routines, unclear roles, new tools they have barely practised with, and managers who are not yet confident explaining what is changing.
This gap is not a failure of communication. It is a structural feature of transformation. Executives experience the change as intent. Employees experience it as consequence. Intent is clean. Consequence is messy. The readiness gap sits between them, and it is one of the most reliable predictors of post-go-live adoption problems.
Why the executive-frontline readiness gap is predictable
The gap emerges because executives and frontline users get their information from different sources, at different times, with different levels of detail. Executives see aggregated readiness scores, programme dashboards, and milestone reports. Frontline users experience the daily uncertainty of not knowing whether a process they have used for years will still exist next month, whether their expertise will still matter, and whether their manager can answer practical questions.
The readiness gap creates specific risks: go-live decisions based on executive confidence rather than frontline evidence, training that assumes knowledge people do not yet have, manager briefings that happen too late to change behaviour, and hypercare plans that underestimate the real volume of confusion and workaround.
What reporting does to the gap
The clearest published account of this comes from the UK National Audit Office. Reviewing Crossrail in 2019, the auditors observed that the progress reports given to the board and sponsors emphasised what had been achieved and how much of the programme had been completed — and did not adequately consider the level of risk to successful delivery that remained. The NAO returned to the finding in its 2023 report Lessons learned: Resetting major programmes.
That is the mechanism in one sentence. Completion is cumulative, easy to evidence and flattering to present. Remaining risk is contestable, unflattering, and can rise the week before go-live. A reporting line optimising for board comfort produces the first and quietly drops the second — and executives are then confident for entirely rational reasons, given what they were shown.
The same report found that when programmes were reset, respondents most commonly identified product or output failure as the trigger. Not a checkpoint. Not an early warning. The failure itself.
How to measure the readiness gap
Measuring the gap requires structured comparison between what executives believe and what frontline evidence shows. Compare executive readiness ratings with frontline survey results for the same dimensions—awareness, capability, confidence, manager support, and perceived capacity. Run manager interviews that ask not just “are you ready?” but “what is the most common question your team is asking, and do you feel equipped to answer it?” Review support-ticket themes in the weeks after go-live, looking for patterns that suggest readiness was overestimated in specific areas.
Three questions produce more signal than a survey round, because none of them can be answered from a status pack:
- Ask a receiving manager what their team will stop doing in the first three weeks. An answer of “nothing” is a finding about capacity, not about attitude.
- Watch four people attempt the core task unaided and time them. Half a day of observation produces more usable readiness evidence than a month of survey work, and it is the only method that reveals borrowed confidence.
- Ask who on the programme thinks the date is wrong, and what they say. If the answer is that nobody does, the answer is wrong.
What a formal readiness gate asks instead
Government assurance regimes have had a gate for exactly this decision for two decades, and the questions are public. The Gateway process — published in workbook form as, for example, Gate 4: Readiness for service — asks “Is the organisation ready for business change?” and does not accept a percentage as the answer. The evidence expected is agreed plans for business preparation and transition, a documented communications plan, staff trained and informed, and a clearly defined service management function already in place.
Its companion question is the one that most reliably exposes the gap: can the organisation implement the new services and maintain existing services? Executives answer that from strategy. Frontline teams answer it from their current workload, and the two answers are rarely the same.
Readiness gap→
Frontline evidence→
Aligned action→
Go-live confidence
Example: closing the readiness gap requires comparing executive confidence with frontline evidence and taking action on the differences.
Why the frontline view is harder to obtain
There is a reason frontline readiness data is thinner, and it is not indifference.
Transformation frequently carries implied job insecurity, and its effects are well documented. The meta-analysis by Magnus Sverke, Johnny Hellgren and Katharina Näswall in the Journal of Occupational Health Psychology found job insecurity has detrimental consequences for employees’ job attitudes, organisational attitudes, health, and to some extent their behavioural relationship with the organisation — with behavioural effects more pronounced among manual than non-manual workers.
An employee who is unsure whether their role survives the programme has limited incentive to report that they cannot yet do the new process. Saying so is a disclosure about their own competence during a period when competence feels load-bearing. Readiness surveys therefore tend to return optimistic answers from precisely the populations under most pressure, which widens the apparent gap between layers while narrowing the reported one.
How to close the readiness gap before go-live
Closing the gap requires deliberate action: present frontline readiness evidence alongside leadership confidence ratings, not separately. Run manager readiness checks that test whether managers can answer the questions their teams are asking. Validate training by testing task performance, not just attendance. Make adoption data visible to executives in a form they can act on—segmented, specific, and connected to business risk.
The structural fix is to stop treating go-live as a single signature. Business readiness is a set of separate claims—people can do the work, there is capacity, exceptions are covered, support is staffed, we can revert—each owned by someone who will personally live with the consequences. Separating those claims from technical sign-off makes the gap visible on the page rather than in week three.
Common mistakes in managing the readiness gap
The most common mistake is assuming the gap does not exist because no one has measured it. A second mistake is relying on leadership confidence without frontline validation. A third mistake is treating the gap as a communication problem when it is often a structural one—executives and frontline users simply experience the change differently. A fourth mistake is ignoring early signals of the gap, such as managers who cannot answer basic questions, training questions that reveal confusion, or support-ticket themes that persist after hypercare begins.
A fifth is writing readiness criteria that can be satisfied without the underlying capability existing. “95% of users trained” will be met, and it permits a warehouse that cannot pick an order — which is why criteria need to be written so they can actually fail.
Closing this gap depends on evidence rather than reassurance. Explore change readiness resources and guidance for related material on measurement and leadership action.