Backup Systems/Redundancy

The engineering principle of building duplicate capabilities so that failure of one component doesn't cause system failure—having more capacity than the minimum needed for normal operations. Airplanes have redundant hydraulic systems. Data centers have backup power. Critical software runs on multiple servers. The trade-off: redundancy costs resources (duplicate systems, excess capacity) but provides reliability (graceful degradation under failure rather than catastrophic collapse). In organizations: cross-training employees, maintaining relationships with multiple suppliers, and keeping cash reserves are all forms of redundancy.

When to use it

When system reliability is critical and single points of failure exist; when key-person risk threatens organizational continuity; when designing systems that need to be fault-tolerant; when evaluating whether the cost of redundancy is justified by the cost of failure.

How it can help

Map critical dependencies and add redundancy proportional to failure consequences. For organizations: the most common single point of failure is key-person risk—only one person who can do X. Cross-training is the cheapest organizational redundancy. For systems: identify which failures would be catastrophic vs. merely inconvenient, and invest in redundancy accordingly.