What Does "Taste" in Design Actually Mean?

The Word Everyone Is Using

Taste. Designers keep bringing it up - in job posts, portfolio reviews, hiring conversations. But most people use the word without fully unpacking it.

Here is a working definition: taste is the ability to recognize what is good, appropriate, and effective - and what isn't. It is judgment, not skill. It is the difference between knowing how to build something and knowing what should be built.

Why It Matters More Now

This conversation is happening because design is changing fast.

Twenty years ago, knowing the software was an edge. Today, anyone can open Figma or Canva. AI can generate UI screens, logos, wireframes, and entire design systems. The technical floor has dropped dramatically.

What AI hasn't figured out is judgment. It can produce options. It cannot tell you which one is right, what to remove, what fits the audience, or what aligns with the brand. That decision is taste - and someone still has to make it.

Taste vs. Decision-Making

These two overlap, but they're not the same thing.

A product manager, an engineer, and a designer all make decisions. The question is whether those decisions consistently lead to outcomes that are effective, elegant, and appropriate. When people talk about "great product taste," they usually mean something more specific - understanding what matters, recognizing quality, knowing when to simplify, anticipating user reactions, and balancing trade-offs elegantly.

Taste is often the explanation for why certain people repeatedly make good decisions in ambiguous situations, where there's no clear right answer and no data to lean on.

What It Actually Looks Like

Taste in practice looks less like creation and more like subtraction.

A designer with strong taste might reject a feature because it adds clutter. They'll remove three buttons and keep one. They'll push back on a trendy visual style because it doesn't fit the audience. They'll spend an hour adjusting spacing that users will never consciously notice - but will feel.

It's restraint. It's knowing when to stop.

Where It Comes From

Taste isn't a personality trait. It's developed.

It comes from consuming a lot of great work - studying Apple products, Stripe, Linear, Arc, but also architecture, film, and typography. It comes from asking better questions: why does this work? What would happen if this element were removed? Why is this version better than that one?

Rick Rubin describes it well in The Creative Act - taste is the ability to recognize excellence before you're capable of creating it yourself. Most designers have experienced this. You can see that something is wrong before you can fully articulate or fix it. The execution catches up over time.

Beyond Visual Taste

For UX designers, taste isn't just about how something looks.

There's product taste - knowing which problems are worth solving. Interaction taste - choosing the simpler flow when both options technically work. Content taste - writing less. Research taste - knowing which questions actually matter.

In product and UX, "taste" is often shorthand for a cluster of things experienced teams recognize but rarely write down - product judgment, design judgment, user empathy, pattern recognition, a sense of quality, and the ability to make trade-offs well.

The Shift

As AI takes on more of the production work in design, the value of a designer shifts - from making artifacts to making decisions.

Taste is what that decision-making capability is increasingly being called. It's not new. But it's becoming the thing that actually differentiates designers who have it from those who don't.