2026-06-04

When Building Is Free, Taste Becomes the Only Moat — and It's Trainable

Let’s start with something that’s already happening: “building things” is becoming nearly free.

Someone with zero coding background can describe what they want and have AI produce a working app. Professionals move at speeds that would have seemed absurd two years ago. The barrier to entry has collapsed. And that raises a new question — if anyone can build, why is yours better?

Speed is no longer the differentiator

For a long time, being fast was a genuine competitive edge. Ship faster, iterate faster, win.

That advantage is evaporating. Because AI has made everyone faster. When every team can spin up five versions in an afternoon, speed stops being scarce. It becomes the floor, not the ceiling.

So what’s the ceiling? The 2026 industry consensus is strikingly unified: judgment and taste. When the cost of building approaches zero, the responsibility for choosing well shoots up. The design world has a phrase for it: taste is the new bottleneck.

What taste actually is

Taste isn’t mysticism. It’s the ability to see the thin line between “good” and “good enough.”

AI can help you write code. AI can help you use tools. But “does this work, is this actually good” — that call is yours alone. That’s taste. And taste is what’s worth the most right now.

The counterintuitive part: taste is trainable

Most people assume taste is innate — you either have it or you don’t.

Wrong. Taste is a learnable skill, built through volume of exposure + deliberate analysis + sustained output.

This is exactly what Ira Glass was describing in his famous observation: your taste develops ahead of your ability. Early on, what you produce doesn’t match what you can recognize as good. That gap is painful. And the only thing that closes it isn’t waiting for inspiration — it’s volume. Make enough things, and your ability catches up to your taste.

How PMs actually train taste (the concrete practice)

  1. Build a high-signal reference library. Every day, collect one or two things you think are genuinely excellent — an interface, a line of copy, an interaction, a product decision. Don’t critique it yet. Just save it.
  2. Dissect one thing a day. Pick one. Ask yourself: why does this work? How is the information hierarchy organized? How does it handle state — loading, empty, error? What’s the rhythm of the copy? Translate “this feels good” into “here’s specifically why” — that translation is where taste actually grows.
  3. Ship constantly and invite criticism. Volume shrinks the gap. Sitting on your work and never showing it keeps your taste frozen in place.
  4. Use AI as a taste gym. Ask AI to give you five versions at once. You pick, you critique, you say “this one’s wrong — it should be more like…” Before, training taste meant waiting for a project to land in your lap. Now you can compare dozens of real options in a single afternoon. AI doesn’t replace your judgment. It multiplies the number of times per day you exercise it — by a factor of a hundred.

Where doaipm comes in

This is exactly what doaipm has been saying all along: AI has handed off the doing. What it’s left with you is choosing well and getting it right.

When anyone can build, what you build and how good it is become the only distinction. The stronger AI gets, the more your taste is worth — and it’s something you can train.

Put your taste to work on real things. Start at the method center and the 言出法随 (“Speak it, AI builds it”) playbook.


Further reading

Discussion

No login needed. Be kind.
Loading…