Daniel Birch

When production is easy, design shapes what’s built.

Design Architects. Thinking about the role of design in an AI world. Leading a small design team in a business that is constantly evolving - acquiring, restructuring, and pushing to be as lean as possible - inevitably leads to one thing: looking to technology for quick wins.

Right now, that means AI.

A lot of the conversation around AI in design is focused on speed. Faster outputs. Faster delivery. Less effort to produce the same artefacts. And alongside that, there’s a growing concern - designers becoming “prompt monkeys”, spending their time trying to get one tool to talk to another just to keep up. That may well become part of the job. But it’s not the part that’s most interesting - or most important.

Production is changing. The core of design isn’t. If you look at design in digital products and services, much of the focus over the past few years has been on tools, outputs, and delivery. How quickly we can move from idea to shipped feature. AI is already reshaping that.

It can generate interfaces, accelerate research, support analysis, and help produce working prototypes faster than before. In small teams especially - where designers are often outnumbered 5, 10, even 30 to one by engineers - this kind of efficiency matters.

And it’s working. We’re already seeing improvements in how quickly we can move. But the output was never the most valuable part of design. The real value has always been in:

  • Understanding the problem

  • Framing the right questions

  • Navigating constraints

  • Aligning people

That hasn’t changed.

From designers to architects. When you step back, the role of a designer starts to look less like a producer of artefacts and more like something else entirely. An architect. Not in the sense of software or systems - but in the original sense: Someone who takes all constraints into account and designs a solution that can actually be built.

That’s the shift.

AI is very good at producing solutions. What it lacks is context. It doesn’t know:

  • Who is in the room

  • What stakeholders really think (not just what they say)

  • Which constraints are undocumented

  • Where the real tension in a problem lies

It can follow guidelines, use design systems, and apply best practices. But it doesn’t understand the messy, human, often ambiguous reality that sits around every real project.

That context still needs to be created.

Where this shows up. This shift is already visible in how we work. Meetings, for example, have changed. What used to be rooms, whiteboards, and fast-moving conversations are now digital spaces, remote collaboration, and distributed teams. The tools are different, but the outcome is the same - we’re trying to make sense of problems and move forward.

The difference now is that production is no longer the bottleneck. So the focus moves upstream.

Workshops.
Framing sessions.
Facilitation.
Bringing people together to align on what we’re actually trying to solve.

Laying out problems clearly.
Exploring different directions.
Helping teams navigate ambiguity.

This is where senior designers are already spending more of their time - and where their value becomes more obvious.

A note on team shape. Working in a small team, everyone tends to do everything. There’s no luxury of specialisation - delivery always comes first. But something interesting happens as teams grow. In our case, with around 15 designers, we’ve been able to carve out space for specialisms - research, design systems, design thinking. Roughly a third of the team is now focused beyond pure delivery.

That wasn’t a deliberate strategy at first, but looking back, it’s had a big impact. It’s allowed us to:

  • Move design further upstream

  • Influence strategy, not just execution

  • Spend more time understanding customers and shaping direction

AI has amplified this. It helps us process research faster, identify gaps, and build confidence in our decisions. But it’s the shift in focus - not the tools that’s made the difference. It suggests there’s a threshold where design can move from reacting to shaping.

The real role of the design architect. This is where the idea of the design architect comes in. Someone who:

  • Frames the problem clearly

  • Understands where there is flexibility and where there isn’t

  • Brings the right people together

  • Guides the team through ambiguity

  • Builds alignment and momentum

  • Shapes the path forward

AI can support many of the individual tasks involved in a project. But it doesn’t orchestrate. It doesn’t adapt in real time to changing opinions, shifting priorities, or incomplete information. It doesn’t take a team on a journey from uncertainty to clarity.

That’s still a human role.

The opportunity. AI will continue to improve production. It will make many parts of the design process faster, easier, and more accessible. But in doing so, it exposes where the real value lies. Not in the artefacts we produce - but in how we think, how we frame problems, and how we bring others with us.

The designers who thrive won’t be the ones who are best at generating outputs. They’ll be the ones who:

  • Create clarity where there isn’t any

  • Provide context that tools can’t access

  • Align people around a shared direction

  • Shape solutions that work in the real world

In other words, they become architects.

And that feels like a much more interesting place for design to be.

This is a footer, but by now you are bored, so nothing more…

© danielbirch 2026