Taste is not subjective

The subjective escape hatch

The scene repeats in every design critique. Someone presents work. Another person pushes back. A third person says "well, it is subjective." The conversation dies. The most senior person's preference wins. This is not a process. It is a power dynamic dressed up as open-mindedness.

Pattern recognition, not magic

Herbert Simon's research on expert intuition describes what taste actually is: pattern recognition trained on volume. Chess grandmasters do not calculate every move from first principles. They recognize board states from thousands of previous games and respond with the move that matches the pattern. Designers with taste do the same. They have seen enough interfaces, studied enough failures, internalized enough cause-and-effect that their gut response is a compressed database lookup, not a mystical feeling.

The missing vocabulary

The statement "I cannot explain why this is wrong" does not mean "it cannot be explained." It means the vocabulary is missing. That is a fixable problem. Cause-and-effect chains make implicit knowledge explicit. This typeface choice creates a formal register. Formal register creates distance. Distance undermines the warmth this onboarding flow needs. That chain is articulable, debatable, and testable. The gut feeling was the starting point, not the argument.

Scoring quality together

Katie Dill built a quality scoring system at Stripe that evaluates design across three dimensions: utility, usability, and craft. At Safe, I adapted this into what we call the DQI — Design Quality Index — scored across five dimensions: Clarity, Focus, Effort, Feedback and Safety, Aesthetic and Emotional Quality. The point is not the specific dimensions. The point is that a shared vocabulary replaces individual talent as the quality bar. When the team can name why something works or fails, critique becomes productive. When they cannot, every critique is a power struggle with extra steps.

Subtraction, not addition

Dieter Rams distilled it decades ago: good design is as little design as possible. Taste is subtraction, not addition. The tasteful choice is almost always the removal, not the embellishment. Knowing what to remove and how fast you can get there — that is the operational definition.

Name it or lose the argument

If you cannot write the cause-and-effect chain, you cannot defend the decision. If the team does not share the vocabulary, every critique is a power struggle.