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

The Changing Landscape of Design in the Age of AI

The Evolution of Design Roles

• Designers are moving away from traditional mockups, focusing more on execution and collaboration with engineers rather than just presenting designs.

• The design process has shifted from long-term visions (2 to 10 years) to shorter timelines (3 to 6 months), emphasizing rapid prototyping over polished presentations.

• There is a growing reliance on AI tools like Claude Code for idea generation, prompting discussions about the future value of human judgment in design decisions.

Insights from Jenny Wen

• Jenny Wen, former head of design for Claude and director at Figma, shares her perspective on the evolving role of designers amidst technological advancements.

• The conversation highlights how designers must adapt to changes in engineering practices and the increasing integration of AI into their workflows.

Impact of Engineering Changes

• As engineering roles evolve rapidly, design is compelled to adapt accordingly; however, it has not changed as significantly yet.

• Acknowledging that while engineering has undergone substantial transformation recently, design's evolution is still ongoing but necessary due to these shifts.

Future Considerations for Designers

• Designers need to consider what aspects will remain uniquely human in decision-making processes as AI continues to advance.

• When hiring designers today, there are three archetypes that stand out as particularly valuable in this changing landscape.

The Evolution of Design Processes in the Age of AI

The Decline of Traditional Design Processes

• The traditional design process, characterized by extensive research and a cycle of divergence and convergence, is becoming obsolete. Designers are encouraged to move away from rigid adherence to this "gospel" approach.

• The rise of AI technologies has accelerated this shift, as engineers can rapidly develop features without waiting for designers to finalize their concepts.

Stratification of Design Work

• Design work is increasingly stratified into two categories:

• Supporting implementation and execution, where engineers create features quickly.

• Establishing vision or direction, which remains crucial but is evolving due to rapid technological changes.

• Designers now have less time for creating detailed mockups; instead, they must adapt to a faster-paced environment where ideas can be quickly prototyped by engineers.

Shifting Focus on Vision Creation

• Creating long-term design visions (2-10 years out) is becoming impractical. Instead, designers focus on shorter-term visions (3-6 months), often represented through prototypes rather than polished presentations.

• This new approach emphasizes guiding teams towards cohesive goals amidst rapid feature development by engineers, ensuring efficiency in the design process.

Collaboration with Engineers

• Designers are shifting roles from gatekeepers to collaborators who facilitate engineering processes. They help ensure that all features align with a broader vision while allowing engineers the freedom to innovate.

• There isn't a unified call for change within the design community; rather, shifts are driven by advancements in engineering tools that enable quicker iterations and implementations.

Industry-Wide Implications

• The insights shared resonate across various sectors beyond just AI companies. Many organizations recognize the need to adapt their design processes due to emerging tools like cloud code that allow for rapid prototyping.

• Despite some backlash from professionals invested in traditional methods, there’s an acknowledgment that adapting design practices is essential as industry standards evolve.

Designing for AI: Insights from Anthropic

The Role of Discovery in Product Development

• There is a debate within the industry regarding the necessity of a stable design process, with some arguing that discovery and user research are essential while others believe in a more iterative approach.

• The discussion centers on whether spending time on discovery leads to better products compared to simply shipping "good enough" versions and iterating based on real user feedback.

• Designers must use discretion when deciding when to ship products, especially with non-deterministic AI models that require real-world testing rather than theoretical prototypes.

Understanding User Interaction with AI

• It’s crucial to observe how users interact with AI tools since their usage can differ significantly from initial expectations, leading to unexpected applications and insights.

• The unpredictability of user behavior highlights the importance of flexibility in design, as seen in projects like co-work and cla code which evolved based on actual user interactions.

A Day in the Life at Anthropic

• Much of a designer's time at Anthropic involves staying updated on various ongoing projects across teams, including model developments and prototyping efforts.

• Designers navigate through numerous internal initiatives, seeking insights into upcoming trends and innovations within the company’s research environment.

Collaboration and Execution in Design

• A significant part of the design role now includes facilitating collaboration among engineers and teams rather than just providing static designs; this ensures cohesive product experiences.

• Curiosity drives designers to engage deeply with internal discussions about industry trends, making platforms like Slack valuable resources for real-time updates.

Future Planning Amidst Rapid Change

• Despite being heavily involved in execution mode, designers also allocate time for strategic thinking about future directions based on market conditions and technological advancements.

• Visualizing potential future scenarios helps align team efforts towards common goals while adapting to evolving challenges.

Designing in Collaboration with Engineers

The Evolving Role of Designers

• Designers engage in collaborative conversations and whiteboarding sessions with engineers, providing feedback on built projects.

• The designer's role includes polishing and implementing code, indicating a shift towards more hands-on involvement in the development process.

• Traditional design processes like prototyping and user research are still practiced, supported by a dedicated user researcher on the team.

Changes in Design Time Allocation

• Previously, designers spent 60-70% of their time on mocking and prototyping; this has shifted to 30-40% as they now collaborate more closely with engineers.

• The new distribution of time includes significant portions dedicated to direct collaboration (30-40%) and implementation tasks.

Tools in the Designer's AI Stack

• The designer utilizes various tools including cloud chat for communication and cloud co-work for managing longer tasks effectively.

• Cloud code is integrated into their workflow via VS Code, allowing real-time adjustments while collaborating with engineers.

Continued Use of Figma

• Figma remains an essential tool for designers despite debates about the future of design tools; it facilitates exploration of multiple design options.

• The ability to visualize different styles and typography within Figma supports creative brainstorming that coding tools do not currently offer.

IDE vs. Command Line Preferences

• While engineering trends move towards command lines, designers still find value in using IDEs for quick edits like CSS changes due to ease of use.

Designing with Engineers: Balancing Feedback and Product Quality

The Role of Designers in Engineering Collaboration

• Designers often find themselves working closely with engineers, providing feedback and guidance to ensure cohesive product development. The advice is to let go of gatekeeping tendencies while still helping steer projects in the right direction.

• Many designers feel overwhelmed by the pace at which engineers are shipping products. A key question arises: how can designers help engineers improve their design skills or manage this rapid workflow without becoming stressed?

Strategies for Effective Collaboration

• When consulting on projects, it's beneficial for designers to explain their reasoning behind design choices. This approach helps engineers understand underlying principles rather than simply following directives.

• Designers should equip engineers with resources like design systems and code examples, enabling them to work independently and effectively without constant oversight from designers.

Managing Workload and Expectations

• Both designers and engineers face challenges in keeping up with increasing demands. There’s a shared sentiment that the capability to do more leads to pressure on both sides.

• The challenge lies not in the absence of designer involvement but rather in managing an overwhelming amount of work that one designer cannot handle alone.

Maintaining Quality Amid Rapid Development

• As products are released frequently, maintaining craft quality, trust, and user experience becomes crucial. It’s essential for teams to communicate clearly about product stages—especially when launching early versions labeled as research previews.

• For instance, launching features as "research previews" allows teams to acknowledge potential flaws while emphasizing the value they bring. This transparency helps set user expectations appropriately.

Building Trust Through Iteration

• It's important for companies to commit publicly to iterating on products after release based on user feedback. Failing to act on feedback can damage brand trust significantly.

• Continuous improvement post-launch fosters a sense of reliability among users, reinforcing that their input is valued and acted upon promptly.

Speed as a Trust-Building Mechanism

• The concept of "building trust through speed" emerges as a vital strategy; quick responses to user concerns demonstrate attentiveness and commitment from the team.

• Active engagement through social media channels enhances this relationship further by showing responsiveness—fixes are communicated swiftly, reinforcing user confidence in the product's evolution.

AI's Evolution in Code Development

The Role of AI in Software Development

• AI has progressed from assisting with code completion to writing 100% of the code, showcasing its rapid advancement.

• The discussion raises questions about the future role of human judgment in design and taste as AI becomes more proficient.

• There is a belief that while AI will improve at taste and judgment, humans will still need to make final decisions on what gets built.

Challenges Beyond Coding

• Many challenges in software development stem from interpersonal disagreements rather than technical coding issues.

• AI can assist but cannot resolve disputes between team members regarding feature inclusion or project direction.

Reevaluating Assumptions About AI

• Observations indicate that even top engineers are beginning to trust AI for coding tasks, challenging previous assumptions about human superiority in project management and design.

• The potential exists for AI to provide data-driven recommendations that could streamline decision-making processes.

Accountability and Decision-Making

• Despite advancements, there remains a need for skilled designers and product managers to oversee decisions influenced by AI outputs.

• Engineers must still validate the functionality of code generated by AI, emphasizing the importance of human oversight.

The Future Interface with AI

Current State of User Interfaces

• Chatbots have become an unexpected mainstay as user interfaces for interacting with AI, contrary to initial expectations that they would be temporary solutions.

Evolving Interaction Methods

• A combination of chatbots and more tactile user interfaces is anticipated as the future way users will interact with AI systems.

Innovations in User Experience

• Recent developments include interactive widgets within Claude that enhance user engagement through visual elements like weather updates and stock information.

Flexibility vs. Structure

• While traditional UIs offer structure, chatbot paradigms provide flexibility previously unavailable, allowing diverse interactions with models.

Future Directions

• It is expected that many UIs will increasingly be generated by models rather than manually coded, indicating a shift towards automated UI creation.

Chatting with AI: A New Medium of Interaction

The Evolution of Communication with AI

• The discussion highlights the emergence of chatbots as a new form of interaction, emphasizing that chatting through platforms like WhatsApp allows for a rich human-like communication experience.

• Kevin Wheel from another AI lab points out that talking is an effective way to engage with varying levels of intelligence, making it scalable across different IQ levels.

The Role of Management in Design

• The speaker reflects on their transition back to an Individual Contributor (IC) role after managing a team, expressing excitement about the work and the importance of being close to the design process.

• They share concerns about the future viability of middle management roles and express a desire to gain hands-on experience before potentially moving up in corporate ranks.

Insights Gained from IC Work

• Working as an IC has provided valuable skills that would not have been acquired solely through management, particularly in understanding evolving design processes.

• The speaker emphasizes the necessity for managers to empathize with their teams by actively engaging in current tools and methodologies used in design.

Future Perspectives on Design Management

• When asked about the longevity of design management roles, they assert that while management will persist, its nature may evolve beyond traditional people management towards providing direction and fostering team environments.

• They express a likelihood of returning to management long-term due to their passion for helping teams achieve their best work.

Design Management and the Importance of Individual Contribution

The Role of Managers in Design

• The speaker emphasizes a flexible approach to management, stating their motto is "whatever it takes" to support the team, whether by providing direction or executing tasks.

• It is suggested that design managers should return to individual contributor (IC) roles periodically to better understand ongoing changes and improve their management skills.

Learning from Engineering Practices

• The speaker notes that engineering disciplines often require engineering managers (EMs) to rotate through IC tasks for several months before fully transitioning into management roles.

• This practice could benefit design as well, which has traditionally focused more on people management rather than hands-on design work.

Challenges of Returning to IC Roles

• The speaker reflects on feeling rusty when returning to an IC designer role, particularly in handling critiques and receiving critical feedback regularly.

Insights on Co-work Development Process

• Discussion shifts towards co-work design; the speaker mentions previous debates about its purpose and how they ultimately decided on a simplified terminal-like interface.

• Multiple prototypes were developed internally before settling on a final version for co-work, indicating extensive exploration prior to launch.

Iterative Development Approach

• Although the final build took 10 days, significant time was spent prototyping various interactions and features leading up to this point.

• The decision was made to release what they had within those 10 days and iterate based on user feedback post-launch.

Reflections Post-launch

• The speaker expresses pride in successfully shipping the product rather than focusing solely on specific features or flaws.

• They highlight ongoing iterations aimed at enhancing user experience, particularly regarding task management between users and Claude (the AI).

Future Improvements for Co-work

• There are plans for further development of co-work's interface, aiming for a more integrated shared task list experience with Claude.

Misconceptions About Development Timeframes

• Clarification is provided regarding misconceptions about the 10-day timeline; it involved extensive prior explorations by multiple contributors.

Understanding the Evolution of Design Roles

The Journey to Co-Work

• The speaker reflects on the iterative process of developing ideas, emphasizing that while the right moment may seem obvious in hindsight, it often involves a long journey of exploration and adaptation.

Defining Co-Work

• Co-work is likened to "clawed with hands," suggesting an interactive and hands-on approach to working on computers. This metaphor highlights the collaborative nature of co-working environments.

• The speaker appreciates how co-work allows for extracting valuable insights from seemingly random or unorganized information, showcasing its utility in creative processes.

Hiring Trends in Design

Key Qualities for Designers

• In today's rapidly changing design landscape, resilience and adaptability are crucial traits for designers. They must be willing to embrace new methods and tools rather than cling to outdated practices.

Archetypes of Ideal Candidates

• The speaker identifies three archetypes they find particularly valuable when hiring designers:

• Strong Generalists: Individuals who excel at multiple core skills (80th percentile), allowing them flexibility across various roles within design.

• Deep Specialists: Designers who possess exceptional expertise in specific areas, making them invaluable assets due to their high level of skill.

• Craft New Grads: Early-career individuals who demonstrate wisdom beyond their years, eagerness to learn, and a fresh perspective free from entrenched processes.

Characteristics of Strong Generalists

• Strong generalists are described as "block-shaped" individuals who can adapt their skills across different domains within design. Their versatility is increasingly important as design roles evolve towards project management and engineering aspects.

Importance of Deep Specialists

• Deep specialists are those whose expertise goes significantly deeper than average; they might rank among the top 10% in their field. Their unique skills can greatly enhance product differentiation amidst a crowded market.

Value of Craft New Grads

• Craft new grads bring a blank slate mentality that can be beneficial in adapting to changing roles. Their lack of preconceived notions allows them to quickly learn new tactics without being hindered by established rituals.

Examples of Deep T-Shaped Skills

• A deep specialist might have technical skills akin to software engineers or excel in visual design elements like iconography. Such capabilities help elevate the quality and uniqueness of designs produced.

Expanding on Skill Shapes

• The discussion touches upon various skill shapes (like F-shape or E-shape), indicating that some candidates possess multiple strong competencies across different areas rather than just one deep specialization.

Advice for Aspiring Designers

• For young designers aiming to break into competitive environments like Anthropic, building a diverse portfolio through practical experience is essential for success.

Design Education and Building Real Projects

The Importance of Practical Experience

• Emphasizes the value of hands-on experience in design education, contrasting it with theoretical learning that often dominates traditional curricula.

• New graduates who actively use technology to create projects tend to be more innovative and less constrained by industry expectations, fostering a sense of limitless possibilities.

Community and Collaboration

• Highlights the emergence of communities focused on building and showcasing projects, akin to science fairs, which encourage creativity and collaboration among designers.

• Shares examples of unique projects within these communities, such as assembling robots or whimsical public art installations, illustrating the spirit of experimentation.

Standing Out in Design Careers

• Suggests that engaging in creative projects can significantly enhance a designer's visibility and appeal in the job market, regardless of their educational background.

Technical Skills for Designers: Is Coding Necessary?

The Role of Coding in Design

• Discusses whether designers need to learn coding; while not essential for all roles, having technical knowledge can enhance a designer's toolkit.

• Notes that understanding coding tools is beneficial even if one does not become an expert coder; awareness can improve collaboration with developers.

Current State of AI in Design

• Evaluates AI tools like Claude regarding their capabilities as designers; currently deemed insufficient for hiring due to lack of depth and creativity.

• Expresses curiosity about future advancements in AI design capabilities but acknowledges current limitations compared to human designers.

Management Insights: High vs. Low Leverage Tasks

Rethinking Low Leverage Tasks

• Reflects on initial management advice regarding prioritizing high-leverage tasks over low-leverage ones; challenges this notion by highlighting the value some low-leverage tasks can bring when performed by leaders.

Benefits of Engaging with Product Development

• Argues that senior leaders engaging directly with product testing fosters familiarity with products and enhances team morale through active participation.

Senior Leadership and Team Dynamics

The Role of Senior Leaders in Team Engagement

• A senior leader's deep care for their team is evident through hands-on involvement, such as fixing bugs and providing feedback directly.

• Personal gestures, like creating anniversary cards, reflect a leader's commitment to team morale and culture.

• Engaging in low-leverage tasks can yield high impact, surprising team members who may not expect leaders to invest time in these activities.

Building a Positive Team Culture

• Encouraging light-hearted roasting among team members fosters psychological safety and camaraderie.

• While not mandated, this practice indicates comfort within the team dynamic, allowing for playful interactions without fear of repercussions.

Balancing Professionalism with Approachability

• Roasting signifies a level of trust where employees feel safe enough to joke with their leader, indicating strong interpersonal relationships.

• Leaders should maintain high standards while also ensuring that their teams feel comfortable expressing themselves freely.

Establishing Psychological Safety

• Creating an environment where employees can critique or poke fun at leadership reflects mutual respect and understanding of boundaries.

• The balance between being approachable and maintaining high expectations is crucial; it allows for open communication without compromising performance standards.

Effective Management Styles

• A successful management style combines caring deeply about team members while also challenging them directly to achieve excellence.

• This approach mirrors concepts from "radical candor," emphasizing the importance of both empathy and accountability in leadership.

Framework for Clarity: The Legibility Framework

• Discussion on the legibility framework highlights its value in enhancing clarity within teams, though specific applications were not detailed.

Understanding the Legibility of Founders and Ideas

The 2x2 Framework for Evaluating Startups

• The framework discussed was introduced by Evan Tana, a partner at SPC, focusing on the legibility of founders and ideas in startups.

• It categorizes founders and ideas as either "legible" or "illegible," suggesting that highly legible combinations may indicate a lack of novelty in the idea.

• An illegible idea might be innovative but not easily understood; this is crucial for venture capitalists seeking unseen opportunities.

Role of Designers in Identifying Illegible Ideas

• Designers can play a role similar to VCs by identifying and transforming illegible ideas through storytelling and user experience (UX).

• The speaker reflects on their process of exploring internal projects to find energy around potentially valuable but unclear concepts.

Case Study: Cloud Studio Prototype

• A specific example mentioned is an internal prototype called "Cloud Studio," which had a complex interface built on agentic harness technology.

• Despite initial confusion about its functionality, the enthusiasm from team members indicated potential value, leading to further exploration.

Insights from Research on Early-stage Companies

• A research project revealed patterns among early employees at successful companies like Palantir and Stripe, highlighting that unconventional ideas often attract interest despite skepticism.

• The discussion emphasizes recognizing energy around unclear concepts as an opportunity for innovation.

Key Takeaways for Engaging with New Ideas

• Not every unconventional idea will succeed, but paying attention to intriguing yet unclear concepts can lead to breakthroughs.

• Understanding why certain ideas excite others—even if they seem nonsensical—can help designers refine these concepts into viable products.

Shoutout to the Anthropic Design Team

Recognition of Team Efforts

• The speaker expresses appreciation for the Anthropic Design team, highlighting their humility and resilience during changing job dynamics.

• The team comprises a diverse range of skills, from technical prototyping to high-craft delivery, showcasing their versatility in producing quality work.

• There is an ongoing hiring initiative at Anthropic, inviting interested candidates who resonate with the team's internal culture.

Hiring Insights

• Candidates are encouraged to consider specific archetypes when applying: strong generalists and deep specialists are particularly valued.

• The speaker emphasizes excitement about technology and innovation as key traits for potential applicants.

Lightning Round Questions

Recommended Books

• The Power Broker by Robert Caro is recommended for its comprehensive portrayal of a controversial figure's life and its lessons on long-term thinking in careers.

• Insomniac City by Bill Hayes is highlighted as a beautiful memoir that explores themes of love and mortality through the lens of Oliver Sacks' final days.

Favorite Movies and Shows

• The speaker enjoyed watching A Sentimental Value, praising its subtle storytelling and character development within a family drama context.

• They also mention enjoying The Pit Season 2, appreciating the competence displayed by characters in high-pressure situations.

Favorite Product Discovery

• The speaker shares enthusiasm for Retro, a photo-sharing app that allows users to document weekly moments without social media distractions. It has become meaningful for reflecting on past experiences over two years.

Life Motto

• (Timestamp not provided; content incomplete)

Life Motto: "It Is What It Is"

Embracing Acceptance in Life

• The speaker reflects on their life motto, "it is what it is," which they often find themselves saying. This phrase, while seemingly defeatist, serves as a reminder of the uncontrollable nature of many aspects of life.

• They share an experience from a 10-day meditation retreat that reinforced this motto, emphasizing the importance of not clinging to outcomes and accepting situations as they are.

• The depth of this acceptance is highlighted, suggesting that recognizing limitations can lead to personal growth and clarity.

Innovative Uses for Co-work

Introspection Through Technology

• The speaker discusses using Co-work for introspection by maintaining a folder filled with various notes over time, including one-on-one discussions and random thoughts.

• They describe how Co-work helps analyze these notes to gain insights about themselves and articulate their design preferences more clearly.

Practical Applications in Hiring

• A practical use case involves creating a rubric for evaluating design craft during interviews by having Co-work read through past interview notes and memos.

• This process reveals implicit insights about the speaker's values and preferences in design that they were previously unaware of.

Engagement with the Audience

Connecting Online

• The speaker invites listeners to connect with them on Twitter (now X), providing their handle as jenny_wen for further engagement.

Feedback Request

• They express a desire for product feedback regarding Co-work or any related projects, indicating openness to suggestions for improvement.