Principle
Stabilize chaos before asking for a complete explanation
In a fire, the first question is not which theory of combustion the meeting prefers.
When it fits
- Conditions are changing so quickly that cause-and-effect analysis cannot guide the immediate response.
When to avoid it
- Use established emergency and safety procedures when they exist; this element is not a substitute for domain-specific incident command.
Why it matters
Take the smallest competent action that reduces immediate disorder or harm, then observe what becomes stable enough to analyze. Once the situation stops changing faster than your understanding, move into diagnosis or controlled experimentation. Keep the stabilizing action bounded and visible so urgency does not become a license for arbitrary control.
An example
During an uncontrolled integration flood, stop or throttle the incoming flow before trying to explain every malformed message.
Check your result
The situation becomes stable enough that the next diagnostic observation has meaning.
Keep this limit in mind
- Use established emergency and safety procedures when they exist; this element is not a substitute for domain-specific incident command.
Evidence and sources
In the Cynefin framework's chaotic domain, Snowden and Boone recommend acting first to establish order, then sensing where stability exists before moving toward a more analyzable context.
What counts as safe stabilization depends on the domain; emergency, medical and security situations may require formal incident protocols.
A Leader's Framework for Decision Making · Abstract; chaotic context