Designers writing code. Developers designing UIs. What happens when AI blurs the boundaries?
Today, Google announced Stitch, a design agent to help developers generate UI. Just last week, Figma introduced Make, a new capability allowing designers to build code-based prototypes.
Two tools. One friction point:
Who owns what part of the delivery in an AI-accelerated workflow?
For me, this isn’t about a turf war.
It’s about redefining collaboration in a way that respects and amplifies the expertise of each role.
Designers bring deep knowledge of user journeys, interaction patterns, and visual systems. Giving them the ability to generate handover-ready code with AI doesn’t undermine engineering; it streamlines intent.
Developers, in turn, are best placed to refine that code, ensuring performance, security, and system integration are rock solid. That’s not just implementation, it’s craft.
But for this new frontier to work, we need to redesign the delivery process itself, not just add AI into existing handoffs and hope for the best.
This is an opportunity to:
• Replace friction with fluency
• Replace over-the-wall handoffs with shared workspaces
• Reimagine delivery as a co-authored experience, not a linear relay
The tools are evolving fast. Our workflows should, too.
How are you and your teams starting to reimagine the delivery process with AI in the mix?
What’s your take? Are we ready to redraw the map?
Leave a Reply