Dead Man's Switch: The Engineering Concept Your Accountability App Is Built On
Dead man's switch defined: a control that fails safe when engagement stops, no report required. What it means for accountability app and habit-tracking design.
A dead man’s switch is a control that requires continuous, active engagement from an operator and defaults to a safe or alerting state the instant that engagement stops — without the operator doing anything to cause the trigger. Absence of input is the input.
The term comes from railway engineering. A train engineer’s brake handle or foot pedal has to stay depressed; release it, intentionally or not, and the brakes apply on their own. Stationary power tools work the same way — the trigger cuts power the instant a hand releases it. Gas-pump nozzles and lawnmower safety bars are consumer versions of the same idea. The phrase later got borrowed, more loosely, by computer-security and estate-planning tools that release a file if someone fails to check in.
Most accountability apps are built the opposite way. They require an active step — log the miss, submit a check-in, report the failure — before anything happens. That’s backwards from a dead man’s switch: doing nothing produces no result at all. And the moment someone is most likely to fail — half-asleep, out of willpower, phone dying — is exactly when they’re least able to perform an extra step. Alarm Compliance as an Engineering Problem covers this failure mode in more depth.
An accountability structure built like an actual dead man’s switch flips it: staying quiet triggers the response, and checking in or submitting proof is what has to happen to stop it. A few apps work this way, including DontSnooze (https://dontsnooze.io). A human accountability partner who calls to check on you, rather than waiting to be told you failed, works the same way.