AI Can't Design

AI can't design.

There. I said it. And yes, I'm the guy who's been posting about how AI completely changed how I work as a designer.

The reactions to my recent posts have been interesting. Lots of enthusiasm, but also a surprising amount of pushback. People asking why anyone would hire a designer anymore. Some even acting like I'm cheerfully handing over my own job.

Here's what's actually happening: the conversation around AI is exposing something that was always true but easy to ignore.

Most people never understood what design actually is.

Design isn't making things look good. It's not picking colors or pushing pixels. It's understanding people, context, and constraints, and making decisions that solve real problems. AI can generate visuals. It cannot design.

I worked on a device for use in restaurant kitchens. The chef couldn't use the interface properly because his fingers were covered in tomato sauce. No amount of AI-generated UI is going to solve that. Someone had to understand that context, think through it, and design around it. That's the job.

And the same goes for companies who now think they can skip the designer altogether. "We'll just use AI." Sure. Go ahead. You'll ship something. It'll look fine. And then slowly, in the onboarding drop-off, in the support tickets, in the customer who just can't figure out step three, you'll start to notice. Design debt doesn't show up on day one. It shows up six months later when nobody can tell you why users keep churning.

The critical reactions, by the way? Almost entirely from other designers.

I get it. This stuff is scary. But if your job was always "make visuals," then yeah, that part is under pressure. If your job was understanding people and translating that into something that actually works, you're fine. Better than fine, actually.

AI doesn't replace that thinking. It just means I spend less time on the parts that were never really design anyway.