Every time I open LinkedIn, my feed is filled with designers arguing that everything is generic now. The AI does the work, so the role of the designer is to be the tastemaker, the gatekeeper. The designer makes sure the artifact carries their taste, and somehow that is the value the designer now holds in the process.
I think that’s a little self-aggrandizing.
Taste is never the point of design.
If you think it is, you’re placing the design role on a pedestal, and AI is already knocking it off.
Whose taste are we talking about?
Back in 2012, I wrote that design lives at the intersection of people, problem and constraint. The designer’s taste isn’t on that list.
If you call yourself the tastemaker, you’ve put your own eye at the center of the work, where the customer belongs. Design’s role is to make the object, the experience, desirable to the customer, and to increase that desire. Do that well and you create a customer: the customer gets what they came for, and the company earns its return.
We do it in many ways, and bringing taste to the experience and the artifact is one of them. But taste is always in service of something else: elevating customer delight, reducing friction, and positioning in the customer’s mind how your product or service lines up with their goal and your goal as a company.
Taste isn’t the gatekeeper to value. It’s an element of it.
Some of those designers mean judgment when they say taste, not polish. Fair enough. But your judgment is only worth something when it creates a customer.
Didn’t taste win customers?
Not in my experience. When I was the UX manager for Gordon Food Service’s B2B ordering platform, my team had to grow the number of customer accounts ordering online by 20% every quarter. We hit it three quarters in a row. (I told the whole story in Twenty Percent a Quarter.)
Those screens had to provide the functionality the customer was trying to use. That’s the very practical need. They also had to communicate the appropriate amount of trust, so the customer felt confident that the screens and utilities they were using were trustworthy. Design has the responsibility to not only facilitate a function, but to establish a presence with the user. That’s a quality of the artifact. It served the customer, and every account that came online counted toward Gordon’s target.
Your job as a designer is to make sure all of those dots connect in a really powerful way. You have to know what resonates with your customer, in service of the business’s goals and the customer’s goals. That is what easily gets lost when designers think it’s just about their taste, or their special ability to see the material world or the digital experience.
What happens when beauty is free?
AI is already making beautiful things customers love, and it doesn’t need a designer to do it. Whether it ever becomes a tastemaker doesn’t matter; the premise was false either way. When anyone can generate a beautiful screen, your competitors have one too. Beauty becomes table stakes.
I wrote in October that when building gets cheap, deciding gets expensive. What’s still scarce is knowing which customer you’re creating, what they’re trying to get done, and how you create value for them and for your company.
A lot of designers are hiding behind taste right now. I think it’s going to be a pretty big awakening when they realize that their ability to create something beautiful is something anyone can now do.
So the next time you defend a design choice, don’t start with how it looks. Start with what stands between your customer and the thing they came to do, and what removing it is worth to them and to your company.
Bring your taste. Then hold it to the same test as everything else you put on the screen: does it help create a customer and earn your company a return? If it doesn’t, it was never the point.






