Fallback: Why Should There Be a Next Step When the Preferred Option Fails?

Fallback means moving to a pre-approved alternative when the preferred method is unavailable. If a smart lock cannot recognise a fingerprint and a physical key is used instead, what is preserved is not the same recognition experience but the core ability to open the door.

Fallback is not retrying, which uses the same method again. Nor is it redundancy, which usually duplicates similar resources. Graceful degradation generally keeps the same service running at reduced quality, whereas fallback may change the method and accept a slower or less convenient result.

The important work is not merely having an alternative. The trigger for switching, the function to preserve and the trade-off to accept must be clear in advance. Falling back at every minor fault can conceal defects in the preferred method; never falling back can let a local failure halt the entire action. Good fallback turns unavoidable failure into a state from which action can continue.