The GFunnel Methodology
Crisis Response Algorithm
The steps
- Detect. Confirm crisis is real before responding. Many “crises” are urgency dressed as emergency.
- Stop the bleeding. Address First Kingdom physical impact before processing causes.
- Centralize command. Per Mentalism: in crisis, decision-making must converge to a clear Third Kingdom locus. Distributed reactive decisions amplify the crisis.
- Establish the gradient between current state and acceptable state. The gradient is what the response will channel.
- Sequence: triage → stabilization → root cause → prevention. Do not jump to root cause while triage is incomplete.
- Communicate per Vibration. Match frequency of stakeholders. Panic responded to with calm reduces escalation. Calm responded to with panic produces panic.
- Document the entire crisis as it happens. Notes, decisions, communications. Per Database step: post-crisis review requires real-time documentation.
- Conduct post-crisis integration. Per Layer I.G: failures become substrate for resilience. What does this crisis teach about the system’s next iteration?
- Apply Repetition. Each crisis handled informs the next at higher baseline. A crisis without integration is repeated.
Articles on this
No articles on this one yet.
From the GFunnel Methodology v5.1 by Cameron Garlick, licensed CC BY 4.0. Steps are reproduced word for word.