Measure change readiness team by team, because a single organisational score can hide differences in preparation. Gartner reported in July 2025 that 32% of the business leaders surveyed felt their most recent change initiative had reached healthy employee adoption. Measuring change readiness therefore takes more than one overall score.
Teams respond differently, but hesitation is sometimes too quickly labelled as unwillingness. Without a view of the causes, you are left guessing whether employees lack knowledge, motivation, practical room or trust. And even clear results change nothing as long as nobody is responsible for the follow-up.
This article offers a practical framework to measure change readiness per team and understand differences. You will see which signals to map, how to involve employees transparently and how to handle privacy carefully. You then translate findings into concrete actions, with an owner and an agreed follow-up moment. That way the measurement becomes a well-grounded starting point for the next change step, not a report that disappears into a folder.
Key takeaways
- Tie the measurement to one concrete change, so you can interpret results purposefully.
- Map knowledge, motivation, practical room, trust and perceived impact separately per team.
- Choose between a fixed measurement method, a baseline measurement or pulse measurements based on your goal and the depth you need.
- Use measuring change readiness as a starting point for actions with an owner and an agreed re-measurement moment.
- Match questions to the day-to-day work reality, so teams can name the barriers and needs that are relevant to them.
Table of contents
- What does measuring change readiness mean for a change initiative?
- Which signals show where teams are ready for change?
- Which measurement approach fits change readiness?
- How do you measure change readiness carefully and turn results into action?
- How does elli make change readiness usable for the next step?
What does measuring change readiness mean for a change initiative?
A change initiative does not touch teams in the same way. A new system may mostly mean new steps for one group, while another group has to adjust planning, responsibilities and customer contact at the same time. Measuring change readiness brings those differences into view. Not to label employees as supporters or opponents, but to see what helps or hinders them in getting to work with a concrete change.
In the context of change management it is about more than communicating the goal. Also map how the change affects day-to-day work and what support teams need. A related way of thinking is measuring workforce readiness, where mental and practical preparation are looked at together.
What exactly does an organisation measure?
Change readiness is the mental and practical preparation of employees for a specific organisational change. It is not a fixed personal trait. Someone can consider a change important and at the same time doubt whether there is enough time to learn new ways of working. Readiness therefore also depends on context, timing and support.
In your measurement, distinguish between four concepts:
- Willingness: how open or motivated someone is to support the change.
- Capacity to change: whether someone has the knowledge, skills and practical room to change along.
- Buy-in: to what extent employees support the goal or the chosen approach.
- Actual behaviour: what people really do, such as following a new procedure or using a system.
Those signals are connected, but they are not the same. An employee can support the goal and still not know how a new way of working should be carried out in practice. People also experience the same change from different roles. A planner, team lead and IT specialist can each face different consequences, questions and dependencies.
Why a general buy-in score falls short
A single average score gives an overview, but can hide important differences. An organisation-wide survey can for example show a positive overall attitude, while one team still has insufficient training or time to apply the change. So split results out by relevant teams or roles. That way you see where extra explanation is enough and where processes, capacity or guidance need attention.
Treat resistance as a signal to investigate further, not as evidence of unwillingness. Hesitation can point to uncertainty about what is changing, missing knowledge or practical barriers in the work. Ask about the cause before you choose an action. An extra presentation for example helps little if the team mostly lacks time to practise the new approach.
Change readiness is the mental and practical preparation of people to understand, support and apply a specific change in their work. That definition makes the measurement usable: you do not assess personality, but map what each team needs to take the next step.
Which signals show where teams are ready for change?
A usable measurement makes visible where preparation is faltering. So do not only poll whether employees support a change. Also map knowledge, motivation, practical room, trust and perceived impact separately. Tie each signal to the change itself. When introducing a new planning method you want to know, for example, whether employees understand the goal, know what is changing in their work and get enough time to practise with it.
Which dimensions deserve a place in the measurement?
Ask targeted questions about what teams have to do. That way you discover not only that there is uncertainty, but also at what point it arises.
- Knowledge: do employees understand why the change is needed and what the desired result is?
- Motivation: do they see the added value for their work, customers or collaboration?
- Practical room: do they have the time, tools and support to apply the new approach?
- Trust: can employees ask their questions and do they get clear answers about the consequences?
- Perceived impact: do people know which tasks, agreements or responsibilities are changing for them?
Make the questions concrete. Do not only ask whether someone feels prepared, but also which step is still unclear. For a new procedure, poll whether employees know where to find instructions. For an adjusted division of tasks, ask which handovers require extra coordination. That way measuring change readiness connects to day-to-day reality instead of general impressions.
A score is an indication, not evidence of the cause. A low score on practical room can relate to workload, planning or unclear priorities. Use open answers or conversations to explore possible explanations. Do not draw a conclusion based on one number. Note which explanations still need to be tested and who will hold the conversation with the team.
How do you recognise differences at team level?
Only compare teams when their context and impact resemble each other sufficiently. A team that uses the new way of working daily experiences the change differently from a team that mostly receives reports. Note therefore which tasks, processes and dependencies are changing per team. That makes differences interpretable and prevents a number without context from being used as a ranking.
A team level score can summarise multiple signals and help spot points of attention quickly. Use that score as an entry point, not as a final conclusion. Also look at the underlying dimensions: the same overall score can go together with trust but little practical room in one team, and with sufficient capacity but many questions about the goal in another.
Team scores complement an organisational average by showing where the change task is experienced differently per team. Use those differences to choose follow-up questions and plan appropriate support. Record which questions get priority and discuss with team leads which signals should be investigated further first. That way it becomes clear where additional explanation, practical support or an adjustment of the approach is most relevant.
Which measurement approach fits change readiness?
The measurement method should fit the decision you want to take with the results. If you want a view of possible barriers before the start, a baseline measurement helps. If you want to use a fixed model as a structure, a model-based approach can give direction. If you want to track how signals evolve, repeated pulse measurements are suitable. No single approach is automatically the best.
So start with your change goal. Determine which teams will experience the change, which choices the measurement should support and when you will discuss the outcomes. Only then choose the questions and format. That way you avoid letting the instrument set the agenda instead of the day-to-day reality of the change initiative.
DINAMO, baseline measurement or pulse measurement?
DINAMO is a model-based way to investigate change readiness. It gives structure to the diagnosis, but still requires translation to the change and work situation you are investigating. Use it when you need a coherent picture of change factors, not just a quick indication.
A baseline measurement maps the starting point before the actions. Record which questions you ask, which teams you involve and how the results lead to follow-up. After that you can use pulse measurements to gather signals again at agreed moments. Keep the questions targeted, so you can discuss changes without presenting employees with the same broad survey each time.
- Choose a model for a structured diagnosis of factors around change.
- Choose a baseline measurement when you first need a reference point for actions and later follow-up.
- Choose pulse measurements when you want to look at specific signals again throughout the initiative.
A short poll suffices when you have a bounded question, such as whether teams know where they can go with questions. A deeper diagnosis is more useful when answers can have multiple explanations or when several work processes are changing at the same time. In that case follow-up questions and conversations give more grip than a single overall score.
When does segment analysis help more than a single overall figure?
Segment analysis groups people who experience their work in a comparable way. Think of teams with the same process or a comparable role in the change initiative. Use such groups to see where experiences diverge. Do not treat segments as labels for individual employees and do not draw conclusions about someone’s motivation based on group results.
Only compare results when the context matches. A team that uses a new system daily is not simply comparable to a team that only supplies data. So alongside the results, also record what is changing in the work per group. That way you tie differences to concrete circumstances and test possible explanations instead of making assumptions.
elli brings surveys and workforce analytics together to make change readiness and underlying factors visible at team level. The first dashboard opens from fifteen responses. The measurement is a starting point for interpretation and follow-up, not the action in itself. So match the measurement approach to the question you want to answer and to the step teams need next.
How do you measure change readiness carefully and turn results into action?
A careful measurement does not start with the questionnaire, but with the decision you want to support with it. Do you have to determine which teams need guidance first? Do you want to check whether employees understand the consequences of a new way of working? A sharp measurement question helps you ask targeted questions and translate results into a next step.
From measurement question to usable baseline
Before the start, record what is changing, which teams are affected and which signals you want to track. Phrase questions in understandable language and tie them to concrete tasks. For a new digital process you can for example poll whether employees know where to find support and which step in their workflow is unclear. Avoid questions that are detached from the change or that ask about several things at once.
A measurement model for workforce readiness can help to arrange signals in a consistent way. Then adapt the measurement structure to the context. A team that carries out a process has different questions from a team that tracks progress. Repeat the same core questions in a later measurement if you want to compare changes in the results.
Be transparent before participation. Explain why you are measuring, who can view the results and how you report answers. Also describe how anonymity works in the measurement set-up. Make clear whether results are summarised at group level and how you prevent small groups or recognisable answers from being traced back to individual employees. Explain which data is kept, for what purpose and how it is protected. That way employees know where they stand when they participate.
From finding to owner and follow-up
Share the main patterns with the teams involved. Explain what you see and test your interpretation against their work experience. A low score on clarity can for example relate to contradictory instructions, but employees may indicate that it is mainly the timing that is unclear. So treat the outcome as a starting point for conversation, not as evidence of a single cause.
Tie each identified barrier to a fitting action and someone responsible. If teams do not know where they can get help, a clear support route may be needed. If practising is hard to schedule, discuss with operational leadership how to make room for it. For each action, note what happens, who follows up and when you will discuss progress.
- Feedback: share results and discuss what they mean in practice.
- Action: choose a measure that fits the tested cause.
- Ownership: assign a single person responsible and agree a follow-up moment.
- Re-measurement: at that moment, look again at the relevant signals.
A score without feedback and follow-up gives little direction. Employees should be able to see what happens with their input. So plan the discussion and the re-measurement moment before you send out the baseline measurement. That way measuring change readiness becomes part of the execution, not a loose report alongside the initiative.
How does elli make change readiness usable for the next step?
A measurement only has value when you can connect the outcomes to decisions and follow-up. elli is a workforce-intelligence platform that brings surveys together with analysis of workforce data. That gives you a view of signals per team and possible factors connected to them. That helps you set priorities. Interpretation remains human work: numbers point to a direction, but do not tell on their own why a team experiences a barrier.
From team result to targeted change action
A team result can for example show that employees have little trust in the support around a new way of working. That is an indication to investigate further, not evidence that communication is the cause. Discuss the finding with the team and test which circumstances are playing a role. Think of unclear instructions, insufficient room to practise or dependencies with other teams.
Translate what you learn into actions at the right level:
- Organisation level: clarify the change goal or adjust agreements that apply across several teams.
- Team level: plan extra practice, make responsibilities clear or arrange targeted support.
- Individual level: make room for a conversation or appropriate help, without using a group score as a judgement about a single employee.
Use the results to choose priorities, not to weigh teams against each other. Agree on who follows up an action and when you will discuss the effect again. A conversation with employees remains essential. Data helps you listen more purposefully and ask follow-up questions; it does not replace the team’s experience.
The first dashboard opens from fifteen responses. That threshold gives access to a first view, but does not by itself prove that every team is sufficiently represented or that a pattern shows the cause of a problem. So always look at the context of the answers and be clear about what you can and cannot infer from the results.
When human readiness is decisive for AI adoption
With AI change it is not enough to make technology available. Employees have to understand how it affects their tasks, know how they can get to work with it and get room to learn a new way of working in practice. If that preparation is missing, usage can lag behind, even when the technical solution is ready.
Measuring change readiness helps you make the human side of that transition discussable. Combine team signals with conversations about work processes and determine where guidance is most needed. That way you connect the ambition around AI to what teams need to apply it in their day-to-day work. Also read the white paper on human readiness and AI adoption.
Turn insight into a feasible next step
A change initiative does not have to wait until every uncertainty has disappeared. Pick one concrete question that is currently blocking a decision. Determine which team is most directly affected and discuss what it needs to be able to move on. That way measuring change readiness becomes part of the execution, not a separate exercise alongside the work.
Next, record what you can adjust in the short term. That could be a clearer work instruction, extra room to practise a new approach or a conversation about the consequences for roles and responsibilities. Agree who follows up the step and when you will look together at whether it helps. That way the change stays connected to day-to-day practice and teams can keep sharing their experiences.
With AI change, human preparation is an important starting point. So do not only look at the technology, but also at what employees need to apply it thoughtfully in their work. Choose a concrete next step and designate someone to take on the follow-up.
Frequently asked questions about change readiness
What does measuring change readiness mean?
Measuring change readiness means checking how prepared employees are for a specific change. Use the outcome to determine where you can adjust explanation, training or practical support. When introducing a new work process, one shift may for example first need a clear work instruction, while another shift mostly needs to know who answers questions. The measurement gives direction, but does not explain behaviour on its own.
How often do you measure change readiness?
Measure at moments when the outcome can influence a decision. For example, start before a trial period and gather signals again after teams have used the new way of working. Plan the next measurement around a concrete milestone, such as the roll-out to another department. That way you can follow up on what changed and where adjustment is still needed, without surveying employees at fixed moments that have no connection to the initiative.
Is a change-readiness measurement anonymous?
That depends on the measurement set-up and the way results are shared. Before participation, explain who has access, whether answers are processed at group level and what data is kept. Pay extra attention to small teams. Even without names, details about role, shift or situation can make someone recognisable. So limit unnecessary breakdowns and only promise anonymity when the design of the measurement supports that promise.
Can you measure change readiness without surveying employees?
You can use behavioural data to see what is happening, but it does not automatically show how employees experience the change. A drop in the use of a new system can for example relate to access problems, a busy period or unclear instructions. A survey or conversation can help investigate those possibilities. Combine data purposefully and do not use it to psychologically assess individual employees.
What do you do when the response rate on a measurement is low?
Be careful with conclusions: those who answered may not represent all teams or roles. First check whether the invitation was clear and whether employees knew what their answers would be used for. Make room to share feedback through a conversation as well. In the reporting, note which groups are poorly represented and what uncertainties that creates. Postpone far-reaching actions if the available answers do not provide a solid starting point for them.
What is the difference between change readiness and resistance?
Change readiness is about how prepared people are; resistance is a possible reaction to what the change means for them. An employee can support the goal and still have objections to the timing, for example because a new procedure coincides with a busy work period. So ask what sits behind the reaction. That way you can distinguish between a lack of clarity, practical hindrance and a substantive disagreement.
Read the white paper on human AI readiness and determine your next step