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

2026-02-26 · Source: Lenny's Newsletter · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering, Project & Product Management · Depth: Intermediate, extended

Summary

Jenny Wen, Head of Design for Claude Co-Work at Anthropic, discusses the radical transformation of the traditional design process, which she declares "dead" in the age of AI. She notes that engineering's rapid development cycles, driven by tools like Claude Code and the use of multiple AI agents, are forcing designers to adapt. The role has shifted from 60-70% mocking and prototyping to 30-40%, with a greater emphasis on supporting implementation, execution, and providing a three-to-six-month vision rather than long-term plans. Designers are now more involved in "last mile" polishing and prototyping in code, working closely with engineers. Wen emphasizes the importance of adaptability, continuous learning, and a willingness to let go of rigid processes, while still valuing human judgment in deciding what to build and ensuring product quality through rapid iteration and user feedback.

Key takeaway

For design leaders and managers navigating the AI era, your teams must embrace a more fluid, execution-focused design process. Encourage designers to develop technical skills, prototype directly in code, and collaborate closely with engineers to guide rapid iteration. Your leadership should prioritize fostering psychological safety alongside high standards, enabling teams to adapt quickly and maintain product quality through continuous feedback and improvement, rather than rigid, long-term planning.

Key insights

AI-driven engineering velocity is forcing a fundamental shift in the design process, prioritizing execution support and shorter-term vision.

Principles

• Traditional design processes are obsolete.
• Engineering changes drive design evolution.
• Build trust through speed and iteration.

Method

Designers must shift from extensive mocking to supporting implementation, prototyping in code, and providing short-term (3-6 month) vision, while continuously iterating based on real user data and feedback.

In practice

• Integrate coding tools into design workflow.
• Focus on "last mile" polish with engineers.
• Utilize AI for introspection and rubric generation.

Topics

• AI Design Process
• AI Development Tools
• Evolving Designer Role
• Design Leadership

Best for: CTO, VP of Engineering/Data, Director of AI/ML, Product Designer, AI Engineer, Software Engineer

Related on AIssential

• Podcast: Beyond Code: How Engineers Need to Evolve in the AI Era — Engineers must evolve beyond pure coding to embrace AI, business context, and human empathy for sustained value.
• I Can’t Keep Up With AI. That’s Not the Problem I Thought It Was. — The rapid pace of AI tool development renders traditional deep skill mastery obsolete for designers.
• The Builder-PM Manifesto — Product management is fundamentally changing as AI's "harness" operating layer shifts scaling laws from models to team-level strategic framing.
• Why the Way AI Feels Is as Important as How It Works - with Carsten Wierwille of HTEC — Late design in enterprise AI is a strategic mistake, leading to adoption failures despite technical functionality.
• AI Isn’t Replacing Programmers — It’s Compressing Teams — AI increases individual developer leverage, compressing team sizes and shifting focus from code execution to judgment and problem-solving.
• You’re not late to AI—you’re early to Frontier Transformation — AI transformation demands redesigning work within specific functions, driven by leadership sponsorship and an adaptive culture, not merely tool adoption.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Lenny's Newsletter.