Lockin

Glossary → Forcing function

What is a forcing function

A forcing function is a structural constraint that makes a desired behavior unavoidable by blocking progress until that behavior is completed — removing willpower from the equation entirely.

Definition

A forcing function is a design feature or environmental constraint that prevents a person from proceeding to the next step until a required prior action has been completed. Rather than relying on memory, motivation, or judgment in the moment, the system is structured so that the correct behavior happens by default and the alternative is simply not available. The classic industrial example is the two-hand safety press: a machine operator cannot engage a hydraulic press unless both hands are simultaneously pressing separate buttons, physically preventing the hands from being inside the press at the moment of activation. The desired behavior — keeping hands clear — is not requested or reminded, it is enforced by the mechanism itself. Other familiar examples include the ATM that will not dispense cash until the card is removed, the car interlock that prevents the gear shift from leaving park unless the brake pedal is depressed, and the microwave that cannot run with its door open. In each case the environment has been designed so that one action is gated on another. Donald A. Norman formalized the concept in interaction design in his 1988 book The Design of Everyday Things, describing forcing functions as a subcategory of physical constraints: situations where the actions are constrained so that failure at one stage prevents the next step from happening. Norman's framework positioned forcing functions alongside interlocks and lock-ins as tools that encode correct procedure into the artifact itself rather than relying on the user to remember or choose correctly. Atul Gawande extended the concept into high-stakes professional practice in The Checklist Manifesto (2009), arguing that surgical and intensive-care checklists function as forcing functions: a procedure step cannot be marked complete until it is actually performed, and the checklist structure makes it difficult to skip steps under time pressure or cognitive load. Gawande's data showed that structured checklists reduced ICU central-line infection rates and surgical complication rates in ways that voluntary reminders and training alone had failed to achieve. The underlying logic is consistent across all these domains: when a behavior is important enough that relying on human intention is insufficient, the environment can be redesigned so the behavior is structurally required. Forcing functions are most effective when the cost of the skipped behavior is diffuse or delayed — which is exactly when human motivation tends to fail.

Where it comes from

The term originates in industrial safety engineering, where interlock mechanisms were designed to physically prevent hazardous machine operations unless prerequisite safe conditions were met. Donald A. Norman brought it into mainstream design discourse in 1988 through The Design of Everyday Things.

How Lockin uses this

Lockin operates as a forcing function for daily commitments. When a user stakes money against a habit — whether building a morning run or eliminating late-night scrolling — the financial stake creates a hard gate on the day. Before midnight, the commitment is either completed and the stake preserved, or it is not and the stake is forfeited. There is no third option, no deferral, no "I'll make it up tomorrow." This removes the most common failure point in habit formation: the in-the-moment negotiation with oneself about whether today counts.

Citations

Related terms

Where this shows up in practice

Stop deciding. Start staking.

Free to download. You set the habit, the limit, the stake, and the charity.

Author

The Lockin Team — Lockin Editorial

Last verified