Statement
P08 Quality lives in the accumulation of details
Quality rarely depends on one big decision. It is recognized in many small decisions that align with one another.
Tension
Explanation
No one separates the interface, engineering, and content: people experience a complete product. One small inconsistency is tolerated; a hundred turn its use into constant friction.
Go deeper: Tension
Users do not separate interface, engineering and content. They experience a complete product. One small inconsistency may be tolerable; a hundred inconsistencies turn use into constant friction.
Meaning
Explanation
Typography, copy, focus, empty states, errors, and transitions form a single experience. No detail can compensate for a poor solution on its own, but their accumulation strengthens or erodes trust.
Go deeper: Meaning
Typography, spacing, wording, focus, empty states, errors, transitions and micro-interactions form a single experience. No detail compensates on its own for a poor solution, but their accumulation can either reinforce or erode trust.
Consequence
Explanation
Less frequent states are also designed and verified: empty, loading, error, success, and recovery. Language, hierarchy, and behavior are maintained throughout the journey, and the experience is reviewed with real content before approval.
Go deeper: Consequence
Design and verify normal, empty, loading, error, success and recovery states.
Keep language, hierarchy and behavior consistent throughout the flow.
Review the product at actual size and with realistic content before approving it.
Example
A shared link opens exactly the cited section and in the selected language. No one notices when it works; everyone notices when it fails.
Counterexample
Treating errors, loading, small screens, or keyboard use as finishing touches to be addressed later.
Sign of non-compliance. A button changes its label between steps, an error appears far from its field, and focus is lost after saving. Each defect is minor; together they break continuity.
Decision test
These questions look for details that contradict the logic of the rest.
Do the details reinforce the same logic, or do they contradict expectations?
What happens in the less frequent states?
Does the product feel deliberately built, or assembled from parts?
Source
Manifesto core v2.1, section PRINCIPLE 8 · P08. Download the core