Designing Beyond the Interface

Just finished reading Figma's piece on AI and design. Got me thinking.

The real shift happening right now isn't the tools. It's how we're starting to think about the work itself.

Figma's take is interesting. They're not positioning AI as some shiny feature or existential threat. They're calling it infrastructure. Which honestly feels right. It's changing how we think, how we make things, how we work with each other. But the part that stuck with me: it's changing who gets to build stuff. That's the bigger deal.

The walls between designer, developer, and strategist are getting thinner. Roles we used to guard like territory are bleeding into each other. Design isn't just interfaces anymore. It's systems that learn. Things that adapt. And if that's true, then our job isn't just making things look clear. It's making sure the thinking is clear. Judgment matters more than execution now.

What's coming isn't design on autopilot. It's design with more room to breathe. AI handles the repetitive stuff. Layouts. Patterns. Nudging pixels around. Fine. But it doesn't know why something should exist. It doesn't understand story. It has no taste. That part is still ours.

The advantage isn't knowing keyboard shortcuts anymore. It's knowing how to show a machine what good actually looks like.

So the question changes. Not how do we go faster. How do we think better. Not what can I make. What should actually exist.

The next chapter of design isn't on the screen. It's in all the invisible decisions that happen before anything gets built. AI is taking over the how. Which means everything now rides on the why.