1 Change Readiness

Meaning and levels of readiness

Change readiness describes how prepared people and organizational conditions are to carry out a particular change. It is specific to the proposed change; it is not a permanent personal trait or simply a measure of whether employees like change.

Readiness has individual and organizational aspects. A person may understand and support a change while their team lacks the time, skills, or resources to adopt it. An organization may have strong systems and resources while employees lack confidence in the change or its value, so assess both levels rather than treating one survey score as the whole picture.

Commitment and efficacy

Weiner’s framework treats organizational readiness as a shared psychological state with two related but distinct dimensions. Change commitment is members’ shared resolve to implement the change: whether they believe it is worthwhile and are willing to make the effort. Change efficacy is members’ shared belief that they can implement it together.

The dimensions need not be equally strong. Staff may value a new process but doubt that they can use it with current staffing, or feel capable of using it but question why it is needed. Readiness is influenced by the value people place on the change and their assessment of task demands, available resources, and situational conditions. Higher readiness can support effort and persistence, but does not guarantee that the change is well designed or will produce its intended benefits.

Beliefs that support readiness

Armenakis and colleagues’ framework identifies beliefs that a change message may need to address:

• Discrepancy: Is there a credible reason to move from the current state?

• Appropriateness: Is the proposed change a suitable response to that need?

• Efficacy: Do people believe they and the organization can carry it out?

• Principal support: Do employees see credible leaders and influential colleagues backing the change?

• Personal valence: Can people see what the change means for them and why it matters?

For example, announcing new scheduling software may explain why the current system is inadequate, addressing discrepancy. Readiness may still be low if staff doubt the replacement fits their work, expect insufficient training, see managers ignoring it, or fear losing flexibility. These concerns call for specific answers and, where possible, meaningful involvement—not simply more announcements.

Assess readiness in context

A readiness assessment should answer a practical question: what conditions, beliefs, or gaps need attention before and during implementation? Use the findings to identify support needs, not to label people as resistant.

A useful assessment process is:

1. Define the change and who is affected. Specify what will change in roles, workflows, technology, or decision-making, and identify groups that may experience different impacts.

2. Choose dimensions to assess. Consider understanding of the need, perceived suitability, leadership support, willingness, confidence and skills, time and resources, workload, competing initiatives, and past experience with change. Include infrastructure and the organization’s capacity to absorb the transition.

3. Gather evidence from multiple levels. Use a tailored survey alongside interviews, focus groups, observation, or existing operational data. Include executives, managers, frontline staff, and other affected groups; do not rely only on project leaders or already enthusiastic volunteers. Representative assessment across organizational levels can help shape support to stakeholders’ needs.

4. Look at group differences, not just averages. Compare roles, locations, shifts, or other relevant groups. An overall positive average can conceal a team that lacks training or a group facing substantially greater impact.

5. Interpret responses in context. Low confidence might signal inadequate training, unclear processes, poor communication, or a genuine lack of capacity. Follow up to understand the cause before choosing a remedy.

6. Act and reassess. Assign actions such as providing practice time, resolving resource constraints, clarifying the rationale, or involving affected staff in workflow design. Check progress again as the change approaches and after implementation begins.

Use evidence carefully

Use clear, change-specific questions and protect confidentiality so people can answer candidly. Questions can explore whether people understand why the change is needed and why this approach was selected; whether they believe it will improve the work; whether they know what will change in their roles; and whether teams have the skills, time, staffing, tools, and leadership support required. Also ask what concerns or risks employees see, whether they believe it is safe to raise them, and which groups face the greatest disruption or competing demands.

Treat results as diagnostic evidence, not as a pass/fail verdict. Readiness instruments vary in what they measure, and reviews have found limitations in the reliability or validity evidence for many available measures. Do not assume that a questionnaire or numerical threshold is universally valid.

Turn findings into support

Connect assessment findings to specific support. Low commitment may call for clearer evidence of need, a better explanation of the chosen approach, or genuine participation in decisions. Low efficacy may call for training, coaching, practice, staffing, or removal of implementation barriers. Weak perceived leadership support calls for visible, consistent sponsorship. Concerns about personal impact call for honest discussion and practical transition support.

Repeat the assessment and connect it to decisions. If feedback shows that a unit lacks time to train, adjust the transition plan rather than merely repeating the announcement. Monitor perceptions and observable indicators such as training completion, access to resources, use of the new process, and unresolved issues. Early adoption alone does not prove long-term effectiveness.

Readiness can support implementation, but it does not guarantee success.