Constraints Principle
Well-designed constraints limit invalid actions or make their boundaries clear while preserving valid choice and recovery.
Direct explanation
What it means
Physical, semantic, cultural, and logical constraints help people infer what is possible. Disabling everything without explanation removes information rather than guiding action.
Preventing impossible or unsafe operations reduces errors, but overconstraint can block edge cases, autonomy, and accessibility.
Research anchor: Donald A. Norman, 2013
Research and interpretation
What the research found
The principle is a design synthesis of how physical, semantic, cultural, and logical limits guide action.
Error-prevention and constraint design are central to usability practice, supported by compatibility, feedback, and human-error research.
Popular advice versus careful use
Common shorthand: Disable anything users should not do.
Prevent clearly invalid or harmful action, explain the boundary, and retain fair recovery and exception handling.
How designers apply it
- 01
Prevent selecting an end date before a start date.
- 02
Limit file input to supported formats while explaining conversion.
- 03
Require review before an irreversible permission change.
Original UI examples
mobile booking
Travel dates
Past dates are unavailable and the reason is stated for screen readers and sighted users.
The picker prevents invalid input without leaving a silent disabled grid.
desktop enterprise
Role editor
Conflicting permissions are detected with an explanation and safe resolution choices.
The admin learns the logical boundary rather than hitting a generic error.
Submit button
Less effective
Disable it with no indication of what remains.
Better fit
Keep the requirement visible, identify incomplete fields, and focus the first issue on request.
Sometimes validation on submit is more understandable than premature disabling.
Limits and failure modes
A constraint only helps when the system’s validity model is correct and the user understands the remaining options.
Common mistakes
- Using disabled controls as undocumented instructions.
- Blocking rare valid cases because the happy path is simpler.
When it should not dominate
- To force business-preferred choices.
- When the system cannot reliably know that an action is invalid.
Responsible use
Accessibility
Communicate constraints in labels and programmatic descriptions, keep errors specific, and ensure disabled states remain perceivable and discoverable.
On mobile: Use appropriate input modes and inline guidance without hiding the valid range.
Ethics and context
Constraints must protect users or system integrity, not obstruct cancellation, refusal, data access, or lawful exceptions.
On desktop: Expose complex rules, dependencies, and exception requests near the control.
Designer checklist
- Define the invalid state and reason.
- Communicate the valid range before action.
- Design exception and recovery paths.
Check your understanding
Which statement applies Constraints Principle most carefully?
Practice and continue learning
See ideas in real interfaces
These external interfaces are editorial references, not examples created to demonstrate this principle.
Sources and further reading
- 01Open source
The Design of Everyday Things: Revised and Expanded
Donald A. Norman · 2013 · Basic Books
Book · primary or original source
- 02Open source
10 Usability Heuristics for User Interface Design
Jakob Nielsen · 1994 · Nielsen Norman Group
Official documentation · primary or original source
Continue the graph
Related principles
usability heuristic
Feedback Principle
Every meaningful action should produce timely, perceivable feedback that accurately communicates the resulting system state.
model
Affordances
An affordance is a possible action supported by the relationship between an actor’s capabilities and an object or environment.
principle
Postel’s Law
Accept safe, unambiguous input variation where useful and produce predictable output, while rejecting ambiguity that threatens security or interoperability.