Designers are Restless

The best ones I’ve known, anyway. They walk into a room, sense what’s absent, and are compelled to become that thing—researcher, storyteller, systems thinker, the person asking the uncomfortable question. Great PMs and engineers can sense this too—but they can succeed without it. For designers, this sensitivity IS the job—moving between contexts, filling the gaps, keeping the human at the center.

For decades the industry narrowed that into something more manageable. “The UI person.” “The pixel polisher.” or worse—“The empathy hire.” Orgs needed a job description so they wrote one. But the value was always broader than the role. Designers at their best aren’t specialists or generalists—they’re translators. Between what the business is building and what the person on the other end actually experiences.

AI is already generating interfaces, writing copy, synthesizing research. The craft we’ve spent years mastering is being commoditized. That mastery wasn’t trivial—it was how we earned credibility, how the feeling became something a team could see. Mourning that is natural. Staying there is a mistake.

Because the thing that’s NOT being automated is harder to name but you know it when you feel it. It’s the tightness in your chest when something looks right but isn’t. It’s the question you can’t stop asking even after the meeting ends. It’s caring about the person using your product—not as a user story, but as an actual human who deserves better than what just got shipped.

That’s not a vague feeling. It’s information. The body registers what’s wrong before the mind can articulate it. But the feeling is where it starts, not where it ends. The raw signal—something is wrong here, and it matters—is detection. What it becomes after you’ve been wrong enough times to know the difference between ‘this bothers me’ and ‘this will fail someone’—that’s discernment. One is a sense you were born with or learned to cultivate. The other took time. We’ve spent careers training ourselves to feel friction that other people walk right past. Questioning what everyone agreed upon too quickly. Preventing those things that would’ve shipped broken and hurt someone.

We talk about “delight” and “feeling” while the room is talking about retention, conversion and risk. We’ve been bad at speaking the language that makes the business listen. But maybe the problem isn’t that feelings are soft. Maybe it’s that we’ve been apologizing for the most rigorous thing we do.

And if we follow that feeling further, perhaps the sensitivity and the proof are really the same practice.

The designer who stays bothered long enough to trace why something feels wrong is already doing the analytical work. They just never learned to connect it to data—and most orgs don’t make that easy—so the feeling stays unread, and leadership never sees what it was worth.

So maybe the shift isn’t about becoming more business-minded. Maybe it’s about owning the feeling all the way to the proof instead of hoping others will do that work.

If anything, AI has removed the distraction—the tools are changing, but the craft of shaping how something feels was never about the tools.

What’s left is the dreaming and scheming. Articulating the vision for what it does, how it feels, and why people will care. And when a team needs to believe, prototypes practically write themselves.

Tools change. The restlessness doesn’t.