Two organisations respond to the same disruption inside forty-eight hours. Seen from the outside, they are equally fast. They are in radically different situations, and that difference will decide what happens to each of them at the next disruption.
The first mobilised a considerable amount of energy, pulled its leaders into an emergency room, improvised a decision chain and reinvented under pressure processes that should have existed beforehand. The second activated mechanisms prepared while conditions were calm.
Structural responsiveness is the fifth of the eight pillars of the invulnerable company. The speed of reaction deceives every time, so it is the wrong measure. The right one is the number of decisions that did not have to be taken under pressure because they had already been taken.
| The illusion | The distinction | The preparation |
|---|---|---|
| Speed says nothing about solidityTwo organisations can respond equally fast to the same disruption from opposite positions. The speed observed from outside never tells you the quality of the decisions taken, nor the real cost paid to take them. | Acting from strength or from constraintImprovised responsiveness spends a considerable amount of energy rebuilding under pressure what should have existed beforehand. Structural responsiveness activates mechanisms prepared while conditions were calm, and pays a far lower cost for a better result. | Decide cold what will otherwise be decided hotThree things have to exist before the disruption: written scenarios on the plausible ruptures, pre-approved resources and delegations, and trigger thresholds defined when nobody is under pressure. |
Two identical speeds, two opposite positions
Agility is celebrated everywhere in contemporary management talk. Moving fast, deciding fast and pivoting fast pass for virtues in themselves. This pillar introduces a distinction that the celebration erases completely, and the distinction is the whole point.
What improvised responsiveness actually costs
An organisation that reacts fast because it is forced to pays three times. It pays in decision quality, since trade-offs taken under pressure are systematically worse than those prepared cold. It pays in organisational energy, which is a finite resource. And it pays in lost options, the ones that existed only during the window before anyone had decided.
That cost is invisible in crisis debriefs, which celebrate the mobilisation rather than question whether it was avoidable. An organisation usually comes out of a crisis handled under pressure feeling it responded well, which is precisely what stops it building the apparatus that would have spared it the reaction.
Operational heroism is admirable and it is a symptom. An organisation that needs heroes has a design problem, and the heroes always end up leaving or burning out.
I see this pattern most clearly in the debrief. The room replays the heroic forty-eight hours, names the people who barely slept, and quietly agrees never to speak of how avoidable the whole episode was. The praise is genuine and it is also the mechanism that guarantees the next crisis will be run exactly the same way, because celebrating the response has replaced examining the design that made the response necessary. Whether anyone in that debrief says the avoidable part out loud depends on a different pillar, because a culture of internal dissent is what makes an uncomfortable observation survivable for the person who makes it.
What structural responsiveness installs
An organisation with this pillar does not have to invent its decision chain at the moment it needs it. It knows who decides what, with what budget authority, on what priority and within what deadline, because those questions were settled while nobody was under pressure.
The difference is measured in a counter-intuitive way. Speed of reaction is the wrong gauge. The right one is the number of decisions that did not need to be taken during the crisis because they had already been taken.
An organisation that comes through a major disruption with no exceptional crisis meeting is not being passive. It built in advance what the others improvise, and its apparent calm is the visible product of invisible work done months earlier.
The three things that have to exist before the crisis
This pillar rests on three concrete arrangements. None requires significant investment, all require executive time, which explains why they are so rarely built in organisations whose diary is already saturated. The scarce resource here is attention, not money.
Written scenarios rather than generic plans
A useful scenario describes a precise rupture, its cascade effects on your operations, and the decisions it would force. It does not try to predict the future, it tries to make familiar a situation that is not yet familiar. Familiarity is what buys speed when the rupture actually arrives.
Two or three scenarios are enough, provided they cover ruptures whose impact would be structural rather than the most probable ones. The loss of your critical supplier, the prolonged unavailability of your information system and the abrupt withdrawal of a market that weighs heavily are three families that cover most real situations.
What separates a scenario from a generic continuity plan fits in one sentence. A scenario names the people, the amounts and the deadlines. A generic plan describes principles.
The test is whether the document would let a newcomer act. Hand your continuity plan to a manager who joined last month and ask what they would do in the first hour of the rupture it covers. If the honest answer is that they would call a meeting to find out, you have a plan. If they can name the first three moves and who authorises them, you have a scenario.
Pre-allocated resources and pre-approved delegations
The second arrangement is the most neglected. It means deciding in advance which resources can be mobilised, by whom, up to what amount and without what additional sign-off. Most organisations have never had the conversation, because in normal times it feels like handing out blank cheques against events that may never come.
In most organisations the authorisation chain stays identical in a crisis and in normal running. The result is mechanical: the first hours are spent obtaining approvals rather than acting, and those hours are exactly the ones where action costs the least.
A crisis delegation pre-approved by the board, capped in amount and bounded in time, costs one meeting to install. Its absence costs several days at the most critical moment, and those days are never recovered.
Trigger thresholds defined cold
The third arrangement answers the question that most often paralyses organisations at the start of a crisis: from what point do we consider the situation justifies switching into degraded mode?
With no threshold defined in advance, that question gets debated while the situation worsens, and it gets debated badly, because everyone has an interest in the threshold matching their own reading. The debate about triggering consumes the time that triggering was supposed to save.
A useful threshold is quantified, observable and not open to argument in the moment. Three days of interruption to a critical supply, a fall in a given indicator beyond a given level, or the unavailability of a given system for a given duration automatically triggers the associated scenario, with nobody having to decide.
Field note
Maersk, the feat everyone tells the wrong way round
On 27 June 2017 the NotPetya malware destroyed the IT infrastructure of the world’s largest shipping line. Four thousand servers, forty-five thousand workstations and two thousand five hundred applications were reinstalled in ten days, where the group’s chairman publicly estimated such a rebuild normally takes six months. The cost was put at 250 to 300 million dollars, for a volume drop held to 20 per cent.
The story has become a textbook case of organisational resilience. Two details, reported by the group itself, make it far less reassuring.
The first is that rebuilding the central directory was only possible thanks to a domain controller located in Ghana, spared because it happened to be powered off at the moment of the attack. The second is the chairman’s own words at the Davos forum, describing a company that was simply average on cybersecurity, like many others.
This case does not demonstrate structural responsiveness, it demonstrates its absence. Maersk produced improvised responsiveness of exceptional quality, carried by a considerable human effort, and its survival hung on a power cut in West Africa. An organisation that owes that kind of debt to luck does not have an apparatus, it had a reprieve. The group’s credit is to have drawn the conclusion and rebuilt afterwards.
Why business continuity plans are useless
Most of the organisations I meet have a business continuity plan. Almost none has structural responsiveness, and that is not a contradiction. The plan and the capability are two different things, and one regularly stands in for the other.
The document against the exercise
A continuity plan written to satisfy a regulatory requirement, signed off once then filed away, produces no effect on the day. Nobody knows it exists, nobody knows its contents, and the people who wrote it have often moved on.
A plan that is never exercised is a document rather than an apparatus. It even produces a negative effect, creating a sense of preparedness that excuses the organisation from building the real preparation.
The difference between the two rests on a single practice: the periodic exercise in real conditions, with the people who would actually decide, and with no warning of the scenario chosen.
What a real exercise reveals
An exercise run seriously almost always reveals the same failures, and they never appear in the plans. The designated people cannot be reached, and the data needed for the decision sits in an inaccessible system. The budget delegations do not exist, and the trigger threshold becomes a forty-minute debate.
Each of these failures is corrected in a few days when it is identified cold. Each costs several days when it is discovered during the real event, at a moment when those days have a value beyond comparison.
One exercise a year is enough, provided it is run with no warning, involves the real decision-makers and produces a written list of corrections with owners and deadlines. Australian directors have a further reason to run it, since the duty of due diligence under work health and safety law extends to being satisfied the organisation has resources and processes to respond to hazards, and a plan nobody has tested is hard to defend as due diligence.
Check first that you have something to respond with
Your scenarios are written but you doubt you could activate them? Make sure the strategic redundancy pillar actually exists, because a scenario with no mobilisable reserve capacity describes an intention rather than an option.
Building your trigger thresholds
Acting on this pillar always starts with the same exercise, and it fits in a half-day of executive time. It turns three plausible ruptures into three quantified thresholds attached to three pre-approved decisions.
The table to complete before you leave the room
Each row has to be complete to be useful. A row whose decision-maker column or amount column stays empty will produce nothing on the day, since that is exactly what will be argued about while the clock runs.
| The rupture | The observable threshold | Who decides without sign-off | Up to what amount |
|---|---|---|---|
| Loss of a critical supplier | Confirmed interruption beyond X days | The operations director, alone | A defined, time-bounded cap |
| Information system unavailable | A given service down beyond X hours | The chief information officer, alone | A defined, time-bounded cap |
| Collapse of a major market | A given indicator falls beyond X points over X weeks | The small executive group, without the board | A defined, time-bounded cap |
The objection that always comes back
The most common objection is about rigidity. Setting thresholds would mean forbidding judgement, when every situation is particular and deserves its own appraisal.
That objection turns around. A threshold does not forbid judgement, it moves when the judgement happens. It forces you to exercise that judgement cold, with complete information and no pressure, rather than hot with partial information and a running clock.
A threshold can always be overridden by an explicit decision of the executive group. What changes is that the starting point becomes action rather than debate, and that inversion alone is enough to win the hours that matter.
This pillar also depends on the two beneath it in the architecture. A threshold only triggers a real response where strategic redundancy has kept some reserve capacity to mobilise, and a pre-approved delegation only survives contact with a crisis where long term governance has protected it from the quarterly pressure that erodes anything with no immediate return.
How I can help you build this pillar
This pillar has a useful feature: it produces fast results. Unlike identity or governance, whose effects are measured in years, the thresholds and delegations install in a few weeks and are verified immediately. It is the fastest of the eight to show a return.
A workshop to build the scenarios and thresholds
The workshop produces, in one day, two or three scenarios written on your real ruptures, with their quantified thresholds, their delegations and their caps. It is the most operational deliverable of the whole path, and the only one that can be applied from the following week.
The design of an unannounced exercise
The exercise tests your existing arrangements in real conditions, with the real decision-makers and no warning of the scenario. It produces a written list of failures and corrections. It is often the most useful and most uncomfortable session of the whole path.
A keynote on preparation rather than reaction
The keynote draws on documented cases of crises that were survived, and on what they reveal when you read them as something other than tales of heroism. It is built for organisations that have just handled a crisis well, which are the ones most exposed to taking nothing from it.
The content sits on the page for the keynote on the invulnerable company. If you want to talk through what this would look like inside your organisation, book a conversation with me directly.
Conclusion
Structural responsiveness is the pillar easiest to confuse with its opposite. An organisation that handles a crisis brilliantly looks a great deal like an organisation that will not have to handle one next time, and the two situations have nothing in common.
Maersk rebuilt its infrastructure in ten days instead of six months, and its survival depended on a server spared by a power cut. The carmakers that came through the semiconductor shortage without stopping their lines had not reacted better than the others, they had planned the scenario before it arrived.
The quality of a response is not measured by its speed. It is measured by the number of decisions that did not need to be taken.
So the question to ask after your next well-handled crisis is the least natural of all. How much of what worked rested on structural responsiveness, and how much rested on the commitment of a few people and a bit of luck?
Frequently asked questions about structural responsiveness
What is the difference between agility and structural responsiveness?
Agility describes a speed of execution, structural responsiveness describes a preparation. Two organisations can respond equally fast, one improvising its decision chain under pressure, the other activating mechanisms defined cold. Only the second will hold at the next disruption.
Is a business continuity plan enough?
Not if it is never exercised. A plan written to satisfy a regulatory requirement then filed away creates a sense of preparedness that excuses building the real preparation. Only the periodic exercise, unannounced and with the real decision-makers, turns a document into an apparatus.
How do you define a useful trigger threshold?
It has to be quantified, observable and not open to argument in the moment. Three days of interruption to a critical supply, or a given system unavailable for a given duration, triggers the associated scenario with nobody having to decide while the situation worsens.
Do thresholds set in advance make decisions rigid?
They move when the judgement happens rather than removing it. The judgement is exercised cold, with complete information and no pressure. A threshold can always be overridden by an explicit executive decision, but the starting point becomes action rather than debate.
How many scenarios should you prepare?
Two or three are enough, provided they cover ruptures whose impact would be structural rather than the most probable. Loss of a critical supplier, prolonged unavailability of the information system and the abrupt withdrawal of a major market cover most real situations.
