Search for a command to run...

Timestamps are as accurate as they can be but may be slightly off. We encourage you to listen to the full context.
In this fascinating conversation, Ryo Lu, Head of Design at Cursor, joins a16z General Partner Jennifer Li to explore how AI is fundamentally reshaping the boundaries between design and development. (01:45) Lu shares his journey from watching designs die in meetings at companies like Notion and Asana to now building tools that let creators ship real products in minutes rather than years. (02:36) The discussion reveals how AI is collapsing traditional product feedback loops and enabling a new era where designers can become full-stack builders. (07:54) Central to their conversation is the idea that we're moving beyond fragmented teams using separate tools toward unified workflows where one codebase can serve everyone if you design the right concepts instead of just buttons. (13:15)
Jennifer Li is a General Partner at Andreessen Horowitz (a16z), where she focuses on investments in enterprise software and infrastructure. She brings extensive experience from the product side, having previously worked with design and engineering teams before joining the venture capital firm.
Ryo Lu is the Head of Design at Cursor, the AI-powered code editor that's revolutionizing how designers and developers work together. He previously held design roles at notable companies including Notion and Asana, where he experienced firsthand the frustrations of traditional design-to-development handoffs. Lu has a biology background and is known for his RyoOS project, which recreates classic operating system interfaces to demonstrate timeless design principles.
Lu emphasizes that while AI tools like Cursor can help you skip from idea to 60-70% implementation on the first try, (13:46) human opinion and taste remain crucial. The key insight is that LLMs have "seen everything" but lack genuine preference, often defaulting to mediocre outputs like "purple gradients everywhere." (15:15) Successful creators must provide clear direction and boundaries about what constitutes good work, as Lu warns: "If you don't put in that opinion, it will just produce AI slop." (15:36) This means the future belongs to those who can combine AI's rapid execution capabilities with strong personal vision and taste.
Lu traces how software development became increasingly fragmented over 15 years, with designers stuck in Figma, PMs in Google Docs, and engineers in code editors, each using "their own tool, their own artifact, their own words and lingo." (08:42) This fragmentation created expensive coordination problems and slow feedback loops. AI tools are now reversing this trend by creating unified environments where the same codebase can serve different roles through different interfaces. (11:00) Rather than forcing people to change their workflows, the new approach absorbs all existing artifacts and formats, allowing teams to collaborate around a single source of truth while maintaining their preferred ways of working.
Lu advocates for a fundamental shift from user-centric to system-centric thinking when building products. (28:58) While user-centric approaches start with specific problems for specific people, they create limitations from the beginning and often force companies to add more features rather than simplify core concepts when expanding. System-centric design starts with the software's fundamental architecture and concepts, then adapts different views for different users. As Lu explains, "All these purposeful apps, they're kind of selfish. They are siloing people, siloing workflows." (31:56) The key is designing the fewest number of concepts that can do the most things for the most people, then providing different packaging and configurations rather than building separate tools.
Lu envisions AI as "almost like a universal interface" where the basic interaction is prompt-and-response, but this can manifest in many different forms beyond chat boxes. (34:34) The interface could be tab completion, element selection, or completely purpose-built views, but underneath it's the same AI architecture. (36:25) This approach prevents the limitation of forcing everyone to interact through a blank input field, which can be intimidating and ineffective for newcomers. Instead, people can be eased into AI capabilities through interfaces they already understand, while still accessing the same powerful underlying functionality. (37:00)
Rather than overwhelming users with infinite possibilities, Lu emphasizes that "the biggest constraint is simplicity" - there's a natural limit to how many concepts any person can process at once. (39:14) Effective AI tools must prioritize what to show and when, building mechanisms that accommodate complexity through layers rather than linear addition of features. (41:13) The designer's role shifts from deciding where buttons go to defining core concepts, their relationships, and appropriate defaults for different user types. This layered approach allows 80% of users to start simply while power users can access deeper functionality, maintaining the tool's essential simplicity while enabling advanced capabilities.