Is My Team Ready for Another Change, or Already Maxed Out?
A new CRM in January. New pricing in February. A reorganized service team in March. Each change made sense on its own, and each one came with a clear reason.
Somewhere along the way, the team that used to adapt in a week started meeting every announcement with silence. No pushback, no questions, just a nod and very little movement.
Low enthusiasm isn't the same as resistance
When a team stops engaging with change, it's easy to read it as an attitude problem. More often, it's a volume problem.
Gartner's research puts numbers on it. The average employee went through 10 planned organizational changes in 2022, compared with two in 2016. Over the same period, the share of employees willing to support organizational change fell from 74% to 43%.
These are the same kinds of people in the same kinds of jobs. What changed was how much was asked of them. The volume wore down the willingness, not the other way around.
Your team's capacity for change is finite. When it runs out, even a good change gets a flat response.
Why changes pile up in a small business
Few owners set out to overload their team. The pile-up happens through ordinary decisions.
Each change is decided separately. You see each one as a single, reasonable request. Your team experiences all of them at once, on top of the work they were hired to do.
Changes don't finish. They fade. A half-adopted change still costs energy: two systems running in parallel, two ways of doing the job, and constant uncertainty about which one counts.
The same few people carry every change. In a 20-person company, the same three or four people end up as the trainers, testers, and early adopters for every new initiative. Their capacity runs out first, and everyone watches how they respond.
Every change competes for the same follow-through. A single change stalls quickly when the owner's attention moves elsewhere, which we covered in Why Does Everything Stall the Moment I Stop Asking About It? Five changes in flight means each one gets a fraction of that attention, at best.
Signs your team is at capacity
New announcements get silence instead of questions. Questions are a sign of engagement.
Your most reliable people start asking, "Is this one actually going to stick?"
Workarounds show up faster than they did with earlier changes.
Changes launched earlier in the year are quietly half-used.
You can't list every change currently in flight without stopping to think.
That last one matters most. If you can't see the full load, you can't judge whether there's room for one more.
How to check before you launch the next one
1. Count what's in flight. List every change you've introduced in the last 12 months. Mark each one: fully in place, partly in use, or fading. The fading ones still cost your team something.
2. Finish or formally stop. Before adding something new, either close out an existing change or officially retire it. A change you retire on purpose frees more capacity than one you let die quietly, because the team stops carrying the question of whether it still applies.
3. Ask the people carrying it. Don't ask "Can you handle one more?" Almost everyone says yes. Ask "What would have to come off your plate for this to work?" The answer tells you what the change will actually cost.
4. Sequence instead of stack. If the January change needs the team's full attention through March, the next change waits until April. Spacing changes out feels slower, but it's usually the fastest way to get all of them to stick.
If you're still building next year's list, cutting priorities before you finalize them helps. This check is about what's already running, because that's where the hidden load lives.
Know where your team stands before you add more
The free Change Readiness Assessment shows where your team stands right now, so you can see the gaps before the next change lands on top of them.
If the results raise questions, or you already know your team is stretched and need to decide what comes next, bring it to Office Hours.
