Designers are anxious. Leaders can fix that.

The Problem

Designers are anxious, and most leaders are missing it

In the last year, almost every designer I have talked to has said some version of the same thing. The employed ones think their role is shrinking. The unemployed ones think the role they trained for no longer exists. Both are reading the same headlines, watching the same demos, and hearing the same 10x goals from leadership.

The fear is not irrational. Tools like Cursor, Lovable, v0, and Figma Make are compressing weeks of work into hours. Companies are openly asking teams to ship more with fewer people. Craft, on its own, is no longer a defense.

What leaders often miss is that anxiety does not just hurt morale. It quietly slows the team down. Anxious designers default to safer work. They stop proposing ambitious ideas. They protect scope instead of expanding it. The very thing leadership wants more of, leverage, becomes harder to get.

How I Saw It

In meetings, 1:1s, and on ADPList

I saw it first in staff meetings. Designers who used to push back went quiet. A PM would say "can we just have Cursor do this," and nobody asked what "this" meant. The room shrank.

I heard it loudest on ADPList. Every week, designers from companies I had never worked at said the same three sentences. "I do not know if I am still relevant." "My manager keeps saying AI-native and I do not know what that means for me." "I have applied to fifty jobs and heard nothing." This was not a few people. It was the field.

The pattern was unmistakable. Leaders everywhere were repeating the same line in all-hands: "10x the team," "3x the output," "be AI-native by Q2." Bigger goals, shorter timelines, almost no specifics. No tools funded. No training time protected. No definition of what 10x actually meant for a designer's week.

What did come with specifics was the layoffs. Same quarter, often the same email thread. "Be 10x more productive with AI" landed next to "we are cutting the team by 20 percent." Designers were not imagining the threat. They were doing the math their leaders were already doing out loud.

Both sides are partially right and entirely talking past each other. Leaders are reacting to real market pressure. Designers are reacting to the absence of a credible plan. The gap between the message and the support is where the anxiety lives.

What Did Not Work

The usual playbook fell flat

We tried the obvious things first. Newsletters about new tools. Recorded talks from internal experts. Optional courses. A Slack channel full of demos. People watched, nodded, and went back to feeling exactly the same. Passive learning does not move anxiety, because anxiety is about agency, not information.

What Worked

Make the new normal learnable, on real work

The shift happened when we stopped talking about AI and started building with it together, in public, on actual projects. Three things, in this order, did most of the work.

Example 1, The Setup

Fix the environment before you teach the tool

Most designers were stuck long before they ever wrote a prompt. They did not have GitHub access. Their terminal was not set up. Claude Code and Cursor were installed but never opened. Storybook and the design system were not wired into either. Every "try this tool" moment turned into an hour of setup and a quiet retreat.

So we set aside dedicated time, with engineers in the room, to get every designer's environment in working order. GitHub access, terminal basics, Claude Code and Cursor configured, Storybook and the design system connected to both. Then we shipped a default starter template so nobody had to think about scaffolding. Clone, open Cursor or Claude Code, prototype against real components in minutes.

Removing that first hour of friction was the single biggest reason adoption stuck. Everything that followed worked because the runway was already clear.

Example 2, Hackathons

Pair designers with engineers, not in parallel tracks

Once the setup was solved, we ran joint hack days. Mixed pairs of designers and engineers, one real problem, ship something live by end of day. Engineers had been quietly using AI tools for months. Designers, in many cases, had been waiting for permission. Putting them in the same room collapsed that gap in a day.

Designers watched engineers prompt their way to a working backend in fifteen minutes. Engineers watched designers turn a half-baked Figma file into a clickable prototype before lunch. Both groups left with a sharper sense of what the other actually does, and what AI can and cannot do for it.

After each session we shared, openly, how much time the tools had saved on real work. Research synthesis went from days to hours. Early-stage exploration went from a week to an afternoon. PRDs that used to bounce between PM and design for a week were drafted together in a single working block.

When the whole team can see where the tools save time, AI stops feeling like a layoff signal and starts feeling like a raise in leverage.

Example 3, Research

Hey Marvin plus Claude, as a company-wide second brain

One of the most popular sessions we ran was on research. We taught the team how to use Hey Marvin and then connected its MCP server to Claude. In a single working block, designers and researchers uploaded user testing videos, sales call recordings, and old strategy decks into Marvin, and queried it all directly from Claude.

Instead of digging through Drive folders for a quote from a study six months ago, a designer could ask Claude, "what did SMB users say about onboarding friction last quarter," and pull verbatim customer quotes in seconds. PMs started doing the same for competitive decks. Researchers stopped being the bottleneck for every insight request.

The bigger unlock was cultural. Marvin plus Claude became a second brain for the whole company, with insights from research, sales, and strategy living in one place that anyone could query in plain language. Hours saved every week, yes. More importantly, the value of research became visible to people who had never opened a transcript before.

The Path

Give the anxiety a finish line

Alongside the hackathons, I published a structured six-week reskilling path. Three tracks: product thinking, business fluency, and AI-native building. It is the same guide I now share publicly as the Age of Builders.

The point is not to turn every designer into a full-stack engineer. It is to give them a credible, finite, sequenced way to close the gap, so the anxiety has somewhere to go. People can tolerate a hard climb. They cannot tolerate a fog.

If You Lead A Team

Five moves for this quarter

AI is not going to slow down. Goals are not going to shrink. What leaders can change is whether their team faces this moment alone or together. That choice, more than any tool, is what separates the orgs that thrive in the next two years from the ones that quietly bleed talent.