The Taste Gap

Ira Glass once described something every creator knows but few can articulate: the gap between your taste and your ability. You got into this work because you have good taste. You can recognize great work when you see it. But the things you make — at least early on — don't meet that standard. And that gap is painful.

Most people talk about this in the context of creative beginners. But the taste gap never fully closes. It just changes shape. The more experienced you get, the more refined your eye becomes — and the more you notice the distance between the vision in your head and the reality on the screen.

Taste as competitive advantage

In a world flooded with tools that make it trivially easy to ship, taste is the last remaining moat. Anyone can spin up a landing page. Anyone can launch a product. The raw act of building has been democratized to the point of commoditization. What hasn't been democratized is the ability to look at something and know — in your gut — that it's not right yet.

Taste is what makes you obsess over the easing curve on a button animation when everyone else has already moved on to the next ticket. It's what makes you rewrite a headline seven times because six of them were fine — and fine is the enemy of great. Taste is the voice that whispers "something is off" before you can name what it is.

The teams that build things people love — Linear, Stripe, Arc, Apple — don't have a speed advantage. They have a taste advantage. They're willing to sit with discomfort longer. They'll delay shipping not because they're slow, but because they can see something the rest of us can't yet.

The trap of "good enough"

Here's the uncomfortable truth: most teams optimize for velocity. Ship fast. Learn fast. Iterate. There's wisdom in that — but it's incomplete wisdom. Speed without taste produces a lot of mediocre things, quickly. You end up with a product that technically works, that checks every box on the spec, but that no one falls in love with.

"Good enough" is the most dangerous phrase in product development. Not because the product fails — it won't. It'll work. People will use it. Metrics might even look healthy for a while. But "good enough" slowly erodes the soul of what you're building. Each compromise compounds. Each "we'll fix it later" becomes permanent. And one day you look up and realize you've built something that's functionally complete but spiritually hollow.

Developing taste

Taste isn't innate. It's cultivated. It develops the same way a sommelier's palate develops — through exposure, attention, and deliberate comparison. You build taste by studying the best work in your field, by understanding why something works, not just that it does.

A few practices that have sharpened mine: saving everything that catches my eye — not to copy, but to build a library of references that trains my subconscious. Asking "what would I change?" about every product I use. Spending time in adjacent disciplines — architecture, typography, film editing — because the principles of craft are universal. And most importantly, shipping relentlessly. You can't develop taste in theory. You develop it by making things, cringing at them, and making them again.

Closing the gap

The gap between your taste and your ability will always exist. That's not a bug — it's the engine. The discomfort of seeing the distance between what you imagined and what you built is what drives you forward. The moment you stop feeling that tension is the moment you've stopped growing.

So don't try to eliminate the taste gap. Learn to use it. Let it be the compass that tells you where to push harder, where to spend the extra hour, where to say "not yet" when everyone else is saying "ship it." The world doesn't need more things that work. It needs more things that sing.