Adaptability helps us change direction; resilience helps us recover, sustain effort and learn after pressure, setbacks or ambiguity. They reinforce each other, but neither asks us to endure an unhealthy workload indefinitely.

During NexoLab's migration, an integration failed shortly before a demonstration. A resilient response was not to hide the problem or work endlessly. The team stabilised the service, informed the client, assigned recovery tasks and captured what had failed in the handover.

1. Stabilise: protect people, service and essential information.
2. Make sense: separate facts, assumptions and emotions.
3. Learn and adapt: repair the issue, update the plan and prevent repetition.

Recovery improves with realistic workload limits, prioritisation, psychological safety, supportive relationships and routines that restore attention. At team level, clear incident roles and blameless reviews reduce the cost of future disruptions.

Mistake: confusing resilience with tolerating any condition. Tip: raise unsustainable risks early and negotiate scope, support or timing.

Mistake: moving on without reviewing the incident. Tip: reserve a short review for lessons, owners and preventive actions.

Think of a recent setback. List what had to be stabilised, which support you used or needed, and one practice that would make the next response easier.

For a missed deadline: inform stakeholders with facts, reduce work in progress, agree on a revised date, and add an earlier dependency check to the next plan.

Resilience is a repeatable recovery capability: stabilise, understand, learn and protect the conditions that make sustained adaptation possible.