Lenny's PodcastJenny Wen, Claude head of design: Why design process is dead
Why non-deterministic AI states can't be cleanly pre-mocked anymore: Anthropic shipped Claude Cowork in 10 days by pairing with engineers, not mocks.
CHAPTERS
Why the classic “trust the process” design playbook is breaking
Jenny argues that the canonical diverge/converge, research-heavy design process designers were taught is no longer realistic. The speed of AI-enabled engineering has collapsed timelines and made fully polished mocks less central to shipping.
A new split: execution support vs. short-horizon vision setting
Design work is becoming stratified into two modes: helping teams execute quickly, and creating direction/vision. Vision work is still crucial, but it’s compressed to weeks or months and often expressed as prototypes instead of decks.
How widespread is the shift (and why there’s backlash)
Jenny sees the change spreading beyond AI labs: PMs and teams everywhere are spinning prototypes with tools like Claude Code and v0. But many designers push back because careers and identities were built around the old process and rituals.
Shipping-first design for nondeterministic AI products
Jenny believes faster execution and learning in production can produce better AI products, because AI behaviors are hard to predict in static mocks. For LLM features, you often need real models and real users to discover actual use cases.
A day in the life at Anthropic: keeping up is part of the job
At a frontier AI company, a significant part of Jenny’s day is understanding what’s happening across research, labs, and product teams. Internal prototypes, debates, and rapid iteration create a “constant catching up” dynamic that informs design decisions.
What designers actually do now: the new pie chart of time
Jenny describes a major rebalance: less time in mock/prototype creation and much more time pairing with engineers and implementing polish directly. Traditional research and prototyping still exist, but the toolset and proportions have changed.
Jenny’s AI stack and why Figma still matters
Jenny is all-in on the Claude ecosystem—Chat, Cowork, and Claude Code (often inside VS Code). She still relies on Figma for parallel exploration and micro-iterations that are harder to do in linear code-based workflows.
Keeping quality and trust when everything ships faster
Jenny reframes quality management as a function of transparency and iteration. Shipping early is acceptable (especially as “research preview”) if users see rapid improvement, responsiveness, and follow-through—otherwise trust erodes.
Where humans stay valuable as AI gets better at taste and judgment
Jenny expects AI to improve meaningfully in design taste and judgment, challenging human exceptionalism. However, humans still need to decide what matters, resolve disagreements, and remain accountable for what ships.
The future UI of AI: chat isn’t going away, but UI will expand
Jenny expects a hybrid future: conversational interfaces remain powerful for flexibility, while interactive UI elements accelerate common tasks. She anticipates more UIs being generated by models rather than hand-built each time.
IC vs. management: why Jenny returned to hands-on work (and what managers should do)
Jenny moved from design leadership back to IC work to stay close to rapidly changing tools and workflows. She believes managers remain valuable, but the future manager must provide direction and understand the work deeply—not just do pure people management.
Claude Cowork’s design evolution: many prototypes, then a fast push to ship
Cowork wasn’t invented in 10 days; it was refined over many explorations, then rapidly packaged for external release. The team shipped what was already working internally to get real signal, then committed to iterating in public.
Hiring in the new era: resilience + three designer archetypes
Jenny prioritizes adaptability and tool openness, then looks for three profiles: strong “block-shaped” generalists, deep specialists, and exceptional early-career craft talent. She also advises new grads to build real things and find maker communities.
Team culture and leadership: “low leverage” work, roasting, and legibility scouting
Jenny argues some “low leverage” manager behaviors are actually high leverage when done by leaders—like deep product dogfooding or thoughtful cultural gestures. She also views playful roasting as a signal of psychological safety, and uses a “legibility” lens to spot frontier ideas worth shaping into products.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome