What Humans Do Best While AI Designs and Codes
- Published on
Let's talk about this wild new world where AI is diving headfirst into design and development. You've probably seen it yourself: tools that generate components, suggest layouts, even create chunks of design and code that feel almost ready to ship. It's exciting, right? Especially in design systems, where everything is so structured and rule-based, AI fits like a glove. Many professionals are even afraid to lose their jobs. But they won't: AI speeds things up tremendously, yet it still needs us humans to steer the ship. Not just to babysit it, but to do the parts that make the whole system thrive in ways AI simply can't touch yet.
Our team has been knee-deep in design systems for years, architecting them across companies and watching how AI changes the game. The great thing is that while AI handles the heavy lifting on creation, we get to focus on the strategic, human-centered and business-focused work that turns a good system into a powerhouse. In this article, you can see what that looks like, and the basis of this material is evolution we guided in real design system teams. By the end, you'll see a clear path forward—one that blends AI's power with our irreplaceable strengths.

1. Re-think Processes, Not Just Tools
Imagine dropping AI into your current workflow without a second thought. It might crank out code faster, sure, but if your processes are built for a pre-AI era, things start to crack. In fact, when introducing AI, you need to reshape everything from handoffs to quality checks.
The key is gathering your team for a dedicated workshop to map it all out. Start by questioning the basics:
- Should your designers start generating prototypes in code or you stay in Figma?
- Should your developers design with the help of AI?
- Do you ship AI-generated code to production?
- What tools fit this new flow, and how do we stay sharp on them?
- Do those two-week sprints still make sense, or can we loop faster with AI in the mix?
And don't forget governance: AI might suggest changes to your design system, but who decides what sticks?
As an outcome for such a workshop, you'll have the new process documented and the check-ins which are set to refine it. When you get this right, AI becomes a true accelerator, not a Band-Aid on old habits.
2. Do Ongoing User Research on the System Itself
Think of your design system as a product in its own right, with designers, engineers and AI agents (!) as its primary users. AI can crunch usage data or spot patterns in logs, but it can't sit down with someone, observe their frustrations, or uncover those unspoken needs that only come out in conversation.
That's where we humans shine. Treat your team like users: run interviews to hear about adoption hurdles, set up diary studies for real-time feedback, or observe how they navigate the system in their daily work. From there, translate what you learn into tangible updates. Maybe deprecating a confusing component or creating better guides.
Sure, AI can help analyze transcripts or suggest survey questions, but guiding the research, building empathy, and deciding what to act on? That's human territory. It ensures your components aren't just technically sound but truly solve the problems people face every day.
3. Decide What Exactly to Do Next
AI is brilliant at building what's asked of it. If you give a specific request to create flawless buttons, responsive grids, even full documentation sites, AI will do. But ask it to decide which components your product truly needs next, or when to pivot the system's strategy? That's where it falls short. It excels at filling in the blanks but struggles with the big-picture vision.
We provide that north star. By connecting the design system's growth to business goals, market shifts, and your roadmap, we chart the course. This means setting scaling principles, defining consistency benchmarks, and establishing accessibility floors that guide every decision. Map out focus areas so that you prioritize layers that need investment and sunset outdated patterns before they drag you down.
Humans optimize beyond the local: we see the strategic path, weighing what to build, deprecate, or reinvent. Even feeding AI your company strategy won't yield the nuanced mapping we bring. It's our vision that keeps the system aligned and forward-moving.
4. Cross-Team Translation and Change Management
New tools and methods mean nothing if teams don't embrace them. AI integrations fizzle when no one bridged the gap and no one explains not just how, but why it changes things for the better.
We step in as coaches, creating playbooks with prompt libraries and escalation paths, hosting office hours or paired sessions to build skills hands-on. Celebrate those early wins with before-and-after stories to spark confidence. And to prove it's working, track real signals like time-to-adopt or component usage rates, feeding them back to refine priorities.
This human touch smooths the transition, turning skepticism into shared momentum. Communicate those victories up the chain, and you secure the buy-in needed to keep investing.
If you can't measure it, scaling becomes guesswork. AI's output is impressive, but without outcomes, it's just activity. We instrument the system to track adoption impact:
— PR cycle times
- design debt reduction
- time-to-market for ideas
Then, monitor health like variant sprawl or change frequency.
With such metrics you can we demonstrate the system's value, turn data into evidence and make it a base for your decisions.
5. Own AI Practices
AI outputs need gates to maintain standards. We define them: clear token taxonomies focused on intent, standardized variants that sync Figma to code, and prompt-ready specs that guide AI reliably.
Set acceptance criteria for accessibility, performance, and more, then codify checks like visual diffs or lints. Design publish policies that cover branching and approvals for both design and code. This ensures AI enhances without compromising.
Document the "why" behind choices, this will give AI agents meaningful guardrails. Once and forever, your design system becomes a single truth source, now for AI too.
You can build canonical prompt recipes for system elements and, depending on tools, craft custom commands for efficiency.
As with any new tools of method, invest time to exploring. Which model gives you better result? What tools fit most economically? Which of them are easier to adopt? It's ongoing learning that keeps us ahead.
Facilitate training on workflows, prompt engineering, and AI agents usage. Encourage experimentation over hesitation. We educate on best practices, foster collaboration across disciplines, and nurture a learning culture that sustains the system.
As AI reshapes design and code, our role evolves into something powerful: architects of vision, guardians of quality, and bridges for adoption. By rethinking processes, driving research, owning direction, managing change, and mastering AI practices, we ensure design systems don't just keep up, they lead. It's a clear path that blends human insight with AI scale, creating systems that truly transform how teams build. What's your next move in this era?