Read the original at Lenny’s Newsletter ↗lennysnewsletter.com · subscriber post
By Lenny Rachitsky · lennysnewsletter.com · @lennysan on X · YouTube · LinkedIn
Lenny Rachitsky opens a series on how top product teams work, using Figma's CPO Yuhki Yamashita as the first case. The post walks through Figma's planning cadence, its shift from OKRs to narrative 'headlines' and rebranded 'commitments', design crit and product review formats, team organization around products and platforms, and the PM's responsibility for articulating the 'why'.
Subscriber post — summary only01Key takeaways
- Set annual company priorities, then run larger half-year planning with quarterly refreshes to adjust course.
- Replacing OKR checklists with claim-style headlines sparked better debates about philosophy and measurement.
- Design crits should be generative and silent-first; product reviews should drive decisions with a mapped option space.
- Organize teams around products plus horizontal platform groups, and expect the structure to keep evolving.
- PMs own the 'why' and should invest in internal storytelling when the rationale behind work is unclear.
“PMs are responsible for the "why.”Yuhki Yamashita · Lenny’s Newsletter
02Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.