Employee Engagement During Change: What to Measure

The new structure went live three weeks ago. The project plan is green, your managers say their teams are fine, and the questions have stopped coming. Nothing looks wrong. It is just quieter than it was.

Engagement during a change usually drops before anyone says so, and it shows up in what people do rather than in what they tell you. Fewer questions. Slower replies. People doing what was asked and nothing past it. You can see it early if you measure behavior instead of feelings about the change, and if you ask your managers' teams rather than only your managers.

Key takeaways

Quiet is a signal, not agreement. During a change, people stop asking before they start complaining, so a drop in questions is usually the first thing you can see.

Your engagement survey is looking backward. Annual and semi-annual numbers describe the organization you had before the announcement.

How people feel about the change does not predict whether they do it. Satisfaction scores and program ratings are easy to collect and weak at telling you anything about adoption.

Measure by team, not by company. Averages hide the two or three groups where the change has already stopped.

Ask the people, not the manager. Managers tend to rate their own handling of a change higher than their teams do.

How does organizational change affect employee engagement?

A change does not make people care less about their work. It changes what they are willing to spend energy on while they wait to see how things land.

That shows up in small, reasonable decisions. Someone stops raising the awkward question in the team meeting because the answer last time was that it was still being worked out. Someone keeps running the old process alongside the new one, because the old one is the one they can explain to a customer. Someone who used to volunteer for the pilot waits to be assigned. None of this is defiance. It is people protecting their ability to get through the week.

Back in 2020 I sat in on a webinar about change and motivation, and the presenter put up a simple chart of engagement levels and the behaviors you see at each one. It struck me in its simplicity, so I shared it across the company, and a colleague asked the best question in the thread: how do engaged people stay engaged? Part of the answer is what the individual does. The bigger part is that managers move people up and down that chart without realizing it, through the ordinary things they say and do not say.

So the work right now is not persuading anyone. It is finding out which teams have actually changed what they do, and which have not.

One small shift: this week, count the questions. Ask three managers how many questions their team asked about the change in the last five working days, and compare that with the week of the announcement.

Why the quiet is not the same as resistance

When people go quiet during a change, the usual reading is resistance. That is almost always the wrong place to start, because it makes you look for people to persuade instead of the information you are missing.

There is a plainer explanation. In its 2019 review of speaking up, the NeuroLeadership Institute argues that three things hold people back. They are not sure whether it is their place to say something. They are lower in the pecking order than the person they would have to challenge. And they can see what it might cost them socially. A restructure touches all three at once. People are not sure who owns what yet, the person who could answer is now two levels up, and nobody wants to be the one who looked negative in the first month.

I have watched an initiative lose most of a year this way. One group genuinely could not do the new process, nobody raised it, and everyone else drew their own conclusion about how seriously the change was meant. At the time it got called resistance. It was a gap nobody mentioned, and the quiet around it got read as a decision.

I have written the longer argument about why teams pull back separately, in psychological safety and change. The rest of this piece focuses on what you can act on this month: measurement.

Why your engagement numbers stay quiet too

Three things go wrong with the numbers you already have.

The timing is behind the change. An annual survey tells you about the organization that existed before the announcement. By the time the next one runs, the window to fix something cheaply has closed.

Satisfaction is not adoption. At the Fortune 500 company where I led learning and development, we measured a coaching program both ways. Two-thirds of the participants who answered were promoters on a net promoter question, and the report carrying that number said plainly that attitude scores do not predict behavior change. That was a small, voluntary, self-reported sample, and it is still the most useful line in the whole report. People can like a change and not do it, and they can be unimpressed by it and do it anyway.

Almost nobody tracks enough to see a pattern. When the NeuroLeadership Institute interviewed talent practitioners about how they measured their growth mindset work, engagement scores were the most common yardstick, usually by adding a few questions to an existing pulse survey, and only 23% of the 16 organizations tracked more than three indicators. Most relied on stories of behavior change rather than numbers. That is the institute's own interview data from a small set of companies, so read it as a description of common practice rather than a measurement of it. It matches what I saw running change programs. The measurement plan is the part that gets written last and cut first.

How do you measure engagement during a change initiative?

You need two kinds of signals, and you can collect both in a week.

The first kind is behavioral. Not opinions, just whether the new way of working is happening. Pick three or four things a person would actually do if they had adopted the change, and count them: orders entered in the new system rather than the old one, exceptions logged rather than worked around, the new step appearing in a team's own meeting agenda. Those are countable, and they are hard to fake.

The second kind is what people are saying to their own manager. This is where most measurement goes wrong, because the organization asks the manager how it is going instead of asking the team.

That gap is measurable. In a virtual change program run with 700 managers, the managers rated their own skills higher after the program, and their direct reports saw a smaller but real improvement. That is the NeuroLeadership Institute's own program data, not an experiment: there was no control group, and one survey asked people for their before-and-after ratings in the same sitting. The direction still holds up against everything I have seen: the manager's view of how a change is going is the most optimistic view available to you.

Measure by team as well, not across the company. Gallup's 2015 State of the American Manager analysis found that at least 70% of the variance in employee engagement scores across business units is attributable to the manager. That is a finding about managers generally, not about any one practice. If it is roughly true where you work, a company-level average during a change is close to useless. It will hold steady while two branches quietly stop.

Five questions worth asking a team directly, in a fifteen-minute conversation with no manager present:

What has actually changed about your day since this went live? You are listening for whether anything has.

What are you still doing the old way, and why? The why is the useful half. Sometimes the old way is better and nobody above you knows it yet.

What is the question you have asked and not had answered? If nobody has a question, that is your finding.

Who would you call if this went wrong today? When a change has not landed, nobody is sure yet who owns it.

What would you tell me if you knew nothing bad would come of it? Ask it plainly, then sit through the pause.

one small shift: before your next change review, pick the two teams furthest from the project team and talk to five of their people without their manager present. Bring what you hear to the review as a standing item, not as an exception.

What questions should leaders answer during times of change?

People are usually asking four things, whatever words they use: what changes for me, when will I know, who decides, and what happens if this does not work.

You will not have all the answers, and pretending otherwise costs you more than the gap does. What you can do is answer the part you can answer, in your own words rather than the project deck's, and come back on a schedule people can rely on.

Say it more often than feels necessary. People are rarely confused about a change. It slides down a list that was already too long, and the thing most of them want is not more training but a reminder from someone who has not lost interest in it.

Then close the loop out loud. When somebody raises something and you act on it, name both halves in the next update: here is what you told us, here is what we did. When you cannot act on it, say so, and say why. On a system rollout I sponsored in 2019, one of the things we leaned on was the product's own Help Us Improve button. Many times people want to be heard, and this gives them a voice.

How do you keep employees engaged during a restructure?

A restructure is the hardest version of this, because the thing people want certainty about is the thing you cannot promise. A few moves still work.

Shorten what you promise. You may not be able to say what the team looks like in April. You can usually say what this week holds and who someone reports to on Monday.

Keep people's work visible. In a reorganization, the fastest way to lose a good performer is for the record of what they have delivered to disappear with their old manager. Write it down and pass it on.

Offer choices where you have them. The best thing a manager can do in this situation is offer choices, and most managers have more to offer than they think: sequencing, who pairs with whom, which part of the new scope someone takes first.

Protect one thing that is not changing. A team meeting that stays on the same day at the same time does more for steadiness than another announcement.

Make the manager's job smaller. Managers in the middle of a restructure are carrying their own uncertainty and their team's. Give them three things to do and say this month, not a toolkit.

Use what you learn on the next one. Most of what these conversations tell you belongs at the front end of the change after this, which is what assessing change readiness is for.

one small shift: give every manager one sentence they are allowed to repeat, in their own words, about what is settled and what is not. Then ask them next week which part their team pushed back on.

A belief worth checking

Most leaders I work with carry a version of the same belief during a change: if people were disengaged, I would hear about it. It is worth running through The Shift Method, because it is the belief that keeps the measurement plan at the bottom of the list.

Identify the belief. If something were really wrong, someone would tell me.

Question the evidence. Who told you last time, and how long after it started? If the answer is a manager, in a monthly review, then what you have is a reporting line rather than evidence.

Reframe it. People tell me when telling me is easy and worth it. During a change, it is neither.

Picture what you want instead. You want to hear about a stalled group in week two from someone who is not that group's manager, and you want it to be routine rather than brave.

Act. Put one unfiltered conversation a week in your own calendar for the length of the change, and a behavioral count on the same page as the project status.

What I would do first

Engagement during a change is not a mood to be managed. It is information about whether the change is working, available earlier and more cheaply than any other signal you have, and most organizations throw it away by asking the wrong people in the wrong month.

I spent 18 years as a Senior Director of Learning and Development in a Fortune 500, leading national rollouts that reached thousands of employees and customers, and I am a NeuroLeadership-trained brain-based coach. The measurement plan is the piece I would now build first rather than last.

If a change you have launched has gone quiet and you want to know what is really happening inside it, that is the work I do with leadership teams at Feed Your Brain | Consulting.

Frequently asked questions

How does organizational change affect employee engagement?

It changes behavior before it changes attitudes. People narrow what they take on, keep running the process they can defend, and stop raising questions that came back unanswered. Most of that is sensible self-protection rather than opposition, which is why it is easy to miss and easy to misread as everything being fine.

How do you measure engagement during a change initiative?

Count behaviors rather than feelings, and do it by team. Pick three or four things someone would do if they had adopted the change, track them weekly, and pair that with short conversations held with teams rather than with their managers. Company-wide averages and annual surveys both move too slowly to help you.

Why do employees resist change?

Often they are not resisting. Quiet usually means people are unsure whether it is their place to speak, the person who could answer is too far up, or raising it looks costly. Genuine resistance is usually specific and reasonable once you hear it. There is more on what sits underneath it in my piece on psychological safety and change.

How often should you measure engagement during a change?

Weekly for behaviors, monthly for conversations, for as long as the change is still being adopted. The point is not more surveys. It is a cadence short enough that you find out about a stalled team while fixing it is still cheap, which an annual cycle cannot do by design.

Our engagement scores look fine but the change is not moving. What now?

Believe the change, not the score. Scores built before the announcement, or averaged across the company, will look healthy while two or three groups have quietly stopped. Find those groups through behavioral counts, then go and talk to them directly rather than sending another survey.

Should managers run these conversations themselves?

They should have their own, and you should not rely on them alone. Managers tend to rate how well a change is going more highly than their teams do, which is human rather than dishonest. Someone outside the reporting line needs to hear it too, on a regular schedule rather than when something has already broken.

About this article. Tiffany Whitney is a NeuroLeadership-trained brain-based coach with 18 years as a Senior Director of Learning and Development in a Fortune 500, and the Amazon bestselling co-author of Strength with Kathy Ireland. Every figure here was checked against the primary source it came from, and research findings are described with the limits the original reports state. This article is general professional guidance on leading organizational change. It is not medical, psychological or clinical advice.