# Constraints

Rules or boundaries that limit available actions and steer users toward valid outcomes.

- Type: principle
- Domain: Research & behavior
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/constraints/>)

## What 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.

## Why 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.

## When to use it

Use constraints when an action is impossible, unsafe, irreversible, dependent on prerequisites, or valid only within a known range.

## How it works

1. Define which actions and values are valid at each state.
2. Prefer removing impossible choices over displaying them as tempting dead ends.
3. Explain unavailable actions when users need to know they exist.
4. Use forgiving defaults, validation, and reversible actions before hard blocks.
5. Test whether constraints prevent errors without trapping legitimate edge cases.

## A 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.

## Where 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.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/constraints/#visualization-constraints>)

## Sources

1. [The Design of Everyday Things, Revised and Expanded](<https://media.aanda.psu.edu/sites/media/aa/files/documents/norman_design-of-everyday-things.pdf>) — Basic Books / Don Norman · book
2. [Understanding Success Criterion 3.3.4: Error Prevention](<https://www.w3.org/WAI/WCAG22/Understanding/error-prevention-legal-financial-data.html>) — W3C Web Accessibility Initiative · standard guidance

## Related topics

- [Affordance](<https://wiki.soroush.uk/topic/affordance/>)
- [Feedback](<https://wiki.soroush.uk/topic/feedback/>)
- [Choice Architecture](<https://wiki.soroush.uk/topic/choice-architecture/>)
