Change Fatigue – Why Project Team Capacity is a Delivery Risk

Someone who used to raise their hand stops raising it. A person who was generous with their time starts guarding it. Meetings get a little more reactive, a little shorter. People stop bringing problems forward because they’re already carrying too much.

It’s not loud. But it keeps showing up. I’ve watched this happen to capable, committed people more times than I can count. And it matters for more than their well-being.

When a project team's capacity starts to disappear, so does some of the capacity required to deliver change well.

Your team isn’t resisting the change. They’re tired of the last five.

When a change stalls, one of the easiest stories to tell is that people are resisting. I understand why that story is appealing. It gives us something or someone to point to. But before we call it resistance, we need to look at what people are carrying.

The volume of organizational change is significant. Gartner reported in 2025 that the average employee faces 13 enterprise-wide changes each year. In a 2024 survey of HR leaders, 73% said their employees were experiencing change fatigue.

Those numbers tell us something important about the context in which project teams are being asked to deliver. This change may not be the only change.

It may be one of many, alongside shifting priorities, new technology, organizational restructuring, leadership changes, and day-to-day demands that haven't disappeared because a transformation is underway.

So when a project team seems to be dragging its feet, pause before you call it resistance.

What looks like resistance may be accumulated fatigue—the effect of carrying multiple changes, competing priorities and unresolved demands for longer than anyone intended.

The wider picture isn’t helping

This isn’t happening in a vacuum. The ground your project team is standing on may already be shaky.

Gallup's 2026 State of the Global Workplace report found that global employee engagement fell to 20% in 2025, its lowest level since 2020. Manager engagement fell from 27% in 2024 to 22% in 2025. For organizations operating in Canada and the U.S., there’s another useful piece of context: Gallup found 50% of employees in the region experienced significant daily stress in 2025.

I don’t think we need another page of statistics to understand what that means for a project team. People are delivering change inside organizations where many of them are already stretched.

This isn’t an excuse. It’s context.

And context matters because capacity doesn’t exist independently of the conditions around us.

As I wrote about in Why Project Decisions Create Organizational Conditions, project teams aren’t only working inside conditions. Through their decisions and ways of working, they’re continually creating them too. A capable team can become less ready to do the work change requires when attention is fragmented, priorities are competing, and people have been operating at capacity for too long.

That doesn’t make them less capable. It changes what they have capacity for.

Why fatigue is a delivery risk, not just a wellbeing issue

I care about the human cost of this first. I always will. But let me also be practical, because sometimes that’s the language that gets people the support they need. A fatigued team doesn’t necessarily stop working. It starts losing capacity for some of the things that make good change delivery possible.

People may be less likely to raise the uncomfortable question. They may stop surfacing the risk they can see coming. They may have less patience for the conversation that needs another twenty minutes. They may narrow their focus because narrowing their focus is sometimes the only way to keep going.

But good change delivery asks us to do almost the opposite.

To see across functions.

To challenge assumptions.

To work through ambiguity.

To notice what a decision might create downstream.

To stay curious when it's easier to move on.

Those things require capacity.

And that’s why I see capacity as one part of Project Team Readiness.

Project Team Readiness isn’t the same as Stakeholder Readiness. Stakeholder Readiness is about the people impacted by the change being able to understand, navigate and ultimately adopt it.

Project Team Readiness starts earlier and continues throughout the lifecycle. It asks whether the team creating the change has the clarity, shared understanding, ways of working and capacity needed to create and deliver it well.

The two are different. But they’re deeply connected.

The conditions a project team works in influence how the team works, the decisions it makes, and the experiences it creates. And those experiences become part of the conditions in which everyone else will eventually experience the change.

What helps a tired team

A pizza lunch isn’t going to solve change fatigue. But that doesn’t mean the pizza lunch doesn’t matter. Appreciation matters. A team lunch, a celebration, a genuine thank you or taking the time to recognize what people have contributed can help people know their effort is seen.

The problem is when appreciation becomes a substitute for addressing the conditions creating the strain. If the workload is unsustainable, priorities keep competing, roles remain unclear, or people don’t feel they can say what they’re carrying, appreciation alone won’t solve the problem.

In fact, when recognition is offered without acknowledging those conditions, it can unintentionally send the wrong message:

We see how hard you’re working. Now please keep working this way.

What helps is more honest and more structural. Capacity gets named instead of quietly absorbed. Priorities get examined rather than endlessly added. Roles and ownership become clearer. People can raise concerns without becoming the problem for raising them.

Teams have space to work through ambiguity rather than being expected to manufacture certainty they don’t yet have.

And people have opportunities to make sense of what’s happening together.

We can’t keep asking people to become more resilient while leaving the conditions exhausting them untouched.

That’s part of the work I do through Project Team Alignment, helping teams see what they may have stopped seeing, understand what’s really happening, and build enough shared understanding to make better decisions and create stronger conditions for readiness and adoption.

Being involved changes our relationship with change

There’s another part of this that matters. People need to feel seen and heard about what the change is asking of them. They also need opportunities to make sense of what’s happening, rather than absorbing one decision after another.

Being involved doesn’t make a heavy workload disappear. But there’s a meaningful difference between carrying hard work you understand and have some agency within, and continually absorbing change you feel you have little influence over.

That’s why participation isn’t only about making people feel better about change. It can change their relationship with it. And that matters for the team creating the change just as much as it matters for the people who’ll eventually be asked to adopt it.

If you’re watching your team run low

Maybe you’re the one carrying the project, and you can feel your team getting quieter. Fewer questions. Less pushback. Less curiosity. A flatness where energy used to be. Maybe you’re running low yourself, holding it together for everyone else the way you always have.

Before you label what you’re seeing as resistance, disengagement or a performance problem, get curious about the conditions underneath it.

What is this team carrying?

What are they compensating for?

What are they no longer saying?

And what capacity does this work require that they may no longer have?

Those aren’t soft questions. They’re Project Team Readiness questions. Because the readiness of the people receiving a change matters enormously. So does the readiness of the team creating it.

This is part of what Project Team Alignment exists to support: the messy middle of delivery, where teams are carrying the work while continuing to create the conditions everyone downstream will eventually experience.

If you’re seeing this in your own team, or feeling it yourself, I’d love to talk it through.

No pressure. Just a real conversation about what your team is carrying, what may be getting in the way and what might need to change.

Book a coffee chat with me.

We spend a lot of time asking whether the organization is ready for the change. It’s worth asking whether the team creating it has what they need to lead it there.

Lisa Blanchet, Creating Space for Change

Book A Call

Get on my Calendar

Explore our services

Take Me to Services

Change Fatigue: Why Project Team Capacity is a Delivery Risk

Your team isn’t resisting the change. They’re tired of the last five.

The wider picture isn’t helping

Why fatigue is a delivery risk, not just a wellbeing issue

What helps a tired team

Being involved changes our relationship with change

If you’re watching your team run low

Responses

Book A Call

Explore our services

Creating Space for Change Blog

Tips, tools & resources to help you create lasting change.

Please take a moment to let me know how I can help you and/or your company create space for change.