The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude)
TL;DR
Jenny Wen, Head of Design at Claude, explains how AI coding tools have killed the traditional design process, forcing designers to shift from creating perfect mocks to supporting rapid engineering execution and setting shorter-term directional vision.
🔄 The End of Traditional Design 3 insights
The gospel process is dead
The sequential research-to-mock workflow that designers treated as sacred cannot survive in an era where engineers ship features instantly using AI agents.
Vision horizons collapsed
Strategic design has shifted from producing beautiful 2-10 year roadmap decks to creating functional 3-6 month prototypes that point teams in the right direction.
Perfect mocks are obsolete
Designers no longer have the luxury of time to create polished mockups when engineers can spin up seven cloud instances and ship working code immediately.
⚡ The New Operating Model 3 insights
Execution over documentation
Modern designers spend 60-70% less time mocking, instead focusing on helping engineers execute and connecting disparate shipped features into cohesive experiences.
Two-track design work
The profession is stratifying into supporting immediate implementation (unblocking engineers) and creating short-term directional vision via working prototypes.
Let them cook
Rather than blocking releases for design perfection, designers must allow rapid iteration and guide the process asynchronously while engineers build.
🤖 AI's Impact on Practice 3 insights
Non-determinism requires shipping
AI's unpredictable outputs cannot be fully prototyped in static mocks, necessitating real-code experimentation with actual models to discover use cases.
Designers become builders
Tools like Claude Code enable designers to handle last-mile implementation and polish directly in code rather than relying on engineering handoffs.
Industry resistance persists
While AI companies embrace this shift, many designers invested in traditional processes push back against abandoning discovery and research phases.
🎯 Future of Design Talent 2 insights
Judgment over craft
As implementation becomes automated, designer value shifts to taste, accountability for decisions, and determining what actually matters to build.
Continuous learning imperative
At Anthropic, designers must constantly track internal research developments, model capabilities, and cross-team prototypes via Slack to remain effective.
Bottom Line
Designers must abandon rigid design processes and embrace a hybrid role of rapid execution support and short-term vision setting, using AI coding tools to ship directly while focusing human judgment on what to build and why.
More from Lenny's Podcast
View all
Building the most AI-pilled engineering team in the world | Fiona Fung (Anthropic)
Fiona Fung, leader of Claude Code and Co-work at Anthropic, reveals how her engineers now ship 8x more code than in 2021, fundamentally shifting the engineering bottleneck from writing to verification and requiring new AI-native management techniques to maintain quality at scale.
The hidden pattern behind successful products | Mark Pincus (FarmVille, Words with Friends, & more)
Mark Pincus shares his "Proven Better New" framework for building hit consumer products, arguing that founders should copy proven elements, make incremental improvements that 10/10 users love, and treat truly novel features as high-risk experiments—contrary to the instinct to prioritize innovation over familiarity.
Father of the iPod and iPhone on building taste, judgment, and creativity in the AI era
Tony Fadell shares lessons from building the iPod and iPhone, arguing that creating category-defining products requires resisting AI-driven cognitive surrender, embracing opinion-based decision-making for 1.0 versions, and micromanaging critical details while maintaining ruthless focus on customer pain points and storytelling.
A rational conversation on where AI is actually going | Benedict Evans
AI represents a transformative shift comparable to the internet or mobile, but we remain in its infancy (like 1997), with adoption spread unevenly across industries and the real challenge being integration and judgment rather than mere task automation.