Disruption Playbook¶
Response protocol / playbook — instantiates Wild-Card Contingency Mapping
Pre-scripts the response to a specific wild-card class — who does what, the trigger to activate and the signal to stand down, and the ethical limits on it all — so the response is executed under authority, not improvised in the moment.
The Disruption Playbook is a pre-written, role-assigned response procedure for one wild-card class. Its distinguishing contribution is choreography and authority: the sequence of moves, who is empowered to run them, the trigger that activates the response and the criterion that retires it, and the ethical limits on pre-authorized action. It does not inventory the response options (the Contingency Option Register does) or hold the capacity behind them (the Strategic Reserve Plan does); it turns a shelf of available options into an executable, bounded plan that a team can run under pressure.
Example¶
A city government keeps a playbook for the class "core municipal systems encrypted by ransomware." When its trigger fires — say, a defined number of critical services confirmed down — it activates a set structure: an incident commander with pre-granted decision authority, a communications lead, legal, and IT, each with scripted first moves (isolate affected networks, switch permit and billing operations to a manual continuity-of-operations mode, open the pre-drafted resident-communications channel).
It pre-answers the questions that otherwise stall a response: who may declare the incident, who may authorize emergency spend. And it encodes ethical guardrails — no ransom payment without council authorization, no blanket collection of resident data under emergency cover — alongside retirement criteria so the city does not sit in emergency posture once systems are restored. The structure mirrors the Incident Command System. Its worth is that on the worst morning, no one is inventing the org chart or debating who is allowed to act.
How it works¶
- Sequence the moves. Order the response actions — drawn from the option register — into a runnable procedure, not a menu.
- Assign authority and roles. Name who declares, who decides, and who executes, pre-delegating enough decision right to move fast.
- Set activation and retirement. Define the trigger that turns the playbook on and the criteria that stand it down, so it is neither slow to start nor stuck on.
- Bound it ethically. State the limits on pre-authorized action so speed does not license over-reach.
What distinguishes it is choreography, authority, triggers, and ethical limits — the how, who, and when, not the what-exists.
Tuning parameters¶
- Script rigidity vs. discretion — how prescriptive the steps are. Too rigid and it marches off a cliff when the event is off-script; too loose and you are improvising again.
- Activation threshold — how low to set the trigger. Low activates fast but risks false alarms; high avoids them but loses time.
- Pre-delegated authority — how much decision right is granted in advance vs. escalated live; more speed against more risk of unchecked action.
- Guardrail tightness — how hard the ethical and legal limits on pre-authorized moves are set.
- Retirement criteria — how decisively the playbook stands down, guarding against a permanent emergency posture.
When it helps, and when it misleads¶
Its strength is that it removes improvisation and authority-confusion from the worst possible moment, so the response is fast, role-clear, and bounded.
Its failure modes: rigidity — following the script when the actual event does not match its anticipated form; pre-authorized powers that quietly over-reach, which is exactly what the ethical guardrail exists to check; the playbook written after the fact to justify a response someone already intends, run backwards as a cover document; and, if retirement is neglected, a standing emergency posture that never ends. The discipline is to treat the playbook as scaffolding rather than a script, prove it under a Readiness Drill and a tabletop, and keep the ethical guardrails and stand-down criteria as explicit as the action steps. The Incident Command System[1] is the canonical model for the roles-and-activation structure it needs.
How it implements the components¶
The Disruption Playbook fills only the choreography-and-authority subset — the components that turn stored options into a governed response:
activation_and_retirement_rule— defines the trigger that activates the response and the criteria that stand it down or retire it, keeping preparedness between panic activation and permanent emergency.wild_card_owner— names the accountable owner and activation authority, plus the response roles, so someone can actually declare and run the response.ethical_scope_guardrail— encodes the limits on pre-authorized action so a fast response stays proportionate and rights-respecting.
It choreographs; it does not stock or prove. The response options it sequences are held by the Contingency Option Register and Strategic Reserve Plan; the classes it answers come from the Wild-Card Workshop; the signals that put it on notice come from the Precursor Watchlist; and whether it actually works is proven by the Readiness Drill.
Related¶
- Instantiates: Wild-Card Contingency Mapping — the playbook is the governed response the whole map exists to make executable.
- Consumes: Contingency Option Register — the playbook sequences options the register holds; the Precursor Watchlist can supply its activation trigger.
- Sibling mechanisms: Contingency Option Register · Readiness Drill · Strategic Reserve Plan · Tabletop Exercise · Precursor Watchlist · Wild-Card Workshop · Contingency Map · Crisis Scenario Catalog · Red-Team Disruption Challenge
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Disruption Playbook operates as a repeatable ordered procedure or handoff sequence that coordinates action because it pre-scripts the response to a specific wild-card class — who does what, the trigger to activate and the signal to stand down, and the ethical limits on it all — so the response is executed under authority, not improvised in the moment.
Independent corroboration: The frozen evidence defines Disruption Playbook as 'Pre-scripts the response to a specific wild-card class — who does what, the trigger to activate and the signal to stand down, and the ethical limits on it all — so the response is executed under authority, not improvised in the moment', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Emergency management cohered incident playbooks with predefined activation triggers, authority, roles, handoffs, and stand-down conditions.
Related originating lineages:
- Military & Strategic Studies — Contingency planning supplied rehearsed responses to named disruption classes under explicit command.
- Organizational & Management Science — Business-continuity practice adapted playbooks to organizational shocks and ethical operating limits.
Review resolution: Both current reviews place disruption_playbook primarily in disaster_management; the reconciled classification retains only lineages that materially shaped the mechanism and keeps breadth of origin separate from reach.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
Activation and retirement are equally load-bearing. Playbooks fail as often by never standing down — normalizing an emergency footing that burns trust and resources — as by activating late. The retirement criterion is the half that teams most often leave out.
References¶
[1] Federal Emergency Management Agency. National Incident Management System. 3rd ed., U.S. Department of Homeland Security, 2017. Defines ICS as a standardized incident structure with named functions and roles activated as needed. registry ↩