Slack
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
To maintain system agility and responsiveness, a certain degree of 'idle resources' (Slack) must be preserved. If everyone is 100% busy, the system becomes congested, and any unexpected event can cause a collapse.
SCAFFOLDING EFFECT
Reduce cognitive load
Anti-involution. Do not pursue 'saturated workload'. It is necessary to leave 20% slack time for the team. That is not waste; it is a buffer airbag for black swan events.
Anchor fast decisions
When a system is fully loaded (utilization approaching 100%), it loses buffer capacity, and any disturbance cannot be absorbed. Small fluctuations can amplify along the chain into congestion or even collapse (similar to how traffic is extremely fragile at full capacity). Retaining a certain amount of idle resources (time, manpower, capacity, capital) is 'slack', serving as elastic space to absorb surprises.
MINIMUM ACTION
In progress 0/4Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Slackverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS