Assessing Change Readiness: The Questions to Ask

The launch date is set, the business case is approved, and every planning meeting has ended with people agreeing.

That is usually the moment someone asks whether the organization is ready, and nobody has a way to answer. A change readiness assessment answers it. It is a structured look at whether the people affected by a change can absorb it: who it touches, what they do today, what you are asking them to do instead, what they believe about it, and what it takes away from them. Run it before you commit to a date, and what you find is still cheap to fix.

Let's break this down, because most readiness work happens in the wrong order. The assessment usually arrives after the budget is set, and the business case are already set, so it can report a problem but it can't change anything. An assessment that cannot move the date is a status report.

Key takeaways

• A readiness assessment measures capacity and belief. Nodding in a planning meeting doesn't tell you whether people can absorb the change.

• Assess by persona, not by headcount. The working managers and the executives above them are two different audiences with two different problems.

• The assessment should end in a decision: go, narrow or wait. If it ends in a score, it wasn't an assessment.

• The manager layer is where readiness usually breaks, and it breaks for reasons that have nothing to do with willingness.

• Do the assessment before you ask people to commit to a date. After go-live it becomes a recovery project.

What is a change readiness assessment?

A change readiness assessment is a check on whether the people a change touches can take it on, done before the change goes live.

It is not a communications plan and it is not a stakeholder map. Those tell you who to talk to. A readiness assessment tells you what each group will have to do differently, what stands in the way, and what the change costs them personally. It produces a short list of gaps, each one attached to a role, an owner and a date.

Prosci's own benchmarking research reports that projects with excellent change management are six times more likely to meet objectives than those with poor change management. That figure comes from a change management firm's client data rather than independent research.

The other reason to do it is the money. A change that stalls keeps costing you long after launch day, and most of those costs were visible before you launched. That is the case I made in why a stalled initiative is one of the most expensive things in your business.

Why readiness assessments usually tell you what you already believe

Here is the common version. A survey goes out, the scores come back mostly green, the launch proceeds, and adoption doesn't follow.

Two things usually went wrong. The survey went to people who are not doing the work, and the questions invited agreement. When I ran usability testing, the rule my team used was simple: don't lead the witness. The same rule applies to a readiness survey. "Do you feel supported through this transition?" gets you a yes. "What will you do differently on the first Monday after this goes live?" gets you an answer you can act on, or a silence that tells you more.

It is also worth checking whether the leaders are ready, not just the staff. In its own Global Transformational Leadership Survey 2025, Happily.ai reported that 45% of leaders felt unprepared or unsure about their readiness for upcoming challenges, from 3,354 interviews and surveys across 26 countries fielded in late 2024 and early 2025. That is the company's own survey rather than independent research. The people setting the date are often the least sure about it.

one small shift: before the survey goes out, write down the result you expect from each group. The gap between your prediction and their answers is your real finding.

How do you conduct a change readiness assessment?

This is the sequence I use. It's the part of a change plan that most often decides whether the rest of it holds up.

Map who is affected, by persona. Not a headcount, and not an org chart. Group people by what the change asks of them, then write a plan for each. If two groups end up with the same plan, they're probably one group, and you can stop writing two.

Write the as-is and the to-be for each persona. What a normal day looks like now, and what it looks like after. If you can't write the second one in plain sentences, the change isn't designed yet. Build the as-is by watching the job rather than from the process document, which tells you how the work is supposed to run.

Name the one behavior each role has to do differently. If two roles get the same sentence, you haven't reached the role level yet.

Find the belief the change challenges. This is the part most assessments skip, and it's often the part that tells you most about whether people will adopt. The Shift Method starts by identifying a belief and questioning the evidence for it. In an assessment, the belief you are after is what each role believes this change will do to their own work. A title examiner who believes the new system will slow down a file she can already close quickly isn't resisting. She has a hypothesis, and your assessment should find out whether she's right. Sometimes she is, and then you have a product problem rather than a people problem.

Name what the change takes away. The SCARF® model, developed by David Rock at the NeuroLeadership Institute, names five things people care about at work: status, certainty, autonomy, relatedness and fairness. Go role by role and ask which of the five this change touches. The person everyone used to call for a file status, now one user among many, has lost something real, and no amount of training gives it back.

What questions should you ask in a change readiness survey?

Keep them short and specific, and ask about next month rather than about how people feel. Ask the people who will do the work, and ask them individually before you ask them in a group.

• What will you do differently on the first Monday after this goes live?

• What part of your current work does this replace, and what happens to the time it frees up?

• What would make your job harder than it is today?

• Who do you ask when you get stuck, and will that still work afterward?

• What choices do you have in how you adopt this?

• Who else in your office is doing this with you?

• What have you been told about the timeline, and by whom?

• What would have to be true for your office to call this a success?

• What do you expect will happen to people who are slow to pick it up?

• What is one thing we could take off your plate to make room for this?

The question about choices comes from a worksheet I built for a rollout, grounded in self-determination theory (Deci and Ryan): autonomy, relatedness and competence. People adopt things they had some say in. Asking the question also tells you whether they have any say at all.

one small shift: ask every question about a specific week, not about how people feel. "What will you do on the first Monday" beats "how prepared do you feel" every time.

What should a change readiness assessment produce?

A decision, not a score.

By the end, you should have a page for each role: what that role does today, what you are asking instead, the gap between the two, who owns closing it, and the date it closes by. Then one of three calls on the change as a whole.

Go. The gaps are small, each one has an owner, and nothing is unresolved in a role that cannot opt out.

Narrow. Launch with the group that is ready, and let them become the working example while you close the gaps for everyone else. This is the call most people miss, because go or no-go feels like the only choice.

Wait. Something the change depends on doesn't exist yet. Moving a date before you announce it costs you very little.

One thing an assessment must never count as evidence is a yes. The buy-in test I use came out of a change program I sponsored in 2019, and it never asks whether anybody agreed; it's about how to rewire habits at work, along with why watching beats asking.

This is a crazy example, and I still really cannot believe it. We had an HR team do a change analysis and identify all the tasks and skills that a group of new interns needed to learn. The project team sponsor and project team all agreed with the analysis. Then we went to roll it out, and the tasks and skills identified were for a role that didn't exist in the state and, worse yet, wasn't needed. Apparently, no one spoke with the state's managers. It was amazing to watch this kind of misstep unfold. And now you know why, from that day forward, I would only rely on my team's change assessment.

One small shift: in your next steering meeting, ask each leader what they will personally do differently in the first two weeks. Write down who has no answer.

Are your managers ready, or only informed?

Another project I sponsored was a system rollout; the first thing my team did was profile the manager audience. We laid out field, middle, and executive managers across three lines of business and wrote down what was true of each.

What we wrote about the working managers, both field and middle, was blunt. They were busy, commission-driven, customer-focused firefighters, inconsistent at sharing information with their direct reports, not focused on people management, and not skilled at performance management. The executives were time-strapped and focused on shareholders.

None of that is a criticism of them. It is the operating reality you are handing your change to, and it decides what your plan can reasonably ask for. A commission-driven field manager won't deliver a 60-minute cascade about your transformation. She will say one sentence to her team between calls. So your job is to decide which sentence, and to make sure she has it.

Readiness at the manager layer is not a willingness question. It is a capacity question, and you can measure it before you launch.

Run a pre-mortem before you commit to the date

The pre-mortem comes from Gary Klein, who described it in Harvard Business Review in 2007. You gather the team, tell them to imagine the project has already failed, and ask each person to write down why. It gives people permission to say the thing they have been carrying around, and it brings up risks a status meeting rarely reaches.

Do it with the people who will have to use it, not only with the project team. Then there are three more things to settle before you set a date.

Identify the date you are asking people to commit to. Then say what it's tied to. If the only thing behind March 1 is that someone said March 1, your people will work that out before you do.

Don't go live with something that makes the job worse. A first release that costs someone time will be remembered long after you fix it.

Check that nothing has been taken away. If the new way removes a step someone relied on, find out in the assessment, not in the first week.

When should you assess change readiness?

Assess at three points: while the change is still being designed, when a finding can still change it; again before you ask anyone to commit to a date; and a few weeks after go-live, when you find out what the first two rounds missed. That last round is also where you learn whether the new way has become routine, which is the problem I take up in how to lead change effectively.

The common mistake is doing it once, as a gate to pass on the way to launch. Readiness is not a state you reach and keep. The organization you assessed in January is carrying three more changes by June.

How do you measure organizational readiness for change?

Count behavior rather than attitude. A satisfaction score tells you how a briefing landed, not whether anything will change. These hold up better:

• The share of people in each role who can say, unprompted, what they will do differently.

• The share of managers who have had the conversation with their own team, not just received the deck.

• The number of roles with an unresolved gap, and whether each gap has an owner and a date.

• The number of groups who cannot use the new way at all because something they need isn't in it.

That last one matters more than its size suggests. One group that can't use the new way, with nobody saying so out loud, teaches everyone else that sitting this one out is fine.

one small shift: report readiness by role, never as a single score. One number hides the group you most need to hear about.

Where to start

Take the change in front of you right now. Pick the three roles it touches hardest, and ask those ten questions of two people in each role. You'll have your first findings in a week, and most of them can be fixed before the date is locked.

If you have a launch coming, or an initiative that already stalled and nobody can tell you why, that assessment is the work we do first at Feed Your Brain | Consulting.

Frequently asked questions

How long does a change readiness assessment take?

The work is conversations rather than analysis. On average, a change assessment takes about 30 days. The tall pole in the tent is the interviews. For one unit, you need a conversation with someone in each affected role, a few hours watching the job being done, and a session to write up the gaps. More lines of business means more personas, not a different method.

Who should run a change readiness assessment?

Someone who does not own the launch date. A project manager whose bonus depends on going live in March will take a yellow for a green, and that is human rather than dishonest. Use an internal team from outside the program, or an outside pair of eyes, and give them access to the people doing the work rather than only to their managers.

What is the difference between a readiness assessment and a stakeholder analysis?

A stakeholder analysis maps influence: who decides, who approves, who needs to be kept informed. A readiness assessment maps capacity: what each group will have to do differently and what stands in the way. You need both, and they answer different questions. A fully mapped set of stakeholders tells you nothing about whether the work itself can change.

Can you assess readiness after a change has already launched?

Yes, and it is often the fastest way out of a stall. The questions barely change. You are asking what each role does today, which is now a mix of the old way and the new one, and where the two are still competing. You usually learn that one group never got what it needed, and nobody said so.

Is a readiness assessment worth it for a smaller change?

Scale it down rather than skipping it. Three conversations and an hour of watching the work will still show you the gap, and on a small change that is usually one role and one missing step. It will still cost you more to find after launch than before.

About this article. Tiffany Whitney is a NeuroLeadership-trained brain-based coach with 18 years of Fortune 500 Learning & Development leadership, and Amazon bestselling co-author of Strength with Kathy Ireland. Statistics are cited to primary sources; where a figure comes from an organization's internal data rather than independent research, that is noted in the text. This article is for educational purposes and is not medical, psychological, or clinical advice.

SCARF® is a registered trademark of NeuroLeadership Institute, Inc. or its affiliates. Feed Your Brain is not affiliated with or endorsed by the NeuroLeadership Institute.