December 11, 2025·5 min read
Latency is a design decision
Speed is not an engineering metric you inherit — it is a feature you choose, budget for, and defend in review like any other.
Ask a team about their visual standards and you will get a straight answer: the type scale, the spacing grid, the exact gray of a hairline. Ask about their latency standards and you will usually get a shrug and a dashboard nobody looks at. Speed, somehow, is treated as weather — something the product has, rather than something the team decided.
But every hundred milliseconds is a decision. It was decided when someone added the third analytics script, when the modal fetched its options on open instead of on hover, when the list re-rendered because equality was by reference. Nobody chose slowness; it was assembled from small unexamined choices, which is exactly how anything mediocre gets built.
Budgets, not vibes
The fix is the same one design already uses: a standard, written down, enforced in review. A latency budget is a sentence anyone can check. Interactions acknowledge input within 100 ms. Navigation paints something meaningful within a second. Nothing shifts after it is visible. When a pull request spends more than the budget allows, that is a design regression — same word, same weight, same conversation as a broken layout.
Perceived speed is honest speed
Some latency cannot be deleted, and that is where design earns its keep. The skeleton that matches the real layout. The optimistic update that assumes success and quietly reconciles. The transition that overlaps the wait instead of stacking a spinner on top of it. These are not tricks; the user's experience of time is the only clock that ships.
- Acknowledge every input instantly, even when the work takes longer.
- Load what the user will probably want next, while they decide.
- Never let the page move under a reader who already started reading.
Fast products feel respectful; that is the whole secret. The tool answers when spoken to, and the person using it gets to stay in their own thought instead of waiting in yours. That feeling has to be chosen on purpose — put it in the spec, give it a number, and defend it like you defend the type scale.