💡

InsightHunt

Hunt the Insights

Y

Yuhki Yamashita

Episode #295

Chief Product Officer

Figma

🚀Career & Leadership🎯Product StrategyExecution

📝Full Transcript

12,997 words
Lenny (00:00:00): There's something controversial about this idea that everyone can see what you're doing or that multiple designers can be in the file at the same time. We like to say that one of the first responses we saw Lenny [inaudible 01:08:35] Figma was, if this is the future of design, I'm quitting, right? I'm changing careers. (00:00:17): And there's that tension of that narrative tension, but that is signal that you're part of this revolution and you're trying to change something. And when it equips your customers or user base with that, then I think that's something that they can really get behind and champion. (00:00:35): So it's not just that they're championing for a tool, they're also championing for a new way of working. Obviously, that's a tall order or don't want to come up with that, but hopefully, if you're a founder and you're working on something, your vision is so big that you have those kind of ideas and it's like, how do you actually equip your customers to want to talk about that? (00:00:58): Welcome to Lenny's podcast. I'm Lenny, and my goal here is to help you get better at the craft of building and growing products, interview world class product leaders and growth experts to learn from their hard won experiences, building and scaling today's most successful companies. (00:01:12): Today my guest is Yuhki Yamashita. Yuhki is Chief Product Officer at Figma, where he's been for almost four years. Prior to Figma, he was at Uber, both as a Product Leader and also, interestingly, as Head of Design for one of their bigger product teams. Before Uber, Yuhki spent time at Google and Microsoft, even taught an introductory computer science course at Harvard. (00:01:33): In our conversation, we explore Figma's product development philosophy, how they build such consistently great products, how they hire, what habit Yuhki has found to be the most instrumental in his success in his career, and also what Yuhki and his product team have learned by bu...

💡 Key Takeaways

  • 1Product Managers must own the 'Why' of a problem, while empowering designers and engineers to own the 'What' and 'How'.
  • 2Great storytelling involves synthesis and 'memification'—turning complex insights into sticky phrases that leadership repeats.
  • 3Use the 'Five Whys' technique not just for engineering outages, but to dig deeper into user feature requests.
  • 4Dogfooding should be extreme: Use your own product for tasks it wasn't originally designed for (e.g., PM decks in Figma) to uncover friction.
  • 5Effective goals (OKRs) must satisfy three criteria: Legibility, Actionability, and Authenticity.
  • 6In Product-Led Growth, the sales team's role is to empower internal champions to evangelize the product, rather than just selling software.

📚Methodologies (3)

🚀 Career & Leadership

A storytelling approach that focuses on synthesizing complex information into simple, repeatable narratives (memes) that stick with leadership and drive decision-making.

Core Principles

  • 1.Synthesis: Distill conflicting opinions and data into a cohesive thesis, not just meeting notes.
  • 2.Memification: Create sticky phrases or stories for data insights so leaders cite them spontaneously in meetings.
  • 3.The Context Reset: Explain the problem assuming the audience has zero context, removing the 'curse of knowledge'.
  • +1 more...

"A story is only as good as the action that it's capable of driving."

#'memification'#storytelling#career
View Deep Dive →
🎯 Product Strategy

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.

Core Principles

  • 1.Question the Request: When a user asks for X, ask why they need X.
  • 2.Question the Problem: Once the problem is identified, ask why that problem exists in the first place.
  • 3.Seek Structural Solutions: Look for opportunities to fix the underlying condition that created the problem, rather than patching the symptom.
  • +1 more...

"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."

#'product#whys'#technique
View Deep Dive →
Execution

A refined approach to goal setting that moves away from rigid metric obsession toward honest commitments about what the team is actually trying to achieve.

Core Principles

  • 1.Legibility: Can anyone outside the team look at the goal and understand exactly what it means?
  • 2.Actionability: Does looking at the goal inspire the team to do something differently today?
  • 3.Authenticity: Does this goal honestly depict what the team is working on, or is it a post-rationalization?
  • +1 more...

"If you stop an engineer in the hallway... and they can't say [the OKR], then what's the point of publishing this OKR?"

#authentic#setting#l.a.a.
View Deep Dive →