The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude)

The old step-by-step design gospel is over. We don’t have time for pristine mocks anymore, and our job leans far more toward moving ideas into reality with engineering.

Today’s guest is Jenny Wen, formerly head of design for Claude and now leading design for Claude Cowork, with past stops at Figma, Dropbox, Square, and Shopify. You’re living at the front edge of where design is going, so how is the process changing with AI?

Engineering shifted first and forced design to adapt, so I split our work into two tracks: support execution as teams ship rapidly, and set a near‑term direction that aligns efforts. Long, cinematic visions turned into three-to-six-month prototypes that point the way.

So the change isn’t a choice; engineering speed makes it necessary, and your value becomes guidance, cohesion, and helping great ideas land.

Exactly, and it’s empowering. I’m pairing in code, handling last‑mile polish, and building working prototypes instead of waiting on handoffs, even as design tooling lags behind.

Is this shift everywhere or just at bleeding‑edge AI companies?

It’s spreading. My talk on letting go of the old process resonated widely, though there’s pushback from folks invested in ceremony. Meanwhile PMs and designers are prototyping with AI too.

Does shipping fast actually make better products now?

With non‑deterministic models, you learn by building. Real data and real use unlock the truth faster than perfect clickable demos, because the best use cases often emerge in the wild.

What’s a day in the life at Anthropic like in the middle of this?

A lot of scanning internal research, prototypes, and debates so I can see what’s coming, then carving time to sketch the next few months, jamming with engineers, and finishing details directly in code. Slack is a goldmine.

Are you still doing research and mocks, and how did your time split change?

Yes, but the mix flipped. I used to spend most of my week mocking and prototyping; now that’s roughly a third to two‑fifths, with much more pairing and a real slice of implementation.

What’s in your stack, and where does Figma fit?

I live in Claude, increasingly Cowork for longer tasks, and Claude Code in VS Code or even via Slack for quick fixes. Figma stays essential for exploring many directions and dialing visual details, while code tools feel linear and commitment‑heavy.

How do you keep up and help engineers get better at design without trying to be a gate?

Explain the why so principles stick, point folks to the design system, and equip them to make strong choices next time. And yes, even engineers feel overwhelmed by how fast their agents move now.

How do you protect craft and trust while shipping constantly?

Ship valuable work as a research preview when needed, then show you’re listening by iterating fast in public. Speed builds trust only if you follow through.

Where do human brains still matter as AI takes more of the stack?

AI taste will improve, but priorities, tradeoffs, and accountability still sit with us for now. The hardest part of software isn’t typing code; it’s deciding what to build and why.

Do we move past chatbots and terminals as the interface to AI?

Expect a blend. Chat unlocks open‑ended flexibility, and models will spin up richer UI widgets for speed and clarity. Tactile UIs and conversation will coexist.

You stepped back into IC work; should other design managers do that?

It made me sharper fast. In a shifting craft, managers benefit from rotations so they can lead with empathy and currency; management still matters when it’s hands‑on, not just people ops.

What felt rusty when you returned to IC?

Taking frequent critique—presenting work and absorbing direct feedback—reminded me it’s a muscle.

Tell us how Cowork’s shape came together and why it “only took 10 days.”

We explored many forms, then pulled proven pieces into a focused, terminal‑like MVP and pushed hard for an external release. It wasn’t just 10 days; it was years of threads converging, and now we’re iterating the home into a shared to‑do between you and Claude.

Give us the one‑liner on Cowork.

Think of it as Claude with hands—it can grab your messy folder and turn it into something you can use.

How are you hiring differently in this new world?

I want resilient builders and three archetypes: unusually strong generalists, deep specialists, and craft‑obsessed new grads who learn fast and ship. New grads should build real things and find maker communities; seasoned folks should add coding tools to their kit.

Would you hire Claude as a designer today?

Not yet. It’s fine for first passes but doesn’t deliver distinctive taste.

You have a counterintuitive take on “low‑leverage” time for managers.

When leaders dogfood deeply, file bugs or PRs, and do small, caring acts, it signals standards and skin in the game. The “low‑leverage” work becomes high leverage because it’s you doing it.

And you encourage a culture where teammates can gently roast each other?

Light teasing is a sign of safety and comfort, not a mandate. Pair that psychological safety with a high bar, and people feel secure enough to do the best work of their careers.

Explain the legibility framework and how you use it.

I hunt for illegible ideas with unusual internal energy and translate them into clear stories and UX. An internal studio prototype inspired Cowork’s plans, to‑dos, contacts, and file views once we reframed it.

What a wild moment for design. Before we hit the lightning round, anything to leave listeners with?

Shoutout to our humble, resilient design team—we’re hiring across profiles. Find me on X at jenny_wen, and please send your Cowork and Claude feedback.

Lightning round time: books, shows, a product you love, a motto, and a favorite Cowork use case.

I recommend The Power Broker and Insomniac City. I loved a recent Norwegian film by the director of The Worst Person in the World and a high‑energy kitchen drama’s second season. Retro is my quiet photo app staple. My mantra is it is what it is. And Cowork shines at introspection—reading my notes to surface patterns and even draft a rubric for evaluating design craft.