Absolutely, Phil — continuing with Batch 8 of the General Mental Models Pack, covering models 71–80. These are clean Markdown files, ready to drop into:
Mental Models (General)/
This batch focuses on risk, resilience, antifragility, scenario planning, and safety engineering — the models that keep systems alive under stress.
Let’s get into it.
📄 71 — Black Swan Events
Definition
Rare, unpredictable events with massive impact that are only obvious in hindsight.
When to Use
• Risk management • Strategic planning • Financial decisions • System design • Crisis preparation
How It Improves Reasoning
It forces you to consider extreme, low‑probability, high‑impact events that traditional forecasting misses.
Steps
- Identify areas vulnerable to extreme events.
- Assess potential impact.
- Build buffers or redundancies.
- Avoid overconfidence in predictions.
Example
The 2008 financial crisis was a Black Swan for most institutions.
Prompts
• “Identify potential Black Swan vulnerabilities.” • “How could this system fail catastrophically?”
📄 72 — Fragility / Antifragility
Definition
• Fragile systems break under stress. • Robust systems resist stress. • Antifragile systems improve because of stress.
When to Use
• System design • Risk analysis • Organizational strategy • Personal development
How It Improves Reasoning
It helps you design systems that benefit from volatility instead of collapsing under it.
Steps
- Identify stressors.
- Assess system response.
- Strengthen robustness or build antifragility.
- Introduce controlled stressors for improvement.
Example
Muscles grow stronger when stressed — an antifragile system.
Prompts
• “Assess fragility vs antifragility in this system.” • “How can this system benefit from stress?”
📄 73 — Risk Homeostasis
Definition
People adjust their behavior to maintain a constant level of perceived risk.
When to Use
• Safety design • Policy decisions • Behavioral analysis • System interventions
How It Improves Reasoning
It reveals why safety improvements sometimes lead to riskier behavior.
Steps
- Identify perceived risk level.
- Observe compensating behaviors.
- Adjust incentives or design.
- Re‑evaluate actual vs perceived risk.
Example
Drivers with ABS brakes may drive more aggressively.
Prompts
• “Identify risk compensation behaviors.” • “How does perceived risk differ from actual risk?”
📄 74 — Red Teaming
Definition
A structured process where an independent group challenges assumptions, plans, or systems to find weaknesses.
When to Use
• Security • Strategy • System design • Risk assessment • Critical decisions
How It Improves Reasoning
It exposes blind spots and reveals vulnerabilities that insiders miss.
Steps
- Define the target system or plan.
- Assign an independent team.
- Challenge assumptions and stress‑test.
- Review findings and adjust.
Example
A cybersecurity team simulating an attack to test defenses.
Prompts
• “Perform a red‑team analysis on this plan.” • “Identify assumptions that should be challenged.”
📄 75 — Pre‑Mortem Analysis
Definition
Imagining that a project has failed and working backward to identify the causes.
When to Use
• Project planning • Risk management • Strategic decisions • Complex initiatives
How It Improves Reasoning
It reveals failure modes before they occur and encourages proactive mitigation.
Steps
- Assume the project has failed.
- List possible reasons.
- Prioritize by likelihood and impact.
- Mitigate proactively.
Example
Before launching a product, the team imagines it flopped and identifies why.
Prompts
• “Conduct a pre‑mortem for this project.” • “List reasons this initiative might fail.”
📄 76 — Stress Testing
Definition
Evaluating how a system performs under extreme or abnormal conditions.
When to Use
• Financial systems • Infrastructure • Software • Operations • Crisis planning
How It Improves Reasoning
It reveals weaknesses that only appear under pressure.
Steps
- Identify stress scenarios.
- Apply extreme conditions.
- Measure system response.
- Strengthen weak points.
Example
Banks simulate economic crashes to test resilience.
Prompts
• “Stress‑test this system under extreme conditions.” • “Identify failure points under load.”
📄 77 — Safety Margins
Definition
Building extra capacity or buffer into a system to handle uncertainty or unexpected stress.
When to Use
• Engineering • Planning • Risk management • Operations • Budgeting
How It Improves Reasoning
It prevents failure when conditions exceed expectations.
Steps
- Identify expected load.
- Add buffer capacity.
- Test under higher loads.
- Adjust margin as needed.
Example
Bridges are designed to hold far more weight than expected.
Prompts
• “Determine appropriate safety margins for this system.” • “Where is additional buffer needed?”
📄 78 — Worst‑Case Bounding
Definition
Evaluating the worst possible outcome and ensuring it is survivable.
When to Use
• Risk analysis • Strategic planning • Safety engineering • Financial decisions
How It Improves Reasoning
It prevents catastrophic failure by ensuring the worst case is acceptable.
Steps
- Identify worst‑case scenario.
- Assess impact.
- Ensure survival or containment.
- Adjust plan accordingly.
Example
A business ensures it has enough cash to survive a 6‑month revenue drop.
Prompts
• “Define the worst‑case scenario and ensure survivability.” • “What is the maximum acceptable downside?”
📄 79 — Scenario Planning
Definition
Developing multiple plausible future scenarios to improve preparedness and adaptability.
When to Use
• Long‑term planning • Uncertain environments • Strategic decisions • Market forecasting
How It Improves Reasoning
It reduces reliance on a single forecast and improves resilience.
Steps
- Identify key uncertainties.
- Develop multiple scenarios.
- Test strategies against each.
- Choose robust options.
Example
A company plans for high growth, moderate growth, and recession scenarios.
Prompts
• “Create multiple scenarios for this decision.” • “Which strategy is robust across scenarios?”
📄 80 — Error Budgeting
Definition
Allocating a tolerable amount of failure or error within a system to balance reliability and innovation.
When to Use
• Engineering • SRE (Site Reliability Engineering) • Operations • Product development
How It Improves Reasoning
It prevents over‑engineering and encourages innovation while maintaining reliability.
Steps
- Define acceptable error rate.
- Allocate error budget.
- Monitor usage.
- Slow changes when budget is nearly consumed.
Example
A service with 99.9% uptime allows 0.1% downtime for experimentation.
Prompts
• “Define an error budget for this system.” • “How should changes be paced based on error budget usage?”