Jenny Wen
It's not just designers who are feeling like, "Oh yeah, we have to keep up with engineers." I think even engineers are like, "How do we keep up with ourselves?", covering product design, AI product work, and engineering tradeoffs.
Episode
Jenny Wen
Summary
Jenny Wen, head of design for Claude Cowork at Anthropic and former design director at Figma, describes how the design profession is being structurally reorganized by AI-accelerated engineering. The old design process — diverge, converge, make beautiful mocks, hand off — is essentially dead for fast-moving teams. Designers are being forced into two new modes: real-time execution partner and short-horizon vision setter prototyping directional bets 3–6 months out.
Key Takeaways
The design time pie chart has fundamentally flipped: what used to be 60–70% mocking and prototyping is now 30–40%, with freed-up time going to real-time engineering collaboration.
Design visions should now be 3–6 months out, not 2–5 years. A working prototype that points the team in a direction is more valuable than a beautifully produced vision deck.
When hiring designers, seek three archetypes: 'block-shaped' strong generalists, deep T-shaped specialists, and 'craft new grads' with no baked-in process baggage.
Trust is built through speed, not perfection. Shipping a labeled 'research preview' with known rough edges is brand-building if the team visibly responds to feedback.
Use the 'legibility framework': hunt for prototypes where there is unexplained internal energy — people excited but unable to articulate why — and dive in before it becomes obvious.
Notable Quotes
“What is in my AI stack? Well, we work at Anthropic, so we're going deep on the Claude stack. I'm using, obviously, chats, Claude Chat, but increasingly more and more Claude Cowork. I've basically shifted all of my chat use cases over to Cowork, because I've been finding that it sort of is better at these longer running tasks. And most of the things I was asking Claude for are these longer running tasks.”
“Whenever I do work with engineers on projects, and it's more on a consulting basis, I do just try to explain why I'm thinking a way that I'm thinking, to help them extract principles. As opposed to me just being like, "No, I don't think this should go here." It's like, "No, I think we should have a button here because not everybody realizes you can prompt this." And here's an example where it comes from research and whatnot. So I also just try to point engineers to our design system and stuff like that in code, because right now Claude is writing a lot of the code and it's not always picking up stuff in the design system and whatnot. So as much as I can equip them with stuff that they can use in the future without me, if that's helpful.”
“... Yeah, getting criticized. You're like, oh yeah, it is hard to get critical feedback and to hear it, and to hear it on such a regular basis, because that's the thing you have to do as a designer, is it's a pretty vulnerable exercise to share work and present it with your team, and then also just get a lot of critical feedback and take that all the time. Yeah.”