On building quiet interfaces

The best features I have shipped were the ones nobody noticed. They made the slow thing fast, or the imprecise thing precise, and then stayed out of the way.

A quiet interface does not announce itself. It does not throw confetti when a form saves. It saves the form, shows a small steady mark, and lets you carry on with the work you actually came to do.

This is harder than it sounds. Loud interfaces are easy: add an animation, add a banner, add a badge. Quiet ones require you to decide what genuinely matters and to trust the user with everything else.

I have started measuring my own work by how little explanation it needs. If a screen needs a tooltip to be understood, that is usually a sign the screen is wrong, not that the tooltip is missing.

Quiet is not the same as plain. A quiet interface can still have a strong point of view. It just expresses that view through rhythm, type, and restraint rather than through noise.