There's a version of this essay where I tell you to keep exploring new tools. That version is safe and mostly useless.
Designers already do that. We try the new app, the new workflow, the new AI thing that promises to remove friction. For a few days it feels like progress. Everything is faster, cleaner, more exciting.
Then the work looks the same.
The tool was never the problem
Tools don't make decisions. They give you options. They remove friction. They make certain things easier and certain things harder.
But they don't decide what matters. They don't know when the hierarchy is wrong. They don't know when an interface has too much confidence and not enough clarity.
Give two designers the same tool and you'll get two completely different outcomes. The difference isn't the tool. It's judgment.
The trap
The trap is mistaking fluency for taste. Learning shortcuts feels productive. Moving faster feels like improvement. But speed only helps when you're already moving in the right direction.
Most bad work doesn't happen because the tool wasn't powerful enough. It happens because nobody stopped to ask whether the decision was any good.
A better tool can make you faster. It can't make you more deliberate.
On taste
Taste is not decoration. It's not a moodboard or a personal preference. It's the ability to notice when something feels off, and to understand why.
Spacing, hierarchy, rhythm, restraint. Knowing what to remove. Knowing when the obvious solution is too obvious. Knowing when something is technically correct but still wrong.
That's the part no tool gives you.
Amplification
Good tools amplify what is already there.
If you have good taste, they help you move with less resistance. If you don't, they just let you produce bad decisions at a higher resolution.
This is why AI-generated interfaces often feel close but empty. They can imitate structure, but they don't care about intent. They can produce a layout, but they don't know what the layout is trying to say.
Tools don't fix bad decisions. They scale them.
What matters now
Execution is getting cheaper. Code is getting faster. Interfaces are getting easier to generate.
That's good. But it also means the thing that used to separate people — the ability to make something — is becoming less rare.
The harder part is deciding what should exist at all, and what form it deserves to take.
Use better tools. Learn them deeply. Let them disappear.
Just don't expect them to think for you.
The bottleneck isn't your toolset. It's your taste.