Your team can survive one disruption after another and still lose the game.
Employees continue showing up. Managers solve urgent problems. Project teams revise their plans whenever new demands arrive. Leaders praise everyone for staying strong, flexible, and resilient.
But the business objective slowly disappears beneath the urgent work.
Temporary workarounds become permanent. High performers carry more because leaders know they can. Projects keep expanding without producing evidence that the solution works. Everyone becomes skilled at absorbing pressure, but the work that matters most does not move.
For CEOs, this appears as strategic drift. The company remains busy while critical priorities slow down. People protect plans that no longer fit current conditions because too much time, money, and reputation have already been invested in them.
For HR and L&D, the problem often arrives as a request for resilient leadership training. The expected program may cover stress management, emotional intelligence, positive thinking, crisis communication, and coping skills. These capabilities can help leaders manage themselves under pressure, and they remain important parts of resilient leadership.
But resilient leaders must do more than stay calm and help people endure.
They must keep the business win visible, recognize when the current play is no longer working, and help the team find another way forward without breaking the people doing the work.
The Team That Kept Adapting
I once worked with a team that had spent almost two years building an application.
The people were not lazy. They had worked through changing requirements, shifting expectations, and new information from stakeholders. Each time another concern appeared, they responded by adjusting the product.
They added features. Reworked earlier sections. Extended timelines. Revised the plan.
From one point of view, they appeared highly resilient. They refused to give up. They absorbed every change and kept working even when the project became more complicated than anyone had expected.
But after almost two years, no beta version had reached actual users.
Every new request had become another requirement. Every new risk had become another reason to delay release. Because the company had already invested so much, leaders felt they had to protect the complete vision.
The larger the project became, the more dangerous it felt to release an incomplete version.
The team had survived every disruption. It had not moved closer to proof.
That is where the conventional view of resilience becomes dangerous. When resilience means carrying everything, the most reliable people receive more weight. When it means protecting the original plan, leaders keep investing long after the evidence should have changed their approach.
Resilience is not the ability to carry the same plan forever. It is the ability to protect the win while changing how you pursue it.
Keep the Win. Change the Play.
When conditions change, many organizations do the opposite.
They change the objective every few weeks while protecting the same activities. Teams continue holding the same meetings, preparing the same reports, following the same approval process, and building the same solution even when those practices no longer help.
Resilient leadership keeps the important result stable enough to guide people while allowing the play to change.
The business may still need stronger customer retention, reliable delivery, safer operations, profitable growth, or a useful product in the hands of customers. What changes is the route.
The full product may become a beta test. The company-wide transformation may begin with two departments. The twelve-month program may become a thirty-day experiment. The expensive technology solution may begin as a manual test designed to determine whether the underlying assumption is true.
This is not lowering the standard. It is finding a faster route to evidence.
Stubborn leaders protect the plan because changing it feels like admitting failure. Resilient leaders protect the win because continuing with the wrong plan would create a more expensive failure.
A Play to Win leader asks, “What are we really trying to achieve, and which play gives us the strongest responsible move under these conditions?”
Bring the Win One Step Away
Large objectives often become less useful during disruption because they feel too far from what the team can do today.
“Restore profitability.”
“Complete the transformation.”
“Regain market share.”
“Finish the application.”
These goals may provide direction, but they do not tell overwhelmed people what progress should look like this week.
Impact-first leaders bring the business objective one step closer to the work.
For the application team, “finish the platform” was still too large. A result one step away might have been:
Twenty intended users complete one essential workflow using the beta version and show us where the product succeeds or breaks.
That result creates a clearer field. The team knows who must use the product, what they must attempt, what part of the application matters now, and what evidence will guide the next decision.
The objective remains visible, but progress becomes observable.
This is essential to resilient leadership. Leaders cannot simply tell people to keep going. They must show them what movement is still possible under changed conditions.
A useful one-step-away result has a unit, a clock, an owner, and proof. Instead of waiting six more months to discover whether the complete product works, the team can learn something important from real users within weeks.
That learning may confirm the direction. It may expose a flawed assumption. It may reveal that one feature matters far more than the others.
Whatever the result, the organization is moving through evidence rather than endurance.
Stop Carrying What No Longer Serves the Win
Resilience is often described as the capacity to handle more.
The resilient manager accepts another project. The resilient employee compensates for a vacant position. The resilient team creates another workaround when a process fails. Because these people continue delivering, leaders keep placing more weight on them.
Eventually, resilience becomes the reason the system is never repaired.
Play to Win resilience requires subtraction.
Leaders must ask which commitment no longer deserves capacity, which activity made sense under earlier conditions, and which assumption has already been disproved. They must decide what will stop, wait, shrink, or move to someone else.
During disruption, organizations tend to add. A new problem creates another report. A missed deadline creates another meeting. An error creates another approval. A customer complaint creates another training session.
Nothing is removed.
The team is expected to adapt while carrying every earlier commitment plus every new response.
That is not resilience. It is accumulation.
Resilient leaders do not merely ask people to become stronger. They remove weight that no longer contributes to the win.
For the application team, this might mean releasing the belief that every requested feature must appear in the first version. It might mean pausing enhancements that do not affect the essential user workflow. It might mean admitting that two years of effort cannot justify another year without customer evidence.
Past investment deserves respect. It does not deserve control over every future decision.
Read the Field Before Calling the Next Play
Resilient leaders do not respond to every disruption by moving faster.
They first read the field.
What changed? Which assumption is no longer true? What constraint has appeared? Which capability still works? Where is the work getting stuck? What information would help us choose the next move?
These questions prevent resilience from becoming blind persistence.
Sometimes the objective remains correct, but the timeline must change. Sometimes the original solution is wrong. Sometimes employees have the necessary capability, but unclear authority prevents them from using it. Sometimes the team could move quickly if leaders removed one approval or stopped one competing priority.
Reading the field also helps leaders distinguish between a temporary obstacle and a change that requires a new play.
Not every setback justifies abandoning the strategy. A responsible plan deserves enough commitment to survive predictable difficulty. But commitment becomes stubbornness when leaders continue protecting the activity after the conditions that supported it have disappeared.
Resilient leadership requires judgement: knowing what must remain steady and what must be allowed to change.
Resilience Must Be Built Before the Crisis
Organizations often discover their lack of resilience only after something breaks.
A supplier fails. A key employee resigns. A customer changes direction. A new competitor enters. A technology platform stops working. Leaders then expect people to respond with creativity, confidence, and speed.
But resilient organizations cannot depend entirely on heroic behaviour during panic.
Resilience is built before the crisis through clear priorities, useful information, trusted relationships, cross-trained people, decision rights, review rhythms, and permission to test smaller responses.
People need to know which decisions they can make without waiting. They need ways to raise bad news before it becomes a crisis. Teams must understand which result matters most when several commitments compete.
Systems matter because motivation fades. A manager may remain calm for several weeks, but calmness alone cannot compensate for unclear ownership, impossible workloads, or decisions that repeatedly rise to the wrong level.
A resilient organization does not prevent every shock. It reduces the number of ordinary decisions that become impossible when the shock arrives.
Rebuild Movement Through a Smaller Play
When people feel overwhelmed, leaders often respond with a large recovery plan.
They create several initiatives, new targets, and a long list of corrective actions. The plan is intended to restore confidence, but it may make the team feel even further behind.
Resilient leaders rebuild movement through a smaller play.
What is one decision the team can make now? What is one customer problem it can resolve? What is one assumption it can test? What is one burden it can remove? What proof could appear within the next week or month?
The first play should be small enough to run and meaningful enough to matter.
For the application team, the smaller play was not another planning session. It was getting a limited version into the hands of users. The purpose was not to pretend the product was finished. It was to learn what finishing should mean.
Small proof restores agency. It shows people that they are not helplessly waiting for better conditions. They can make a responsible move, observe what happens, and improve the next attempt.
Resilience grows through this rhythm: act, learn, adjust, and act again.
What CEOs Must Stop Praising
CEOs should be careful when praising resilience.
Sometimes the organization is celebrating people for compensating for poor systems. Employees work weekends because priorities were never resolved. Managers repeatedly rescue the same process because nobody owns the root cause. High performers keep projects alive while low-value commitments remain untouched.
The effort may deserve appreciation. The condition should not become permanent.
Before asking people to become more resilient, CEOs should ask what the organization keeps requiring them to endure.
Which priorities remain active even though circumstances have changed? Which teams carry more because they succeeded before? Which temporary workarounds have become part of normal operations? Where do employees need clearer authority rather than another message about perseverance?
The CEO’s responsibility is to keep the business win clear, make the difficult trade-offs, and give leaders permission to change the play.
What HR and L&D Must Build
HR and L&D should not design resilient leadership as a set of personal coping techniques detached from the work.
Begin with a real disruption or recurring pressure. What business objective was affected? What did leaders do when conditions changed? Which response moved the work, and which one merely protected the familiar plan? What organizational conditions made adaptation difficult?
Then build practice around that moment.
Give leaders a situation where an important assumption changes, a resource disappears, a deadline becomes impossible, or a customer rejects the original solution. Ask them to clarify the win, identify what must change, choose what should stop, recommend a smaller play, and define what evidence they will examine.
This is how practical leadership training develops resilience for real work. Leaders do not merely discuss the traits of resilient people. They practise changing the play while keeping the business objective visible.
Change the Play Without Losing the Win
The application team did not need more encouragement to keep going. Its members had already demonstrated endurance for almost two years.
They needed permission to stop carrying the complete plan.
Once the leaders clarified the real win, a smaller release became possible. The team could place something useful in front of users, learn from what happened, and let evidence guide the next move.
Their resilience no longer appeared as endless tolerance for change. It appeared as the ability to adapt without losing direction.
That is the Play to Win standard for resilient leadership.
Resilient leaders do not merely return people to where they were before the disruption. They help people see what still matters, release what no longer serves it, and run the next play that can move the business forward.