It is tempting to think of resilience as something a team either has or does not, a kind of organisational personality trait. In practice, it is closer to a set of specific habits, built deliberately, well before the disruption that tests them.
The first habit is knowing who covers what when someone is out. Not on paper in a file nobody opens, but genuinely rehearsed: has the backup person actually done the task recently, or would they be learning it live during a crisis?
The second is a team that can disagree productively under pressure. Teams that only practice consensus in calm periods tend to either freeze or fracture when a fast, high-stakes call is needed and people do not fully agree. Practicing structured disagreement in low-stakes moments builds the muscle for when it matters.
The third is psychological, not procedural: does the team have a track record of surfacing bad news early, or does it tend to sit on problems hoping they resolve? That pattern is set long before any actual shock, in how small mistakes get handled month to month.
None of this shows up on an org chart. It shows up in how a team performs on the one week a year when everything goes wrong at once, and by then it is too late to start building it.