Running a change readiness diagnostic before a major initiative

The average-employee problem

Change management programs are typically designed for a composite: the average employee, in the average role, with an average relationship to the change. Communications are written for this person. Training is built for this person. Timelines are set for this person. The problem is that this person does not exist. Real workforces contain people who will adopt immediately, people who will struggle for specific reasons, and people who will resist for reasons that are entirely rational given their circumstances. A change readiness diagnostic exists to find the distribution — and to identify the specific risks at the tails.

What change readiness actually means

Readiness is not enthusiasm. An employee can be enthusiastic about a change and completely unready for it — because they lack the skills, their workflow will break, or the change conflicts with how they are evaluated. Conversely, an employee can be skeptical and highly ready — because they understand exactly what is changing and have already adapted. A useful change readiness diagnostic separates these dimensions:

• →

  Awareness — Does the person understand what is changing, when, and why?

• →

  Capability — Does the person have the skills, tools, and support to operate in the new model?

• →

  Motivation — Does the person see the change as beneficial, neutral, or threatening to their role?

• →

  Structural alignment — Do the systems around the person — evaluation criteria, incentives, workflows, reporting lines — support the new way of working, or do they still reward the old one?

Finding the high-risk tail

The most valuable output of a change readiness diagnostic is not the average readiness score. It is the identification of specific groups, roles, or conditions where readiness is low for specific, addressable reasons. A department where readiness is low because the manager has not communicated the change requires a different intervention than a department where readiness is low because the change eliminates a core workflow that employees depend on. The diagnostic identifies both — and the distinction determines whether the right response is communication, training, workflow redesign, or timeline adjustment.

When to run the diagnostic

The diagnostic should run after the change has been defined but before the rollout plan is finalized. Running it too early produces speculative responses — people reacting to rumors rather than specifics. Running it too late means the findings arrive after the rollout plan is committed and the budget is allocated. The ideal window is when leadership can describe the change concretely — what is changing, who is affected, and what the expected timeline is — but still has room to adjust the implementation approach based on what the diagnostic reveals.

What the diagnostic produces

The output is a readiness map segmented by population, role, business unit, or other relevant dimensions. Each segment receives a readiness profile that identifies the primary risk factors and their causes. The report includes a prioritized list of interventions — communication gaps to close, training to deliver, structural misalignments to resolve, and timeline risks to address — with owners and target dates. The follow-up measurement schedule confirms whether the interventions shifted readiness in the target populations before the rollout reaches them.