Constraints can make the correct action the only feasible action

What it is

When a design limits options, order, or state so that people can complete only an action meeting necessary conditions in the current situation, it makes the correct action the only feasible one. This forcing function appears in required critical information, prerequisite checks, mutually exclusive choices, or a flow that cannot continue until confirmation is complete. Its purpose is to prevent a particular error before it happens rather than explain it afterward.

Why it happens

The system encodes risk rules into interaction state: until a condition is met, subsequent action is unreachable or cannot submit; after it is met, the path opens. This transfers judgment from user memory and attention to system execution. The limit is valuable only when its condition genuinely fits the goal and risk. If a system misunderstands intent, hides exceptions, or fails to explain the block, the sole feasible path becomes meaningless obstruction.

Studying it

Select behaviors to prevent from real error and risk records. Test whether the constraint blocks the behavior, incorrectly blocks legitimate work, and can be understood and satisfied. Observe circumvention, help seeking, abandonment, completion time, and error consequence. Stress-test exception paths to ensure permission differences, edge input, and recovery cases do not leave people permanently unable to proceed.

Where it stops holding

Forcing functions suit cases with consequential outcomes, clear rules, and few legitimate exceptions. They do not suit locking down every preference, low-risk exploration, or uncertain information; excessive forcing increases friction, invites fabricated entries, and weakens expert ability to handle anomalies. Many cases are better served by a prompt, default, or reversible confirmation than a single channel.

Applying it

• Block only clear safety, integrity, or compliance risks, and state necessary conditions and the reason for blockage before the attempted action.
• Offer controlled alternative flows, authorization, or draft saving for legitimate exceptions rather than making people falsify input to pass a check.
• Review block rate, abandonment, and circumvention continuously to ensure the constraint reduces real risk rather than valid work.

Related

• Same group: B2.05.1 Physical constraints limit possible actions · B2.05.2 Semantic constraints are determined by contextual meaning · B2.05.3 Cultural constraints depend on learned social convention · B2.05.4 Logical constraints are inferred from relationships among elements
• Nearby: B2.06 Feedback · B2.11 Error prevention
• Search terms: forcing function · error prevention · constraint