Measurement · Explore

Measure readiness and resistance separately

Staff can be keen on AI and worried about it at once. Ask about the two separately. A single “readiness” score hides the worry.

When Do next. Once your first uses of AI are running.
Effort Medium (weeks, a few people)
Evidence Emerging

The main source is a review of ideas, not a test. One survey that asked the same 301 employees three times shows positive and negative reactions to AI existing side by side. No study has tested whether measuring the two separately leads to better rollouts.

Fits
Industries All industries
In the guide Enterprises

What it is

Many staff surveys ask how ready people are for AI and report one number. Ask two sets of questions instead: what makes people willing, and what makes them hold back. Report the two results side by side and never merge them into one.

What the evidence shows

  • Readiness and resistance are not opposites. A review of the research on readiness and resistance argues that the two are separate. A person can be high on both. Resistance also shows up in two ways: in what people think, and in what they do.
  • Both reactions exist in the same workforce. In a survey that asked the same 301 employees three times, people who saw the extra demands of AI as a challenge became more willing to use AI. People who saw the demands as obstacles grew anxious and less willing.
  • One reading is not enough. A review of 47 studies found that readiness is defined in many ways and usually measured only once. Its link to successful rollout remains unclear.

A team with high readiness and high resistance needs something different from a team that is low on both. The first needs its worries dealt with. The second needs a reason to care.

How to do it

  1. In your staff survey, keep questions about willingness apart from questions about concerns. Short questionnaires exist for both. ATAI gives separate scores for acceptance and fear in five questions.
  2. On the concerns side, ask about specific things: job security, loss of skill, extra workload, being monitored, quality of the tool.
  3. Ask about behaviour as well as opinion: do people use the tool, avoid it, or work around it?
  4. Report two scores per team, plus the most common concerns.
  5. Sort teams into four groups: high or low on each. Plan a different response for each group.
  6. Measure before the rollout and again during it.

What to measure

  • Willingness and concerns, as two separate scores per team.
  • Actual use against stated willingness.

Where it fails

  • Treating concerns as a fault. Some concerns are correct. Staff may have seen that the tool is wrong for the task.
  • Surveys only. People do not always report resistance. Watch what they do.
  • No action. Measuring concerns and then ignoring them makes them worse.

By company size

  • Medium: a short anonymous survey and a team discussion will do.
  • Mid-market and enterprise: results by team matter more than the company average. Give the results to line managers with guidance on what to do.

Assessments for this practice

These are existing questionnaires, tests and guides you can use. Each card gives the question it answers, who answers it and whether you can use it freely. All assessments.

Sources

  1. Repovš, Drnovšek and Kaše (2019). Change Ready, Resistant, or Both? Exploring the Concepts of Individual Change Readiness and Resistance to Organizational Change. Economic and Business Review, 21(2). What this study did and found
  2. Chang, Zhang, Cai and Guo (2024). Does AI-Driven Technostress Promote or Hinder Employees’ Artificial Intelligence Adoption Intention? A Moderated Mediation Model of Affective Reactions and Technical Self-Efficacy. Psychology Research and Behavior Management, 17, 413–427. What this study did and found
  3. Caci, Nyantakyi, Blum, Sonpar, Schultes, Albers and Clack (2025). Organizational readiness for change: A systematic review of the healthcare literature. Implementation Research and Practice, 6. What this study did and found