Most leadership development still measures the bounce-back. The better question is why the drop had to happen at all.
Most of what leadership development calls resilience training is actually recovery training. It teaches a leader how to metabolize a hit after it lands: how to steady the room, how to talk to the board, how to keep functioning three days after the thing nobody saw coming. All of that has real value. None of it asks the harder question, which is why nobody saw it coming in the first place.
Resilience, in the way most organizations use the word, is backward-looking. It gets measured after the fact, the same way a KPI measures what already happened. How fast did the team recover. How well did the leader hold the room. How much revenue came back within a quarter. These are legitimate questions. They are also the wrong ones to ask first.
Dr. Gavriel Schneider, in his book Presilience: How to Navigate Risk, Embrace Opportunity, and Build Resilience, names this gap directly. Resilience tells you how well you bounced back. Presilience asks whether you were positioned, before the disruption ever hit, to turn it into an advantage instead of just a wound to survive. That is not a semantic difference. It is the difference between a leadership team that reacts well and one that was rarely fully surprised to begin with.
The comparison that clarified this for me is one most operators already carry from a different context. A KPI tells you what happened last quarter. An OKR tells you where you are going and what has to be true to get there. Resilience is a KPI. Presilience is an OKR. One measures the past with precision. The other architects the future on purpose.
Here is why most leaders default to the KPI version anyway. Recovery is visible. A leader who holds a team together during a crisis gets seen, credited, sometimes celebrated. Readiness is invisible by design. Nobody throws a leader a parade for the crisis that never happened because someone quietly built the early-warning system eighteen months earlier. The incentive structure of most organizations rewards the comeback and is blind to the prevention. So leaders keep building comeback skill, because that is the version of strength anyone will ever actually witness.
There is a practical shape to what building readiness instead of recovery looks like, and it holds up whether the disruption is a market shift, a key departure, or an SLT dynamic finally coming to a head.
Anticipate. Before something breaks, ask what is most likely to. Not what already has, that is the recovery question. A regular, unglamorous exercise, walking the leadership team through what could plausibly go wrong in the next two quarters, does more for organizational readiness than most crisis retrospectives ever will. Pre-mortems earn their keep here.
Rehearse. Response quality under real pressure is mostly a function of whether the pattern has been practiced before the stakes were real. A team that has walked through a scenario, even loosely, moves differently when the actual version shows up. This is not about predicting the exact crisis. It is about lowering the cost of the first sixty seconds of any crisis.
Assign. Decide, in calm weather, who owns which call when the room is not calm. Most organizational paralysis in a real disruption is not a competence problem. It is a decision-rights vacuum, three capable people looking at each other, unsure whose call this actually is, while the clock keeps running.
I will admit something here. For most of my career, I built exceptional recovery skill, because I had to. I got very good at the comeback. I was considerably less intentional about readiness, about doing the quieter work of anticipating what was coming before it arrived on my desk demanding a response. Recovery skill is what you build when you keep getting surprised. Readiness is what you build once you decide being surprised this often is itself the problem worth solving.
Recovery proves you can survive what you did not see coming. Presilience is the discipline of seeing more of it coming in the first place.
Omar
Omar Rivas / Organization Leadership Development & Advisory / connect@omarrivas.com