A forcing function is a design element that prevents you from completing an action without first doing something else, essentially making it impossible (or very difficult) to make a specific mistake. The concept comes from human factors engineering, where designer Don Norman defined forcing functions as physical constraints built into systems to stop errors before they happen. You encounter them constantly: the microwave that won’t run with the door open, the car that won’t shift out of park unless your foot is on the brake, the software dialog box that makes you confirm before permanently deleting a file.
The idea has since expanded well beyond product design into healthcare, software, business management, and personal productivity. In every context, the core principle is the same: instead of relying on people to remember, pay attention, or exercise willpower, you change the system so the wrong action becomes structurally difficult or impossible.
The Three Types of Forcing Functions
Norman’s original framework breaks forcing functions into three categories based on how restrictive they are.
- Interlocks force operations to happen in a specific sequence. You can’t move to step two without completing step one. A microwave that won’t start until the door is closed is an interlock. So is a car ignition system that requires you to press the brake before shifting into drive. Interlocks are the most restrictive type because they control both what you do and the order you do it in.
- Lock-ins keep an operation active and prevent you from stopping it prematurely. A word processor that prompts you to save before closing an unsaved document is a lock-in. It doesn’t control the order of your actions, but it prevents you from accidentally abandoning work in progress. This makes lock-ins slightly less restrictive than interlocks.
- Lockouts prevent you from performing a dangerous or erroneous action entirely. A child-proof cap on a medicine bottle is a lockout. So is a safety gate blocking access to a restricted area. Lockouts are the least restrictive of the three because they only block one specific behavior rather than controlling a whole sequence.
How They Work Psychologically
Your brain operates in two modes. The first is fast, automatic, and effortless: the kind of thinking you use when driving a familiar route or filling out a routine form. The second is slow, deliberate, and analytical: the kind you use when solving a math problem or reading a contract carefully. Most of the time, you’re operating in the fast, automatic mode, which is efficient but prone to errors. You skip steps, repeat actions out of habit, or overlook details because your brain is essentially on autopilot.
Forcing functions work by deliberately interrupting that autopilot. They insert a friction point that forces you to shift into the slower, more deliberate mode of thinking, even for a moment. The Interaction Design Foundation describes this as “waking the user up” by disrupting the automatized performance of a task. A classic example: if you’re deleting files one by one and a confirmation dialog pops up each time, you’re more likely to notice when you’ve accidentally selected the wrong file. Without that interruption, the repetitive clicking can easily lead to a perseveration error, where you continue the same action one step past where you intended.
Forcing Functions in Healthcare
Patient safety is one area where forcing functions have proven especially valuable, because the consequences of human error can be fatal. One of the earliest forcing functions identified in healthcare was removing concentrated potassium from general hospital wards. For years, staff occasionally prepared intravenous solutions with concentrated potassium by mistake, causing a small but consistent number of deaths. By physically removing the substance from areas where the error could occur, the mistake became impossible rather than merely unlikely.
A study in emergency medicine found that a computerized forcing function improved how consistently staff followed restraint reordering protocols. The median time to renew restraint orders dropped by 56 to 64 minutes compared to the baseline period, and the rate of renewal orders per hour jumped dramatically, from 0.08 to 0.89. Time patients spent in restraints also trended downward by as much as 105 minutes. The researchers noted that while forcing functions have been widely promoted in medical literature as a remedy for errors and inconsistent practice, published studies of their actual use in clinical settings were rare at the time.
Forcing Functions in Software and Technology
Digital products use forcing functions constantly. Mandatory form fields that won’t let you submit until critical information is entered, password requirements that reject weak passwords, and version control systems that require a commit message before saving changes are all forcing functions. So is the “Are you sure?” dialog before you empty your trash, or the countdown timer some email services offer that lets you cancel a sent message within a few seconds.
In software development, code freezes serve as forcing functions for teams. By setting a hard deadline after which no new code can be added, a code freeze forces developers to finish and test their work within a defined window rather than letting features creep in indefinitely. Automated testing pipelines work similarly: code that doesn’t pass tests can’t be deployed, making it structurally impossible to ship broken software to users.
Forcing Functions for Personal Productivity
Outside of engineering and design, people use forcing functions to overcome procrastination and build accountability into their own behavior. The principle is the same: instead of relying on motivation or memory, you change the conditions so that the desired behavior becomes the path of least resistance.
Public commitments are one of the most common examples. Scheduling a webinar on a topic you haven’t fully prepared forces you to organize your ideas before the date arrives. Booking a meeting specifically to complete a task during the call (like making investor introductions in real time) prevents that task from sitting on a to-do list indefinitely. One entrepreneur describes leaving his laptop charger at home when working from a coffee shop: with a limited battery, he has no choice but to focus on high-priority work before the screen goes dark.
Financial commitments work the same way. Paying for a conference registration, hiring a coach, or investing in a course creates a sunk cost that motivates follow-through. The money is already spent, so the forcing function is the discomfort of wasting it.
Where They Sit in Safety Hierarchies
In occupational safety, the NIOSH Hierarchy of Controls ranks interventions by their expected effectiveness, from most to least reliable. The top tiers focus on eliminating hazards entirely or substituting them with safer alternatives, followed by redesigning the work environment. Education and encouragement sit at the bottom because they depend on individual behavior, which is inherently inconsistent.
Forcing functions live in the redesign tier. They don’t eliminate a hazard, but they restructure the environment so that human error is far less likely to cause harm. This makes them significantly more effective than training or warning labels alone, which rely on people to remember and comply every single time. A sign that says “Danger: High Voltage” is education. A locked gate that physically prevents access to the high-voltage area is a forcing function.
How to Create an Effective Forcing Function
Designing a good forcing function starts with identifying the specific behavior you want to trigger or the specific error you want to prevent. Vague goals produce vague constraints. “Reduce mistakes” is too broad. “Prevent users from submitting an order without confirming the shipping address” is specific enough to design around.
Next, choose the right mechanism. Time pressure (hard deadlines, expiring offers), accountability (public commitments, scheduled reviews), design constraints (required fields, physical interlocks), and environmental changes (removing temptations, restricting access) all work, but the best choice depends on context. A forcing function in a nuclear power plant needs to be absolute. A forcing function for your morning writing habit just needs to be inconvenient enough to keep you on track.
Calibration matters. A forcing function that’s too aggressive creates frustration and workarounds. If users find your safety constraint annoying enough, they’ll tape over the sensor or find a bypass. Leave some flexibility for genuine exceptions, monitor whether the function is actually changing behavior, and adjust the intensity based on what you observe.