The Resilience Evidence Bank
Turn recovered setbacks into evidence for the next disruption
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 89%
When the team's truck broke down in the Sahara, Cook says the problem felt minor because they had already worked through worse situations and had become a coordinated unit. Stan's account, relayed by Bartlett, was that their resilience accumulated as repeated setbacks supplied evidence that the team could find a way through. The framework formalises that mechanism: after a disruption, record the response, lessons, and capability demonstrated; when another setback arrives, retrieve the closest evidence before acting. A failed attempt can still contribute lessons. This is a mental model extracted from their discussion, not proof that adversity automatically strengthens people or that prior survival makes a new danger safe.
Origin
Extracted from The Diary of a CEO. Bartlett and Cook discuss how recovering from repeated difficulties gave the Africa team evidence and coordination that changed its response to a later truck breakdown in the Sahara.
Core principles
- 01Recovered setbacks create evidence that future problems may be solvable
- 02Lessons still have value when an attempted solution fails
- 03Shared recovery can improve a team's confidence and coordination
- 04Past survival supports action but does not make a new risk harmless
How to run it
- 1
Describe the setback accurately
Record what happened, what was at stake, and what remained unknown. Avoid turning a dangerous event into a heroic slogan.
Pro tip Write the account while details are still fresh.
- 2
Capture the response
List the decisions, actions, and handoffs the team used. Include attempts that failed as well as the final solution.
Pro tip Separate luck from repeatable capability.
- 3
Extract the evidence
Name what the recovery actually demonstrated, such as coordination, improvisation, or persistence. Keep the claim narrower than “we can handle anything.”
Pro tip Use one sentence linking the capability to the observed result.
Watch out Survival alone does not prove that the choices were safe or repeatable.
- 4
Retrieve a relevant precedent
When a new setback occurs, recall the closest previous case and the capability it established. Use it to reduce paralysis and organise the first response.
Pro tip Match on problem structure, not surface drama.
- 5
Reassess the new risk
Check what is different before reusing an old response. Preserve confidence while updating for new consequences and constraints.
Pro tip Ask which assumption from the earlier case no longer holds.
Watch out Do not let accumulated confidence become complacency.
In the wild
After months of more severe disruptions, the support truck broke down far from the nearest road. Cook says he regarded it as a minor problem they would solve, while Bartlett reports Stan's view that the team's resilience had accumulated through earlier setbacks.
→ Prior recovery evidence reduced alarm and supported a coordinated response to another operational problem.
Common mistakes
Romanticising adversity
The discussion supports learning from setbacks, not seeking danger or claiming that hardship always produces growth.
Banking vague confidence
“We are resilient” is less useful than naming the exact capability demonstrated in a specific recovery.
Reusing an old answer blindly
A new hazard may differ materially even when earlier setbacks were resolved.
Is it for you?
Best for
Teams repeatedly handling uncertain, recoverable operational problems together.
Not ideal for
Novel or high-consequence hazards where confidence from past survival could encourage unsafe complacency.
From the transcript
“We'd been through much worse.”
“We all just got on with our jobs.”
From the episode
Russ Cook (Hardest Geezer): I Haven't Told The Whole Truth About Africa!, They Took Me Into The Jungle To Kill Me!