Design Intent
Design intent is the product decision and intended behaviour that an implementation must preserve, not merely its visual appearance.
- Product decisions
- Implementation fidelity
What design intent means
Design intent is the product decision and intended behaviour that an implementation must preserve across content, state, devices and constraints.
The term focuses on what the product is meant to communicate, enable, prevent or respond to when it is built for real use.
What design intent includes
- 01
Information priority
The implementation should preserve which information matters most and how that priority is expressed across content changes.
- 02
Interaction and feedback
The intended interaction, system response and user feedback remain part of the design, not separate implementation details.
- 03
Consequence
Design intent includes the consequence of a user action or system state, so behaviour is judged by what it preserves for the user.
- 04
Responsive change
The intent must survive changes in content, viewport and device rather than depend on a single fixed visual state.
- 05
Accessibility
Accessibility is part of the intended behaviour because the same product decision must remain available across user needs and constraints.
Why visual sameness is not enough
Pixel identity can conflict with intent when content or viewport changes. Production fidelity is therefore correspondence to intent, not visual sameness.
A build can look close to a static design and still miss the product decision if hierarchy, feedback, responsive behaviour or accessibility changes in use.
Terminology note
Discuss your product intent
Talk to Tcules about preserving the product decisions and intended behaviours that matter in implementation.