i

Constraint & Forcing Function

STR·08 · 8 of 11

The strongest instruction is the impossible action: design so the wrong thing cannot be done.

traditional Long-standing practice, with no single citable origin. Why: A design practice with a long lineage rather than one founding paper.

The same task, built twice

Both panes below are real interfaces. They respond, they can be got wrong, and each is timed from your first move in it. The times are not a study — two panes, one reader, no controls. They are here to make a difference you can feel into a number you can see, and nothing is recorded or sent anywhere.

Your task

Book a collection slot. The depot is closed at weekends and cannot take same-day bookings.

Validated afterwards—

Both rules exist. Neither is visible until you have already chosen, typed and submitted. The interface knew the answer before you started and waited to tell you.

Constrained beforehand—

Weekdays only, from tomorrow onwards.

Weekends and today are simply not offerable. Nothing is hidden — the rule is stated above the picker — and the invalid choice was never made available to make.

What to watch A constraint you can violate is a validation message waiting to happen. The right-hand pane cannot produce an error because it cannot produce an invalid state.

The principle

OriginNorman (1988) on constraints; the manufacturing lineage is poka-yoke (Shingo).
EvidenceThe ATM that returns your card before the cash (Floor 5's classic — the machine holds the money hostage against your forgetfulness); SIM-card notches; plugs that only fit one way.
Limits & misuseConstraints protect; they also imprison. A forcing function on a rare-but-legitimate action becomes the workaround culture that defeats it — the taped-over sensor is a constraint's obituary. The Hawaii alert is what its absence costs.