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.
At a glance
WHAT IT’S REALLY ABOUT
AI-driven engineering speed is reshaping designers into decision-makers and partners
- Jenny argues the canonical “discover → diverge/converge → pixel-perfect mocks” design process is effectively dead, primarily because AI tooling lets engineers ship and iterate at unprecedented speed.
- Design work is splitting into two modes: (1) hands-on implementation support—pairing with engineers to polish what’s being built in real time—and (2) setting near-term direction through prototypes and lightweight visions (3–6 months), not multi-year decks.
- In AI products, you can’t pre-design every state due to non-determinism; shipping earlier and learning from real usage becomes the path to better design, with trust built through fast iteration and responsiveness.
- Wen shares how she hires for this new era (block-shaped generalists, deep specialists, and “craft new grads”), why managers should return to IC work, and how to spot “illegible” frontier ideas worth making legible through UX and storytelling.
IDEAS WORTH REMEMBERING
5 ideasClassic, linear design rituals can’t keep up with AI-accelerated shipping.
When engineers can rapidly prototype with multiple agents, designers can’t be the bottleneck producing perfect mocks. The role shifts from gatekeeping to guiding and integrating what’s shipping in real time.
Design is splitting into two jobs: execution support and near-term direction-setting.
One track is partnering with engineers to refine and connect fast-moving implementation; the other is providing a coherent “north star” that’s now often a 3–6 month prototype rather than a 2–10 year vision deck.
In AI UX, you must test with real users because you can’t mock all states.
Model outputs are non-deterministic, so exhaustive UI state design is unrealistic. Better outcomes come from shipping a workable version, observing behavior, and iterating based on real data and emergent use cases.
Quality and brand can be preserved by shipping early—if you visibly iterate.
Wen distinguishes “research preview” launches (known rough edges) from brand-damaging launches where nothing improves. Trust comes from responsiveness: acknowledging flaws, shipping fixes quickly, and demonstrating momentum.
Designers’ time allocation is flipping from mocks to collaboration and implementation.
Wen’s personal shift: mocking/prototyping dropped from ~60–70% to ~30–40%, replaced by ~30–40% engineer pairing plus a new slice of direct code-based polish and shipping.
WORDS WORTH SAVING
5 quotesThis design process that designers have been taught…we sort of treat it as gospel…that’s basically dead.
— Jenny Wen
You as a designer actually…do not have the time to make these beautiful mocks anymore.
— Jenny Wen
A few years ago, 60 to 70% of it was mocking and prototyping, but now…I feel the mocking up part of it is 30 to 40%.
— Jenny Wen
At the end of the day, someone has to decide what is actually going to get built and what actually matters. Someone still needs to be accountable for the decision.
— Jenny Wen
The way that you really lose trust…is if you release it early and then nothing ever happens.
— Jenny Wen
High quality AI-generated summary created from speaker-labeled transcript.
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