resilient tree bending with the wind
Editorial

Why Demands for More Resilience From Our Teams Are Failing

5 minute read
Rachel Cooke avatar
By
SAVED
You can't demand resilience and ignore the conditions creating the strain. What leaders owe the teams they're asking to keep adapting under pressure.

Every leader I talk to right now is saying some version of the same thing: we need our teams to be more resilient, more agile, more adaptable to change.

They're not wrong.

The pace of change is real. Expectations and pressure are high. It tracks that leaders want resilient, agile, adaptable teams. But wanting this alone doesn't entitle them to it.

People are being asked to absorb tremendous organizational demands in the face of AI anxiety, job insecurity, economic uncertainty, political instability and more. These aren't distractions from work. They're the conditions under which work is happening.

Forty percent of employees globally now fear losing their jobs to AI, a number that has jumped twelve points in two years. Most aren't saying this out loud. They're showing up to meetings, nodding through strategy updates, and delivering status reports while quietly calculating what AI means for their role, their relevance and their future.

All of these realities become like programs running in the background, quietly consuming processing power long before anyone notices a slowdown in performance.

Leaders can ask for resilience. They can ask for agility. But those asks come with an obligation. If people are expected to keep adapting under pressure, leaders have to create the conditions that make adaptation possible. Otherwise the message becomes simple: absorb more, recover faster and treat the strain as your own responsibility.

Leaders are effectively telling their teams that resilience and change agility are the drivers of our success. And if we don’t succeed, it’s your failure. Missing from that equation is a recognition that adaptability is shaped by the environment people are asked to operate in, not just by their personal capacity to absorb change.

The Operating Failures Hiding Behind the Resilience Label

Resilience language can hide a set of leadership habits that make adaptation harder, then leave employees responsible for coping with the strain.

Urgency used as a substitute for prioritization

When everything is urgent, leaders have not prioritized. They have delegated prioritization to the team by default.

The team has to figure out what really matters, absorb the cost of guessing wrong, and repeat the exercise when the next urgent thing arrives.

That’s not agility, but an operating failure.

Declaring everything urgent is still a decision. It just pushes the hard part — figuring out what actually matters — down to people who don't have the authority or the information to make that call well. When pressure is high, leaders owe their teams a real answer about what matters most and what can wait, slow down or get done with less care. Everything else is delegation disguised as urgency.

Resource cuts treated as invisible adjustments

Headcount goes down. Budget shrinks. Scope stays the same.

Then, when the team strains under that math, the conversation becomes about their ability to do more with less.

“Do more with less" is a way of avoiding a harder conversation about what actually has to change.

If resources shrink and expectations stay fixed, something else has to change. Maybe the decision process gets faster or approvals are streamlined or meetings are eliminated or altered. Maybe the team gets clearer authority to make tradeoffs without escalating every call. Or leaders stop asking for the same level of polish on work that no longer warrants it.

The point is leaders don’t need to lower the bar to infuse ease into the system. But they do have to change the operating conditions around the bar. Don't, and you don't have a resilience problem. You have a leadership problem.

Hesitation read as resistance

When a team slows down on a new initiative, the default interpretation is often lack of buy-in.

But hesitation can mean many things. It may mean people are doing risk math the leader hasn’t done yet. They may see downstream complications invisible from the leader’s vantage point — a likely but unfortunate customer impact, an operational dependency, the need for systems that don’t interact well to interact well.

Or hesitation may mean a lack of buy-in.

The point is leaders should explore it. Ask their teams, before I assume an absence of change-agility here, what can’t I see? What do you know that I don’t?

Learning Opportunities

Pausing to check in may seem like a slow-down upfront. But the volume of errors and rework from which it protects ultimately drives velocity.

Silence on the things people fear the most

Leaders often stay quiet about the hardest questions because they don’t have clean answers.

What will AI mean for this function? Are jobs at risk? What is the company really betting on? Which skills will matter more in two years? What’s still unknown?

Silence can feel careful. But silence doesn’t keep people calm. It leaves them alone with their own guesses.

When leaders say nothing, teams invent their own stories. Typically in the horror genre.

A team quietly wondering whether its work, role or function has a future is not giving its best attention to the work in front of it. Leaders don’t need certainty to speak. They need enough honesty to say what they know, what they don’t know, what they’re watching and when people can expect to hear more.

Leaders don't need certainty to address uncertainty. They need to be willing to be as clear and transparent as possible with what they do know. To commit to not making promises they may be unable to keep. And sometimes just to make space for people to share the experience of feeling unsteady together. To address it even if a solution isn’t available.

Resilience Is a Reasonable Ask. It Is Not a Free Pass.

None of this is an argument for asking less of people or lowering the bar.

The moment is hard. The demands are real. Organizations need people who can adapt, learn, recover and keep moving when conditions change.

But resilience doesn't emerge from expectation alone.

Leaders who treat resilience as an employee characteristic rather than an operating condition they help shape will keep running into the same wall: change initiatives that land with less traction than expected, teams that look increasingly brittle and a widening gap between what is being asked and what is actually possible.

The leaders who get genuine adaptability from their teams don’t just demand resilience. They make the work more resilient.

They clarify what matters, they remove obstacles, they explore hesitation and silence, and they communicate as transparently, vulnerably and clearly as possible.

They expect resilience, but they recognize their role is to do more than demand it.

If leaders want teams to keep carrying more, they have to be accountable for the conditions under which people are carrying it.

Editor's Note: How else does work need to be redesigned to allow for human capacity?

fa-solid fa-hand-paper Learn how you can join our contributor community.

About the Author
Rachel Cooke

Rachel Cooke is the founder of Lead Above Noise and the host of Macmillan’s Modern Mentor podcast. She helps organizations and leaders enhance how work gets done so that both business results and employee experiences can thrive. Connect with Rachel Cooke:

Main image: Peter Law | unsplash
Featured Research