The Fastest Way to Get Good Taste

Most people treat taste as a mysterious gift, something you either have or you don't, like perfect pitch or a good singing voice. But taste is closer to a muscle than a talent. It grows through repetition, feedback, and the willingness to make things that embarrass you six months later. The problem is that iteration feels slow. You want to skip to the part where your work looks like the vision in your head, and that gap between vision and execution is exactly where taste gets built. Every time you finish something and cringe at it, you're calibrating. You're learning what "off" feels like, and that feeling is the raw material of taste. So the first step is accepting that the cringe is not failure; it's the mechanism.

Speed matters more than polish when you're developing taste, because the number of complete cycles you run through is what drives improvement. A finished draft, a shipped prototype, a published post—these give you something concrete to react to. An unfinished masterpiece in your head gives you nothing. The trick is to shorten the loop: make smaller things, make them faster, and put them in front of reality sooner. Write a 300-word sketch instead of agonizing over a 3,000-word essay. Build the ugly version first. Show it to one honest person. Then iterate. Each loop teaches you something about your own standards and about what actually lands. Over time, you stop guessing and start knowing. That knowing is taste.

There's a cultural bias against iteration because we celebrate the polished final product and ignore the messy path that produced it. We see the chef's plated dish, not the burnt sauces and over-salted soups. We read the novelist's elegant sentence, not the four rejected drafts. This bias makes us think that good taste arrives fully formed, and that if we're not immediately good, we're not meant to be doing the thing. That's backwards. The people with the sharpest taste are usually the ones who have made the most bad work and paid attention to why it was bad. They've developed a library of mistakes in their nervous system. When they see a new problem, they recognize patterns faster because they've seen so many variations. Taste is compressed experience.

But iteration alone isn't enough. You also need discrimination—the ability to tell the difference between something that's genuinely better and something that's merely different, or worse, something that's just more expensive. This is where feedback becomes crucial, but not all feedback. Praise feels good but teaches little. Blanket criticism is demoralizing and often wrong. What you want is specific, reasoned response: why did this choice work or not work? What was the effect? That kind of feedback helps you connect cause and effect, which is how you build reliable intuition. If you can't find a mentor or a peer group, you can generate this yourself by comparing your work to work you admire. Ask: what did they do that I didn't? What did I do that they wouldn't? The comparison is not about self-flagellation; it's about extraction. You're mining the principles behind the surface.

In a hurry, the temptation is to skip the comparison and jump straight to copying. Copying can be useful as an exercise, but it doesn't build taste because you're not making decisions—you're just following instructions. Taste requires choice under uncertainty. You have to pick a color, a word, a feature, and then live with the consequences. That's why constraints are so helpful. When you limit your options, you force yourself to prioritize, and prioritization is where taste lives. A photographer with one lens learns to see differently than one with a bag full of glass. A writer with a strict word count learns to cut the fat. The constraint makes the feedback loop tighter because you can see the trade-offs clearly. So if you're in a hurry, don't remove constraints; add them.

One practical way to accelerate is to keep a taste journal. Not a diary of feelings, but a log of specific decisions and their outcomes. "I chose this headline because it was concrete; it got twice the clicks of the abstract one." "I used this shade of blue; it made the interface feel colder than I wanted." Over weeks, patterns emerge. You start to see your own biases and blind spots. You also start to see which of your instincts are reliable and which need recalibration. This journal becomes a personal database of cause and effect, and it's far more useful than a list of abstract rules because it's grounded in your own work. The act of writing it down also forces you to articulate why, which deepens the learning.

Finally, taste is not static. What was good ten years ago may feel dated now, and that's not a failure of taste—it's a sign that culture moves. The people with enduring taste are the ones who keep iterating, who stay curious, who don't confuse their current preferences with universal truths. They hold their standards firmly but their specific judgments loosely. That balance lets them adapt without losing their core. So if you're in a hurry, the answer isn't to find a shortcut around iteration. The answer is to iterate faster, more deliberately, and with better feedback. Make more bad things. Pay attention. The taste will come.