Crisis management¶
The coordinated preparation, decision making, communication, response and learning used when an unexpected threat endangers an organization and its stakeholders under severe time pressure.
Core Idea¶
Crisis management spans prevention and readiness, acute response, continuity, stakeholder communication, recovery and post-event learning; operational crises, disasters and reputational events require different expertise and authority. Signals trigger escalation, a cross-functional authority structure builds a shared situation model, prioritizes life and stakeholder harms, allocates actions, communicates under uncertainty and adapts as evidence changes. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.
Scope of Application¶
Crisis management belongs to organizational resilience and is useful where the analyst can specify the typed organizational resilience carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the organization and stakeholders, crisis definition and trigger, command and decision rights, situation assessment, priorities, response and continuity actions, communication, legal and ethical duties, resource constraints, recovery, documentation and after-action learning are explicit. The scope is broad within that domain but bounded by the need for the organization and stakeholders, crisis definition and trigger, command and decision rights, situation assessment, priorities, response and continuity actions, communication, legal and ethical duties, resource constraints, recovery, documentation and after-action learning are explicit.
Clarity¶
The abstraction clarifies a crowded vocabulary by making the organization and stakeholders, crisis definition and trigger, command and decision rights, situation assessment, priorities, response and continuity actions, communication, legal and ethical duties, resource constraints, recovery, documentation and after-action learning are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.
Manages Complexity¶
Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Crisis management. Crisis management compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.
Abstract Reasoning¶
- Identify the carrier. State what the elements, states, objects, or observations are: the typed organizational resilience carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the organization and stakeholders, crisis definition and trigger, command and decision rights, situation assessment, priorities, response and continuity actions, communication, legal and ethical duties, resource constraints, recovery, documentation and after-action learning are explicit independently of one notation or implementation.
Knowledge Transfer¶
Knowledge transfers strongly among subfields of organizational resilience because they reuse the typed organizational resilience carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, Signals trigger escalation, a cross-functional authority structure builds a shared situation model, prioritizes life and stakeholder harms, allocates actions, communicates under uncertainty and adapts as evidence changes., and type the carrier, state every parameter and convention in the definition, test that the organization and stakeholders, crisis definition and trigger, command and decision rights, situation assessment, priorities, response and continuity actions, communication, legal and ethical duties, resource constraints, recovery, documentation and after-action learning are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.
Relationships to Other Abstractions¶
Current abstraction Crisis management Domain-specific
Parents (1) — more general patterns this builds on
-
Crisis management is a kind of Resilience Prime
The proposed strict upward parent is
prime:resilience.
Hierarchy paths (4) — routes to 4 parentless roots
- Crisis management → Resilience → Adaptive Capacity
- Crisis management → Resilience → Robustness
- Crisis management → Resilience → Homeostasis → Stability
- Crisis management → Resilience → Homeostasis → Discrepancy-Driven Correction → Feedback
Neighborhood in Abstraction Space¶
Crisis management sits in a moderately populated region (51st percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.
Family — Risk, Scheduling & Operational Control (32 abstractions)
Nearest neighbors
- Strategic control — 0.89
- Decision downloading — 0.89
- Organizational memory — 0.88
- Structured what-if technique — 0.88
- Organizational identity — 0.88
Computed from structural-signature embeddings · 2026-09-08