"When machines can generate “good-enough” UI in seconds, the value of designers shifts. It’s no longer about how fast you can mock something up. It’s about taste. Judgment. The ability to know what’s worth building, and what will actually move the needle."
Source: Design at Intercom
This quote from Thom Rimmer, Sr. Director of Design at Intercom has been bouncing around in my head all week—and for good reason. It perfectly captures the inflection point we’re at in our craft.
Design has never moved faster—but not everyone’s noticed
In my last post, The New Shape of Design Work, I explained that we’ve hit a turning point. AI, design systems, and better tools mean most designers can move fast. The craft is no longer the bottleneck it once was.
But here’s the paradox:
Some teams still treat design like it is.
I’ve heard leaders ask:
“Do we really need to ‘design’ this?”
“Can’t we just add on top of what we’ve already got?”
“Is a designer even needed on this [project/team]?”
In orgs where design is still seen as polish—not leverage—its value gets questioned.
This isn’t a tooling issue. It’s a perception gap.
And if we don’t close it, design risks being sidelined in the very moment when it should be leading.
What AI can’t automate (yet)
While tools can generate layouts or mimic visual patterns in seconds, what they can’t replicate is the kind of thinking that lives at the intersection of systems, users, and strategic tradeoffs.
Designers still make the calls that matter:
“This is a problem worth solving.”
“This component solves five things at once—if we do it right.”
“This touchpoint deserves love—because it’s where trust is won or lost.”
“This concept helps users build stronger habits. That’s the real win.”
That kind of discernment isn’t just craft—it’s judgment. It’s strategic product thinking.
And that’s where our value now lies.
The Design Work That Doesn’t Look Like Design
One of the traps we fall into is equating “design” with creating interfaces. But some of the most valuable design work doesn’t involve pixels at all and often takes place before you ever open Figma.
Designers are often the first to ask:
“Are we solving the right problem?”
“Have we talked to any real users yet?”
“Is this even the job to be done?”
These are strategic questions. And asking them early saves teams months of wasted execution.
We bring invisible strengths to the table:
User research – Running discovery interviews, finding patterns, spotting signals, and testing assumptions early before they become hard costs.
Framing problems – Synthesizing chaos into direction. Creating clarity where ambiguity stalls progress.
Facilitating alignment – Organizing workshops, story mapping, or reframing debates through prototypes and shared language.
Reframing constraints – Helping teams think laterally, not just linearly. Designers do this naturally because we navigate systems and stories.
None of this requires opening Figma—but it’s all deeply design.
It’s time we treat these strengths not as extras, but as core contributions to how we build. Not as “soft skills,” but as leverage.
What I’m seeing—and asking—from the ground
The most effective designers I’ve worked with aren’t just executing—they’re thinking like PMs, testing like engineers, and staying involved long past the handoff.
Here are the tensions and conversations I’m exploring within my teams:
“Can designers flex PM strengths when it matters?”
Maybe it’s not about being the PM—but about knowing when to step into product thinking. Framing problems. Sequencing bets. Influencing scope. Designers with strong product instincts don’t replace PMs—they raise the floor of product strategy across the team.
“Can designers prototype in production—not just Figma?”
Not to replace engineers or even ship production-ready code, but to increase learning surface area and shrink the loop between idea and outcome. Whether through code, low-code tools, or sandboxed environments, designers who can test + build real experiences in real software can unlock higher quality deliverables.
“Should we kill the concept of ‘handoffs’?”
Handoffs create friction, latency and introduce unintentional human error. The most effective teams I’ve seen don’t pass work between silos—they treat their work as an end-to-end function, from shaping the bet to iterating live.
Ownership beats documentation.
I think so. In fact, I think it’s already happening.
🔀 Design x Engineering
The future of design isn’t handoff—it’s integration. Designers who can move from Figma into GitHub—or even just think in terms of the underlying systems—aren’t just faster. They’re more credible.
Designers today need to think beyond Figma and into the systems where their work lives. It’s not about writing code—but about understanding how performance, responsiveness, and system constraints shape the user experience.
Designers who collaborate with engineers from day one stop designing for ideal states and start designing for real systems.
Collaborate upstream, not post-handoff
Consider tradeoffs before committing to high-cost polish
Use Storybook, flags, or sandboxed flows to prototype real interactions
Fluency, not mastery, is what earns trust and unlocks better design decisions.
📍 Design x PM
Designers are often closest to the user problem—and that gives them an edge in product shaping.
The best Designers don’t wait for projects or tickets to be assigned to them. They frame the problem, define success, and propose scope that balances ambition with risk. It’s not about taking over PM roles—it’s about partnering to build clarity earlier and reduce waste later.
Strong designers don’t just respond to briefs. They help write them.
🎯 Design x Impact
Usability is the baseline. Today, design needs to be measured by outcomes: did the flow convert? Did behaviour shift? Did the work actually matter?
This means staying involved post-launch—watching the data, running tests, iterating when things don’t land.
Designers who embrace impact thinking move from “did this feel good?” to “did this work?”
Good design delights. Great design delivers.
But let’s not pretend this shift is frictionless
While it feels like a natural evolution—designers flexing PM skills, building in code, owning outcomes—it’s not for everyone. And even when it is, it only works if the org is ready to support it.
That means:
PMs who see this as partnership, not threat.
Engineers who invite design upstream, not just into QA.
Leaders who reward impact, not just titles.
Otherwise, you’re not enabling growth—you’re just stretching designers thin in cultures that aren’t ready for them to show up differently.
Where does that leave us?
If AI makes execution cheap and fast, and teams still question design’s role—then the real work isn’t just what we build.
It’s how we show up.
Designers who lean into judgment, strategy, systems, and outcomes are rewriting the role in real time. They’re not waiting to be invited upstream. They’re shaping the roadmap, informing the bet, and staying through the outcome.
But we can’t do this alone.
We need orgs that are willing to evolve with us—to build teams where:
✅ Designers are empowered to influence the roadmap
✅ Design is measured by impact, not just aesthetics
✅ Judgment, fluency, and ownership are valued over handoffs and artifacts
Design isn’t the bottleneck. It’s the unlock—if we let it be.
👇 I’d love to hear from you:
What’s one way your team is evolving how design shows up—or one place where it’s still stuck?
The New Shape of Design Work
About 10 years ago, a manager of mine would often joke that most designers were just one step away from becoming PMs. Back then, I saw it as a quirky observation. Now? I think they were onto something.