The 'Product Five Whys' Technique
by Yuhki Yamashita • Chief Product Officer at Figma
Yuhki is the CPO at Figma, previously serving as a VP at Uber and holding product roles at Google and Microsoft. He has a unique background bridging engineering, design, and product management, having also taught introductory computer science at Harvard.
🎙️ Episode Context
In this conversation, Yuhki Yamashita breaks down Figma's unique product culture, emphasizing the importance of 'memifying' insights through storytelling and the PM's responsibility to own the 'Why.' He shares candid experiences about the failures and evolution of OKRs at Figma, strategies for product-led growth, and how extreme dogfooding drives quality.
Problem It Solves
Building exactly what customers ask for often leads to feature bloat without solving the underlying user problem.
Framework Overview
Adapting the engineering 'Five Whys' root cause analysis to product management. Instead of stopping at the feature request, the PM asks 'why' repeatedly to find the core structural opportunity.
🧠 Framework Structure
Question the Request: When a user ask...
Question the Problem: Once the proble...
Seek Structural Solutions: Look for o...
Own the Why: PMs strictly own the 'Wh...
When to Use
During user research, roadmap planning, and when receiving feature requests from vocal customers.
Common Mistakes
Stopping at the first layer of 'why' (the functional need) rather than reaching the behavioral or structural root cause.
Real World Example
At YouTube, Yuhki learned that because he couldn't specify every detail in a spec, he had to clearly define the 'Why' so engineers could make autonomous, high-quality decisions on error handling.
A customer is asking for a feature... why do they have that problem in the first place? Maybe there's an opportunity to fix that underlying condition.
— Yuhki Yamashita