domains / families / general / thinking-margin-of-safety

thinking-margin-of-safety

separate

When provisioning, setting a limit, or committing an estimate under uncertainty, size a buffer to residual error and the cost of breach—not to the optimistic edge.

When to use

• Capacity, timeouts, pool sizes, queue depths, storage, or SLA numbers under load uncertainty
• Timeline or budget commitments where underestimation is costly
• Architecture headroom when scaling or recovery is slow
• Any public or production commitment where being wrong has asymmetric downside

When not to use

• Breach is detected immediately and fixed near-zero cost (fast auto-scale, live-tunable limit)—static fat buffers waste resources
• `cost(buffer) > P(breach) × cost(breach)`—right-size or measure instead of maxing out
• Uncertainty is eliminable by measurement or lookup—get the real number first
• Stopping-criterion / search budget problems—use bounded rationality, not padding
• Fully known parameters and low stakes where edge optimization is the goal

Skill page

Source