How do you know there’s too much change at work?

That quiet is often the first sign of too much change at work. It isn’t resistance to the new idea. It’s a team telling you, without words, that it has no room left. This post is about how to see that load before it shows up as silence, and what to do about it.

How do you know there’s too much change at work?

There’s too much change when your team is starting new changes faster than it finishes old ones. The clearest signs are half-done projects, people asking which priority comes first, and new announcements met with a shrug rather than a question.

Other signs tend to travel with those. Old ways of working quietly come back because the new ones were never fully set up. People say “we tried that last year” about something you thought was finished. Good people stop volunteering ideas, because they assume the next initiative will replace this one before it matters. Meetings fill up with status updates on changes rather than the work itself.

None of this means your team is weak or that the changes were wrong. It means the total is higher than the team’s capacity to absorb it. At Coach42 we call that total change load: everything landing on a team at once, finished or not, measured against the time and attention the team actually has.

Why do senior leaders miss the signs?

Because each change looks small from where you sit. You see one decision at a time. Your team lives with all of them at once, plus the ones from last quarter that never quite finished.

Rose Hollister and Michael Watkins describe this in Too Many Projects in Harvard Business Review. They write that “leaders keep layering on initiatives,” which can lead to severe overload at levels below the executive team. The overload is real, but it sits a layer or two below the people approving the changes, which is exactly why it’s easy to miss.

The volume has also grown. Writing in Harvard Business Review in 2023, Cian O Morain and Peter Aykens of Gartner report: “In 2022, the average employee experienced 10 planned enterprise changes,” up from two in 2016. That is the organisation as a whole. Add the changes you start locally, inside your own area, and the number your team feels may be higher still.

There is a second blind spot. Most senior leaders hear about change through updates, and updates are written to show progress. “On track” tells you a project hasn’t failed. It doesn’t tell you what the team stopped doing to keep it on track.

Does too much change actually hurt performance?

Yes. Research links heavy change to tiredness, lower engagement and people thinking about leaving. It isn’t just a mood problem that passes once the change settles.

A 2022 study by C. B. Cox and colleagues in the Journal of Organizational Change Management found that “participants from organizations experiencing more change reported greater change fatigue.” In turn, change fatigue “predicted increased strain, burnout, intention to turnover and decreased engagement.” The authors’ second study also found indirect effects on teamwork and performance. These are links found in survey data rather than proof of cause, but they point the same way.

A 2024 concept analysis of change fatigue among nurses is useful here because it names what fatigue looks like up close. The authors describe it as a state of “exhaustion, decreased agency, and passive acceptance of change.” That last part matters. They call passive acceptance “a form of silent dissent.” The quiet room in September is not agreement. It may be people deciding to wait this one out.

What makes up change load?

In our experience, four things decide how heavy change feels to a team. Look at all four before you decide what to do, because the right move depends on which one is heaviest.

• How much change is landing: the number and size of changes your team is being asked to absorb right now, from above and from you.
• Changes left unfinished: the projects that are 60% or 80% done, still taking attention every week, never quite closed.
• The team’s spare capacity: how much time and energy is left once the day job is done. A team running at full stretch has no room for any change, however small.
• Explaining the why: whether people can say, in their own words, why each change matters and which one comes first.

These pull on each other. A modest amount of new change can overload a team with no spare capacity. A clear why can make a heavy load bearable for a while, but it can’t create hours that don’t exist. And unfinished changes are the quiet weight in most teams, because nobody announces that a project has stalled. It just keeps sitting on the list.

Should you pause, finish or stop a change?

When load is high, start with finishing. A change that is nearly done is costing attention every week and delivering little until it’s closed. Finishing it lightens the load and gives people a win they can see.

After that, pause what can wait. A pause is not a failure. It is a decision to protect the changes that matter most, made openly, with a date to look at it again. Stopping is the hardest of the three, and Hollister and Watkins note in the same HBR article that “it’s surprisingly hard for organizations to kill existing initiatives.” Every initiative has a sponsor, and stopping it can feel like admitting a mistake. But some changes have simply been overtaken by events, and keeping them alive costs more than letting them go.

A rough guide:

• Finish changes that are mostly done and still needed.
• Pause changes that matter but aren’t urgent, and say when you’ll revisit them.
• Stop changes nobody would miss, or that a newer change has replaced.
• Protect the one or two changes the whole plan depends on, and give them the capacity you just freed.

What does choosing what to pause look like in practice?

Here’s a hypothetical example. A director leads a customer operations area of about 60 people across four teams. Her managers seem stretched, and she has just been asked to roll out a new performance review process. Before she agrees a start date, she lists every change her area is carrying.

1. New ticketing system: launched four months ago. About 80% of teams have moved across. One team still runs the old system in parallel, so its people do some work twice.
2. Merging two regional teams: agreed in spring. The new structure is on paper, but the two teams still run separate rotas and separate meetings.
3. New quality checklist: introduced by head office in summer. Managers say it adds ten minutes to every escalation and nobody is sure it’s being read.
4. Out-of-hours pilot: her own idea, started in August. Two volunteers per team, running alongside normal shifts.
5. Training on the new refund policy: scheduled, half delivered, then pushed back twice.
6. New performance review process: the one she’s just been asked to start.

Seen together, the list tells a different story from any single update. Five changes in flight, none fully finished, and a sixth on the way. Her teams have little spare capacity, because the ticketing team is doing work twice and the pilot borrows people from normal shifts. And when she asks two managers why the quality checklist exists, neither can answer.

So she chooses. She finishes the ticketing move first, giving the last team two weeks with extra support and a fixed date to switch off the old system. She pauses the out-of-hours pilot until the new year, and tells the volunteers why and when it will come back. She asks head office what the quality checklist is for, and agrees a shorter version for routine cases. Then she goes back to her own boss with the list and a question: can the performance review process start in the next quarter, once the ticketing move is closed?

None of this took courage on a grand scale. It took a list, three decisions and one honest conversation upwards. Her team’s load drops before the new change arrives, rather than after it breaks something.

How do you explain the why without adding more noise?

Keep it short and tie it to what people already know. For each change, people should be able to say what it is, why it matters now, and where it sits against everything else. If they can’t, another all-hands is unlikely to fix it.

The nurses study above recommends information and training support to help people “understand and actively engage with changes.” In practice, the most useful thing you can explain is often the order. “This comes first, that waits until March, this one has stopped” is clearer than three separate announcements, each pitched as the top priority.

It also helps to explain what a change replaces. If a new process doesn’t remove an old one, people hear it as extra work, and they’re right. For more on why priorities get lost between layers, read why employees don’t understand your strategy. The same habits that blur a strategy blur a change programme.

How do you push back when the next change comes from above?

Bring the list, not a complaint. Show your boss every change already in flight, how far along each one is, and what your team gave up to make room. Then offer a choice: which one should pause so the new one can start?

That framing does two things. It shows you aren’t refusing the change, you’re managing the load. And it puts the trade-off where it belongs, with the people who approved the changes in the first place. Most senior teams don’t see the total either, for the same reason you didn’t at first.

If decisions about what to stop keep getting put off, that waiting has a cost of its own. We call it Decision Debt, and stalled changes are one of the places it hides.

How heavy is your team’s change load right now?

You can make the list on paper, and you should. A short self-test can help you see which part of the load is heaviest, so you know where to start.

Change Load is a free test built for that. It takes about 4 minutes, needs no sign-up, and your answers stay in your browser. You answer 12 questions across the four areas above: how much change is landing, changes left unfinished, your team’s spare capacity and explaining the why. You get a change load gauge, running from room to absorb to overloaded, and it shows your two heaviest areas, each with one move to try, so you can see what to pause or finish first.

It’s a self-rating, so it shows how the load looks from your seat. It isn’t a diagnosis of your team, and the most useful next step is often to show the result to your managers and ask whether it matches what they feel.

If you want a wider read on how you lead, including whether you protect your team’s focus when new work arrives, try The 42 Test. You’ll find more tools for this level on the senior leaders page.

Too much change at work rarely comes from one bad decision. It builds from good decisions that nobody added up. Add yours up, finish one thing, pause another, and only then say yes to the next.