Change Readiness Assessment: What to Check Before Rolling Out a New Process

The new process has an owner, a launch date, and a training deck. The project team is ready to roll it out.

The supervisors expected to reinforce it are covering vacancies. Employees will need information stored in a system they cannot access. The old performance measure still rewards the behavior the new process is supposed to change.

A change readiness assessment examines whether the people and conditions required for a specific change are sufficiently prepared. It helps leaders identify what needs to be resolved, supported, or sequenced before implementation.

Assess readiness for a particular change

Avoid asking whether the company is generally ready for change. Define what the proposed process will require different people to do.

Who will make a different decision? Enter new information? Coordinate with another function? Stop using an existing workaround? What will managers need to explain or reinforce?

Prosci's readiness assessment guidance examines organizational preparedness alongside individual readiness and attitudes toward change. The useful unit of inquiry is the work people will actually need to change.

Check leadership agreement

Ask sponsors and affected leaders to explain the purpose, expected result, tradeoffs, and their own responsibilities. Compare their answers.

One leader may describe the process as mandatory while another treats it as a pilot. One may expect local adaptation while another assumes uniform use. Resolve those differences before managers inherit them.

Name the person who can decide consequential questions and the route for issues that cross functions. A visible sponsor is valuable, but employees also need a usable path for decisions.

Check capacity and competing demands

List the work required to learn, test, and use the process. Include manager preparation, coverage, system setup, practice, and follow-up—not only training attendance.

Examine what else is happening for the affected groups. A launch date can look reasonable in a project plan and be unrealistic for a plant completing an integration or a team already carrying several initiatives.

Decide what will be stopped, delayed, or resourced differently. Readiness is partly an executive choice about capacity, not simply an employee attitude to measure.

Check skills, access, and workflow fit

Ask people to walk through the new process using a realistic scenario. Can they find the information, use the system, and apply the decision rules? What happens when the standard case does not fit?

In manufacturing, test across relevant shifts and locations. Support available during office hours may be missing at night. A procedure designed for a desk-based employee may be impractical on the production floor.

Observe where people have to invent a step. Those moments identify requirements the design may have missed. Training cannot compensate for unavailable information or incompatible systems.

Check incentives and manager support

What behavior do current measures reward? Will employees be penalized for the time needed to use the new process? Will a supervisor encourage the change or quietly direct people back to the old route when output is under pressure?

Give managers enough understanding and authority to support the process. Ask what questions they expect and what circumstances could make reinforcement difficult.

Review whether the process changes expectations without changing the resources employees need to meet them. A readiness finding should lead to a decision about those conditions.

Listen to concerns as evidence

A concern may reflect confusion, workload, loss of influence, previous experience, or a flaw in the proposed process. Investigate before labeling it resistance.

Use interviews, focused discussions, a short survey, or a pilot according to the question. Check whether people understand the purpose and can explain what will change for them. Examine concerns alongside practical evidence.

Your AI Rollout Has an Organizational Design Problem explores a related issue: a tool or process can create output while leaving ownership and downstream work unresolved.

Turn findings into rollout decisions

For each gap, identify evidence, consequence, owner, and required action. Decide whether to proceed, proceed with targeted support, pilot in a limited area, or resolve a critical gap before rollout.

Do not let an average readiness score conceal a serious dependency. Strong enthusiasm does not offset missing access to a necessary system. Conversely, uncertainty does not always require postponing the entire initiative; it may call for better support and a smaller test.

Set a review point and repeat the relevant checks as conditions change.

Measure adoption in work

After launch, examine whether the process is being used as intended, whether people can handle exceptions, and whether the expected outcome is emerging. Training completion is useful information, but it is not evidence of sustained use.

Include feedback from the people carrying the process. New workarounds may show where the design still does not fit.

Culture Pop's organizational change consulting helps leaders connect readiness, leadership alignment, and implementation support. Let's examine what your rollout needs before the launch date becomes the decision.