Constraints
Rules or boundaries that limit available actions and steer users toward valid outcomes.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/constraints/
01What it means
Constraints reduce the set of possible actions. They may be physical, logical, semantic, or cultural. In interfaces, constraints can disable unavailable commands, limit formats, sequence steps, or make invalid combinations impossible.[1][2]
- Physical
- The form or environment makes some actions impossible
- Logical
- Relationships and state narrow what can follow
- Semantic
- Meaning suggests which actions make sense
- Cultural
- Learned conventions shape expectation
- Policy
- Rules, permissions, safety, and obligations
- Feedback
- People can understand why an action is unavailable
A constraint should prevent error without blocking legitimate goals, excluding users, or disguising a business preference as technical necessity.
02Why it matters
Well-designed constraints prevent errors before they require explanation. They simplify decisions, protect data, and make the structure of a task easier to infer.
03When to use it
Use constraints when an action is impossible, unsafe, irreversible, dependent on prerequisites, or valid only within a known range.
04How it works
- Define which actions and values are valid at each state.
- Prefer removing impossible choices over displaying them as tempting dead ends.
- Explain unavailable actions when users need to know they exist.
- Use forgiving defaults, validation, and reversible actions before hard blocks.
- Test whether constraints prevent errors without trapping legitimate edge cases.
05A practical example
A booking form prevents choosing a return date before the departure date, updates available dates as the itinerary changes, and explains why sold-out dates cannot be selected.
06Where it breaks
Over-constraint can block expert workflows, uncommon but valid inputs, or recovery. Disabled controls with no explanation are opaque. Constraints should reflect real rules, not compensate for incomplete product logic.
Common mistakes
- Validating only after submission when invalid input could be prevented earlier.
- Disabling a control without saying what prerequisite is missing.
- Using rigid format constraints that reject legitimate names, addresses, or identifiers.
07Sources
- The Design of Everyday Things, Revised and ExpandedBasic Books / Don Norman · bookThe Design of Everyday Things, Revised and Expanded
- Understanding Success Criterion 3.3.4: Error PreventionW3C Web Accessibility Initiative · standard guidanceUnderstanding Success Criterion 3.3.4: Error Prevention