Physical Constraint Design For Impossibility¶
Make the wrong action physically impossible, materially rejected, or harder than the correct action.
The Diagnostic Story¶
Symptom: The same wrong action keeps recurring despite training, signage, checklists, and reminders. The incorrect action is physically possible — often easier, faster, or visually similar to the correct one — so it happens under load, interruption, or fatigue. Defects are found downstream, after cost or harm has already accumulated, because the prevention strategy relies on human vigilance rather than on the structure of the system. Near-misses cluster around the same ports, steps, labels, or controls.
Pivot: Stop asking memory, training, and inspection to compensate for a permissive action space. Instead, identify the physical or procedural degrees of freedom that currently allow the wrong action, and change shape, fit, sequence, interlock, default state, or access route so the undesirable action is blocked or rejected before judgment must intervene.
Resolution: The wrong action is no longer available in the action space under ordinary conditions, so error prevention no longer depends on sustained vigilance. Downstream exception paths stop being overloaded with the same preventable defect class. The system's safety is embedded in its structure rather than delegated to the people operating it.
Reach for this when you hear…¶
[manufacturing] “We've retrained the line three times for the same wrong-orientation assembly — just change the connector shape so it physically cannot go in backwards.”
[hospital pharmacy] “The look-alike vials keep getting mixed up; labels and warnings haven't fixed it in two years — the storage design needs to make co-selection impossible.”
[software deployment] “If running the migration in the wrong environment is possible from the same terminal session, someone will eventually do it — make production credentials unavailable in the dev shell.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A recurring harmful action remains available in the action space, so prevention depends on vigilance, instruction, reminders, inspection, or after-the-fact correction rather than on the structure of the system itself.
Show the applicability expression
Applicability expression3 distinct conditions
groundedpartly groundedopen
3 conditions, all required.
3Required in every casenumbered 1–3
These hold no matter which pattern applies.
Training-resistant recurring error · open
The same wrong assembly, connection, sequence, medication, handoff, or configuration recurs despite training.
The source archetype describes the situation as follows: The same wrong assembly, wrong connection, wrong sequence, wrong medication, wrong handoff, or wrong configuration recurs despite training. The normalized requirement above isolates the load-bearing portion used in this condition set.
Wrong action easier · 3 cases · 3 matched
The incorrect action is physically similar to, easier than, or more available than the correct action.
The source archetype describes the situation as follows: The incorrect action is physically similar to the correct action, easier than the correct action, or enabled by a permissive interface. The normalized requirement above isolates the load-bearing portion used in this condition set.
Late defect detection · open
Downstream inspection finds the defect only after cost, delay, risk, or irreversible harm accumulates.
The source archetype describes the situation as follows: Downstream inspection can detect the defect only after cost, delay, risk, or irreversible harm has already accumulated. The normalized requirement above isolates the load-bearing portion used in this condition set.
Other requirements and context (3)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Source review — the source wording is not structurally clear enough to support a formal trigger role without clarification.
Supporting contextThe task is performed under time pressure, fatigue, interruption, low visibility, high cognitive load, or handoff ambiguity.
Solution feasibilityThe error class has a clear material, spatial, sequence, fit, access, or default-state signature that can be redesigned.
Source reviewThe target accepted prime is error_proofing_poka_yoke and direct accepted coverage is absent in the scaled queue.
Coverage
1 of 3 conditions grounded · 2 open.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (1)
- Error Proofing (Poka-Yoke): Error prevention.
Also references 20 related abstractions
- Access Control: Restrict system access.
- Cognitive Load And Attentional Capacity
- Constraint: Limits possibilities to guide outcomes.
- Controllability: Ability to steer system.
- Data Integrity: Accuracy and consistency preserved.
- Decision: Committing to one alternative from a set under uncertainty and trade-off, collapsing open deliberation into a chosen path and foreclosing the others.
- Design for Implementation: Real-world feasibility.
- Fail-Safe: Default to safe state on failure.
- Feedback: Outputs influence inputs.
- Human-Centered Accommodation: Adapt to human limits.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Accessory Coupled Configuration Completion · implementation variant · recognized
Attach a mode-specific internal reconfiguration element to the accessory that enables that mode, making configuration completeness automatic.
Interlock Human Or Material Access With A Recorded · implementation variant · recognized
Interlock human or material access with a recorded decontamination sequence so the containment boundary opens only after verified completion.
Editorial Notes¶
Problem Classification¶
Classification: Correctness, Conformance & Formal Validity Failure → Feasibility & Requirement Consistency
Problem kernel: harmful action remains physically feasible
Rationale: Earliest causal condition: A recurring harmful action remains available in the action space, so prevention depends on vigilance, instruction, reminders, inspection, or after-the-fact correction rather than on the structure of the system itself.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A recurring harmful action remains available in the action space, so prevention depends on vigilance, instruction, reminders, inspection, or after-the-fact correction rather than on the structure of the system itself. That is a feasibility requirement and invariant consistency problem because Required constraints, guarantees, relations, or necessary conditions are absent, mutually incompatible, intrinsically impossible, or unenforceable together within the stated scope.
Review outcome: Independent reviewer agreement; high confidence.