A lot of "strategy problems" are actually nervous-system problems wearing a suit. Under impact, leaders either over-control, avoid, or thrash. The fix is not more motivation. It is not a better framework. It is triage: stabilise first, then classify correctly, then execute.

Most resilience failures are category errors. You cannot execute a clean plan while emotionally flooded, and you cannot accept what you have not correctly classified. Triage is the gateway to decision quality. Skip it and every downstream action inherits distortion from the moment of impact.

In Post 1, we defined resilience as the system that restores decision quality after impact. This post installs the protocol. Three steps, in order, no exceptions: stabilise, classify, execute. Get the sequence wrong and you will call panic "strategy."

This post builds the triage protocol. For the operating model it sits inside, see Post 1: Resilience as an Operating System. For what happens when your interpretation layer distorts the classification, see Post 3: Interpretation Under Volatility.

Stabilise: Reduce reactivity so decisions are clean. Rectify: Change what is changeable through disciplined action. Adjust: Carry constraints you cannot change while still executing on what matters. The sequence is non-negotiable: stabilise before you classify, classify before you execute.

The Cost of Misclassification

There are exactly two ways to misclassify a problem, and both are expensive.

The first is fighting reality. You pour resources into changing something that is structurally given: a market shift, a regulatory constraint, a person who has already left. This produces thrashing. Thrashing feels like effort. It looks like leadership. But it burns capital, exhausts the team, and delays the adaptation that would actually restore forward momentum. The leader who spends three weeks trying to "reverse" a board decision that is already final is not being persistent. They are haemorrhaging time.

The second is surrendering the solvable. You treat a fixable operational problem as an immovable fact. The underperforming hire stays because "that is just how it is." The broken process continues because changing it feels uncomfortable. This produces drift. Drift is quieter than thrashing, but over time it is more corrosive. The organisation slowly adapts to dysfunction rather than correcting it, and the leader's credibility decays with each unsolved problem that everyone can see.

Both errors share a common root: the leader classified while activated. Under stress, the brain does not distinguish well between "this is difficult" and "this is impossible." The result is that changeable situations feel permanent and permanent situations feel like personal failures. Misclassification is not a thinking problem. It is a sequencing problem. You classified before you stabilised.

You cannot trust the gauges when the engine is overheating. Cool the system first, then read the instruments.

The Incident Triage Metaphor

Think about how a hospital emergency department handles a mass-casualty event. The first thing triage does is not treatment. The first thing is assessment under discipline: stabilise the patient, classify the injury, then allocate the right intervention to the right case. Nobody redesigns the hospital during the fire. Nobody performs elective surgery while the emergency bay is full.

Leadership under volatility operates on the same logic. When the impact lands, you are in the emergency bay. Your job in that moment is not to solve the strategic problem. Your job is to prevent cascading failure. Stabilise first. Diagnose second. Treat third. In that order.

The leaders who consistently recover well are not calmer by temperament. They have internalised a sequence. They know that the first 20 minutes after impact are not for decisions. They are for downshifting the system so that the decisions that follow are worth making.

Step 1: Stabilise (10 to 20 Minutes)

Stabilisation is not a luxury. It is the precondition for every useful action that follows. You do not stabilise because you are weak. You stabilise because the physiology of acute stress is incompatible with accurate classification.

How do you know you need to stabilise? The signals are consistent and learnable:

If any of these are present, you are flooded. Classification under flooding produces garbage data and expensive decisions. The protocol is simple: stop, move, breathe, delay. Walk for 10 minutes. Put the phone down. Do not draft the response. Tell your assistant, your co-founder, or your own calendar that the next 20 minutes are a holding pattern.

This is not avoidance. Avoidance is indefinite. Stabilisation is time-boxed. You are not running from the problem. You are cooling the system so that your next move is clean.

Pattern in Practice

Bad Quarter Announcement: Revenue is down 18%. The board chair sends a terse email requesting an "urgent strategic review." The founder feels the floor drop. Within minutes, they are drafting a restructure memo, pulling up hiring data, and considering whether to fire the VP of Sales.

Stabilise protocol: Close the laptop. Walk for 15 minutes. Return. Write three facts on a card. No memo, no restructure, no calls until the 20-minute window closes. The problem will still be there. The reactivity will not.

Step 2: Classify (Rectify vs Adjust)

Once stabilised, you have one job: sort the situation into two columns. What can be changed through action, and what must be carried as a constraint while you continue executing.

Rectify means there are actionable levers. You can change the process, restructure the team, renegotiate the contract, have the conversation. The situation is difficult but moveable. Here, resilience is execution under discomfort. Not waiting for certainty. Not waiting for the discomfort to pass. Acting because the situation responds to action.

Adjust means the situation is structurally given. The market has shifted. The regulation has changed. The person has left. You cannot reverse these facts. Resilience here is adapting your operations to carry the constraint without denial and without despair. You do not pretend the constraint does not exist. You do not collapse because it does. You redesign around it.

The classification must be written, not thought. Thinking it through in your head allows the emotional charge to contaminate the sorting. Write two columns on a page. Label them "Rectify" and "Adjust." Put every element of the situation into one column or the other. If you cannot decide, it goes into "Adjust" temporarily, because the cost of premature action on an ambiguous element is higher than the cost of carrying it for a week while you gather information.

Pattern in Practice

Key Executive Resigns: Your Head of Product gives notice. Emotional reaction says: "We are unstable. Everyone will leave. The board will panic."

Classify: Rectify — onboarding process that creates single points of failure; absence of a documented product roadmap; team communication gaps. Adjust — the individual's decision to leave; the 4-week notice period; current pipeline commitments. Now you have a clean picture. The rectifiable items become your action list. The adjustable items become your constraints to design around.

Pattern in Practice

Investor Pressure After a Miss: You missed the quarterly target. The lead investor schedules a call. Emotional reaction says: "They are going to pull support. This is the beginning of the end."

Classify: Rectify — the narrative (build a clear, data-backed explanation); the forecast model (tighten assumptions); the operational gaps that caused the miss. Adjust — the investor's concern (legitimate; cannot be argued away); the missed number itself (historical fact); the market conditions that contributed. Set a communications boundary: "We will have a full debrief ready by Thursday." Then execute against the rectifiable items only.

Step 3: Execute (Two Actions Only)

Here is where most leaders lose the protocol. They classify well, then generate a list of 12 actions and call it "decisiveness." That is not decisiveness. That is panic wearing a to-do list.

After classification, you pick exactly two actions. One to reduce risk. One to create information.

Risk reduction is the action that prevents the situation from getting worse while you work the problem. It might be an interim appointment, a communications line to the team, a hold on spending, or a conversation that stops a misunderstanding from compounding. The purpose is containment.

Information gain is the action that creates data you do not currently have. It might be a conversation with a key stakeholder, a market test, a review of the numbers with a fresh set of eyes, or a structured debrief with the team. The purpose is to reduce ambiguity so your next round of decisions is better informed.

Two actions. Not ten. Not "a comprehensive response plan." Two. You execute them, review the result, and then decide what comes next. This is iterative, not exhaustive. The discipline is in the constraint, not the volume.

Don't redesign the system during the fire. Contain, diagnose, then rebuild — in that order.

The Volatility Circuit Breaker

In electrical systems, a circuit breaker exists to prevent cascading failure. When the load exceeds safe operating limits, the breaker trips. It does not solve the underlying problem. It prevents the problem from destroying the system while you diagnose and fix it.

The stabilise-classify-execute protocol is your circuit breaker. It trips early, before the leader's reactivity propagates through the organisation. Because that is the real danger: not the original impact, but the leader's unprocessed reaction to the impact radiating outward through every email, meeting, and decision made in the 48 hours after the hit.

A founder who thrashes after bad news creates three problems: the original problem, the organisational instability caused by the thrashing, and the credibility damage from the team watching the founder lose composure. The circuit breaker prevents the second and third problems entirely. The first problem was going to need solving regardless. Now it gets solved by a stabilised leader making clean decisions, rather than by a flooded leader generating more fires.

Where the Protocol Gets Misused

Any tool can be turned into a weapon against yourself. The triage protocol has three specific failure modes, and you need to know them in advance.

Calm-First Becomes Permanent Avoidance

Stabilisation is time-boxed: 10 to 20 minutes, occasionally an hour for severe impacts. If you are still "stabilising" three days later, you have converted the protocol into an avoidance strategy. The tell is that you feel calmer but have taken no action. Calm without action is not stability. It is drift with a better narrative.

Over-Execution as Anaesthetic

Some leaders skip stabilisation entirely and go straight to a blizzard of activity. Twelve tasks, four meetings, three new initiatives. This feels like leadership because it involves effort. But activity is not the same as triage. If you have not classified first, half those actions are aimed at the wrong target. The busyness is not strategic. It is the nervous system using movement to discharge anxiety. The giveaway: none of the actions have a clear success criterion, and none of them are reviewed.

"Adjust" Becomes Learned Helplessness

The adjust column is for genuinely unchangeable constraints. It is not a bin for everything that feels hard. If your adjust column is consistently longer than your rectify column, audit it. Are those items truly structural, or are they uncomfortable actions you have mislabelled as impossible? "I can't fire him" might actually be "I don't want to have that conversation." That is a rectifiable item wearing an adjust costume.

Executive Protocol

The 3-Door Executive Triage Card

Purpose: A one-page decision card for use within 30 minutes of any significant impact. Keep it on your phone or printed in your notebook.

  1. Door 1 — Stabilise. Am I flooded? (Impulsive comms, catastrophic projection, inability to focus, physical activation.) If yes: stop. Walk 10 minutes. No emails, no calls, no decisions. Return when I can hold one thought for 60 seconds without circling. What good looks like: calm enough to write, not calm enough to be comfortable. Comfort is not the goal. Clarity is.
  2. Door 2 — Classify. Write two columns: Rectify (actionable levers) and Adjust (structural constraints). Every element of the situation goes into one column. If unsure, it goes into Adjust temporarily. What good looks like: a clean, written list where each item sits in one column only. No narratives. No justifications. Just the sort.
  3. Door 3 — Execute. From the Rectify column, pick exactly two actions: one risk-reduction action and one information-gain action. Schedule both within 48 hours. Set a review point. What good looks like: two actions with owners, deadlines, and a clear criterion for "done." Everything else waits until the review.
Failure Modes
Executive Protocol

The Two-Action Rule

Purpose: Prevent the common post-impact failure of confusing volume with quality. After every classification, constrain yourself to two moves.

  1. Action 1 — Risk Reduction. What is the single action that prevents this situation from getting worse in the next 48 hours? This is containment. Examples: interim coverage for a departing role, a holding statement to stakeholders, a spending freeze on a troubled initiative, a direct conversation that stops a misunderstanding from compounding.
  2. Action 2 — Information Gain. What is the single action that gives us data we do not currently have? This is diagnosis. Examples: a structured debrief with the team, a call with the departing employee to understand the real reasons, a market data pull, a customer conversation, a financial review with fresh eyes.
  3. Review Point. Set a date within 5 business days to review the results of both actions. At the review, and only at the review, decide the next two actions. This is iterative triage, not a one-time plan.
Failure Modes

The Compounding Return of Triage Discipline

Leaders who install this protocol report a consistent pattern. The first few times, it feels slow. Twenty minutes of stabilisation feels like an eternity when the building is on fire. But by the third or fourth use, the sequence becomes automatic. Stabilise, classify, execute. The recovery half-life shortens. What used to be a 72-hour thrash cycle becomes a 4-hour triage sequence. Over a year, that difference compounds into hundreds of additional hours of clean decision-making.

The protocol also changes how the team experiences volatility. When the leader stabilises before responding, the team receives a clear, classified assessment instead of a reactive broadcast. The contagion effect reverses: instead of the leader's anxiety propagating through the organisation, the leader's discipline propagates. People start using the same language. "Is this a rectify or an adjust?" becomes a shared diagnostic. The organisation builds a collective immune system instead of relying on one person's composure.

Key Takeaways

Resilience Series

← Previous: Resilience as an Operating System Series Index Next: Interpretation Under Volatility →

If volatility repeatedly hijacks your execution, this becomes an operating cadence. Assessment consultations are available.

Request Assessment

This content is educational and does not constitute medical, financial, or relationship advice.