We optimized delivery. We forgot to ask if people could keep up

Change fatigue is a delivery risk — and it’s time project managers treated it like one

I want to start with a confession. Some years ago, during my Consultancy experience, I ran a project that was, on paper, a success. Delivered on time, tested, live. And it landed with a soft thud. Not because anything was wrong with it, but because it was the fourth new thing we’d asked the same team to absorb that year. They weren’t resisting. They were simply full. There was no more room.

For a long time I filed that under “bad luck.” I’ve stopped doing that. I now believe it was a capacity problem I failed to see — and that seeing it is part of my job.

The number that stopped me cold

Here’s the statistic that changed how I think about this. Employee willingness to support organizational change has collapsed from 74% in 2016 to just 38% a few years later. In roughly six years, we’ve gone from a workforce that mostly said “yes, let’s go” to one that mostly says “not again.”

And it’s not because people got lazy. It’s because the volume exploded. The average employee went from about 10 planned enterprise changes in 2022 to 14 concurrent initiatives, with overlap between them exceeding 60%. For the first time ever, “change fatigue” has entered the top five barriers to organizational success — cited by 44% of leaders, ranking ahead of talent shortage and economic uncertainty.

Gartner puts it starkly: less than half of employees — just 45% — actually achieve the change goals their organization sets, and only a quarter of the workforce is absorbing change at the desired pace without damaging their health. As one of their directors said, today’s change is “ungovernable; it keeps changing, is more frequent, complex and faster paced.”

Why this is a PM problem, not just an HR one

It would be easy to read all this as a wellbeing issue and hand it to HR. I think that’s a mistake, and here’s why: change fatigue directly attacks the thing we’re paid to deliver — adoption.

Think about the through-line of my last few pieces. Go-live isn’t the finish line; adoption is. You can’t have adoption without behavior change. And behavior change requires cognitive bandwidth. When a business unit is saturated, even a brilliantly designed initiative stalls, because the people receiving it “no longer have the bandwidth to engage.” Over half of change-fatigued employees are actively looking for a new job.

So when I launch my perfectly-scoped project onto an exhausted team, my adoption curve is compromised before day one. The risk didn’t come from my project. It came from the cumulative load of every project — including mine — hitting the same people. And nobody was tracking that load.

The blind spot in our governance

We are meticulous about some finite resources. We track budget to the euro. We track time to the sprint. We track headcount. But we almost never track the one resource that determines whether any of it produces value: the organization’s capacity to absorb change.

The uncomfortable truth is captured in a Deloitte finding: last year 93% of business investment went into technology, and only 7% into people. We keep buying more change and assuming the humans on the other end have infinite absorption. They don’t. Picture a glass of water that used to be half full — now it’s always one drop from overflowing.

Most governance frameworks can tell you whether a control was followed or a policy approved. Very few can answer the question that actually matters here: can leadership defend launching another initiative before the ones already in flight have been absorbed?

Treating change capacity as a project constraint

Here’s where I’ve landed, and what I’m trying to do differently. If change capacity is finite, then it deserves the same discipline we give time and budget. A few concrete shifts:

• Map the cumulative load, not just your initiative: before adding a project to a team’s plate, ask what else is landing on those same people this quarter. The overlap is where saturation lives
• Sequence and pace deliberately: change saturation is, at heart, a traffic-jam problem — too many initiatives arriving at the same intersection. Staggering go-lives isn’t weakness; it’s how you protect adoption
• Make “absorption capacity” a go/no-go input: a readiness check shouldn’t only ask “is the system ready?” It should ask “do these people have room for this right now?”
• Build change reflexes, not just training: Gartner found that employees who could apply a relevant “change reflex” were 3.5x more likely to adopt healthily — and had markedly better mental wellbeing. Capacity isn’t just protected by doing less; it’s expanded by making adaptation a practiced skill
• Watch your managers: the highest burnout rates sit with middle managers — the exact people we rely on to make change stick. If they’re depleted, the whole cascade fails

The point I want to leave you with

There’s a line from a talent director that I can’t shake:“We don’t have change initiatives anymore. We have a permanent state of reorganization interrupted by brief moments of stability.” That’s the world we’re delivering into now. Stability is the exception; disruption is the baseline.

In that world, the most valuable question a project manager can ask isn’t “can we deliver this?” We can almost always deliver something. The harder, more honest question is:“do the people have the capacity to absorb this — and if not, what should we NOT do right now?”

Because here’s the paradox I’ve come to believe. Sometimes delivering less is the fastest way to make change actually stick. Protecting people’s capacity to change isn’t the soft side of our job. It might be the most strategic thing we do.