The Enterprise Designer

There's a pattern hiding in plain sight inside design's title history. We've been so busy debating methodologies and tools that we missed the signal the titles were sending the whole time. It's not about the designer. It was never about the designer. It was always about the thing being designed.

Look at the progression. Graphic Designer — designing graphics. Web Designer — designing the web. UI Designer — designing the interface. UX Designer — designing the experience. Product Designer — designing the product. Each title marked a moment when a new material entered the picture. A new surface, a new scope, a new thing that needed to be designed — and couldn't be designed well by the people who came before, because they didn't have the right fluency.

Graphic designers were masters of visual communication. But the web wasn't a poster. It was an information space. You needed people who understood library science, human factors, cognitive load — people who could think about how humans navigate information, not just how they read it. Then software became the material. Apps weren't just websites. They had state, behavior, constraints, affordances. Design had to go deeper than the surface. Product design was born from the need to think in the material — to understand software well enough to design with it, not just on top of it.

Every transition followed the same logic: new material enters, existing design practice is insufficient, a new role crystallizes around the fluency required.

Which brings us to now.

For the last twenty years, there's been a gap that product design couldn't close. Not for lack of talent — for lack of reach. The gap lived between products. In the seams between systems. In the handoff from one department's software to another's. The customer who had to re-explain their problem when they got transferred. The employee who toggled between four applications to complete one task. The data that lived in one system but was needed in another.

I've spent most of my career watching designers bang their heads against this gap. We'd map the end-to-end journey. We'd identify every pain point in the seam between systems. We'd present beautiful service blueprints showing exactly where the experience broke. And then we'd hit the same wall: the systems are different. The teams are different. The budgets are different. The technology stacks don't talk to each other. The designer's role — for all its evolution — still ended at the edge of the product.

What AI actually changes isn't what most of the noise suggests. There's a lot of talk about faster prototyping, generative UI, automated handoffs. That's real, but it's not the point. The deeper change is this: for the first time, the seam is designable. When experience can be orchestrated across systems through intelligent agents — when natural language can bridge SAP and Salesforce and your customer portal and your service team's workflow — the gap between products is no longer a fixed constraint. It's a design surface.

And this changes what "the thing being designed" actually is. It's not the interface. It's not the product. It's not even the end-to-end service journey — though that's closer. It's the enterprise itself. The whole organism. Every touchpoint, every handoff, every moment where a human being encounters the organization's intent — whether through a screen, a conversation with an agent, an automated decision, or a human employee whose workflow was shaped by systems a designer never touched.

This is what I mean by "enterprise designer." Not a new job title to put on LinkedIn. A recognition that design's material has expanded again — and this time, the material is the organization. The person who can hold the full picture of how an enterprise behaves as a human experience, and who has the fluency to shape that behavior through AI-enabled systems, is practicing a form of design that didn't exist five years ago.

It requires everything that came before. You still need visual communication skills. You still need to understand information architecture, interaction patterns, software behavior. You still need product thinking. But you also need something that the previous roles never required: the ability to design across organizational boundaries, to think in systems that span departments and technologies, and to shape AI agent behavior in ways that feel coherent from the outside even when the inside is a mess of legacy systems and competing priorities.

There's another shift happening alongside this scope expansion, and it's just as significant. For most of design's history, the relationship between designer and engineer had a fundamental asymmetry: designers specified, engineers built. The designer produced artifacts — wireframes, prototypes, specs, redlines — and handed them over. What got built was always a translation of the designer's intent, filtered through someone else's execution. This created entire practices oriented around influencing the build rather than doing it. Over-the-shoulder art direction. Dev-ready design. Design systems as a way of constraining engineer decisions.

That constraint is collapsing. Not because designers are becoming engineers. But because the material is becoming responsive to design intent directly. When you can instantiate a functional, interactive prototype by describing what you want — when the gap between "this is what it should feel like" and "this is what it does" shrinks to minutes — the designer's relationship to the material changes fundamentally.

I've seen this firsthand at Slalom. Designers who never wrote code are now building working applications, creating feature branches, collaborating with engineers in the same material. The best of them aren't just producing faster outputs — they're developing a new kind of fluency where design judgment and technical capability merge. They're not designers who learned to prompt AI tools faster. They're the ones who recognized that their years of cross-disciplinary thinking — the ability to hold a user's mental model, a system's behavior, and a business's constraints simultaneously — is exactly the fluency required to work with generative, agentic material.

The designers who are struggling are the ones waiting for the tools to stabilize before adapting. They're treating this like a tool transition — like the shift from Photoshop to Sketch, or Sketch to Figma. It's not. It's a scope transition. The tools are just the signal.

For design leaders, this means the team you're building looks different. You're not hiring five specialists and hoping they collaborate. You're looking for people with genuine range — who can think in systems and craft a moment, who understand enterprise architecture and care deeply about a single user's frustration, who can build alongside an engineer without losing their design perspective.

For organizations, this means design is no longer a service function that decorates products other people have decided to build. Design is the practice that determines whether your enterprise, as a human experience, actually works. That's a strategic function. It belongs at the center of product and technology decisions, not downstream of them.

And for designers — the ones reading this, wondering whether their skills are becoming obsolete — here's what I want you to hear: everything you've learned still matters. The empathy. The systems thinking. The craft. The ability to hold complexity and find the essential thing. That's not being automated away. That's becoming more valuable, because for the first time, it can actually operate at the scale it always deserved.

You were always supposed to design the whole thing. Now you can.

The progression isn't over. It just got a lot more interesting.