Everyone’s got an opinion about AI and design these days. Seems like every other LinkedIn post is either doomsaying (“designers are obsolete!”) or eye-rolling dismissal (“it’s just a toy”).
Neither take is particularly helpful, to be honest.
What’s actually happening? It’s more mundane than either camp wants to admit. The way designers work is shifting—not because AI is suddenly replacing us, but because the traditional shape of the role has been creaking under pressure for years. AI just…speeds things up. Makes the cracks more obvious.
The designers who’ll do well? Those who adjust now, not when the ship’s already halfway underwater.
Design systems aren’t optional anymore
If your team still treats design systems as a “nice to have” or something you’ll get to “when there’s time,” you’re setting yourself up for pain.
Modern workflows—especially AI-assisted ones—don’t work without structure. They need components, tokens, variables, patterns. The better your system, the more AI can actually help. The worse it is, the more AI just highlights how broken things are.
When your system is solid, AI becomes a multiplier. Need to explore variations? Done in minutes. Want to test different layouts? Easy. And consistency? It’s baked in because the rules already exist.
But when your system is a mess—half-documented, inconsistent naming, components that sort of work but not really—AI can’t save you. If a machine can’t interpret your component library reliably, that’s not the AI’s fault. That’s your system telling you it’s not as robust as you thought.
Designers are getting closer to code
The line between design and engineering has been blurring for ages. Design systems sit right in the middle of that convergence.
Components don’t ultimately live in Figma files. They live in code. And as systems get tighter, designers naturally end up caring more about implementation. Not because we’re becoming engineers (we’re not), but because the gap between “how it should look” and “how it actually works” is where everything breaks.
You don’t need to be a developer. But you do need to understand:
- How components are structured
- How tokens get consumed
- How behaviours are defined
- How changes ripple through a system
When designs can’t be cleanly built, it’s usually not an engineering problem. It’s a mismatch between visual intent and technical reality.
More teams are creating roles that sit in this space—design engineers, systems designers, whatever you want to call them. The title varies, but the pattern doesn’t: owning not just how things look, but how they function, scale, and integrate.
Designers who get comfortable here? They reduce friction. Fewer miscommunications. Fewer late-stage surprises. Less rework.
AI works within systems, not around them
The most useful thing AI does for design today isn’t blue-sky creativity. It’s systemic leverage.
AI is good at:
- Evaluating component usage
- Spotting inconsistencies
- Supporting token migrations
- Flagging when design and code have drifted
In large teams, this is genuinely valuable. Divergence between intent and implementation isn’t an edge case—it’s the default. Things drift. Components get duplicated. Styles multiply. What started clean becomes chaotic.
Getting earlier visibility into that drift? That changes everything. You catch problems while they’re still cheap to fix, not after they’ve metastasized across half the product.
Operational overhead has always been the real enemy
Designers spend absurd amounts of time on stuff that isn’t actually design.
File management. Documentation. Triage. Cleanup. Asset wrangling. Necessary? Sure. High-value? Rarely.
When AI can absorb more of that mechanical crud, it’s not a threat. It’s a correction.
The time you get back? That’s when the real design work happens:
- Framing problems properly
- Running research and validation
- Iterating on solutions
- Collaborating across teams
- Refining systems
AI handling the busywork isn’t automation displacing designers. It’s automation removing the stuff that was diluting our impact anyway.
What actually matters for tomorrow’s designer
This isn’t about tools. It’s about mindset.
The designer who thrives going forward is:
- Systems-first, not screen-first
- Focused onreuse, not one-off output
- Comfortable near code, not isolated from it
- Thinking long-term coherence, not just immediate deliverables
Judgement still matters. Empathy still matters. What changes is where you apply them.
Designers increasingly operate at the intersection of systems, constraints, and scale. AI reinforces that direction by rewarding structure, clarity, and consistency.
For teams building products today, this isn’t hypothetical. These dynamics are already reshaping workflows, responsibilities, and what “good design” looks like.
The future isn’t approaching.
It’s already baked into how effective teams work right now.
So if you want to work like the designer of tomorrow? Start adjusting today. Not next quarter. Not when your manager tells you. Today.
Because the shift isn’t coming. It’s already here.