Read the original at Lenny’s Newsletter ↗lennysnewsletter.com · subscriber post
By Lenny Rachitsky · lennysnewsletter.com · @lennysan on X · YouTube · LinkedIn
Lenny Rachitsky profiles how Miro builds product, drawing on an interview with its CPO Varun Parmar. The post covers Miro's cross-functional AMPED structure, its three-year vision and annual strategy process, a streamlined OKR approach, quality-focused design reviews, and the team rituals that reinforce speed and craft.
Subscriber post — summary only01Key takeaways
- Cross-functional teams that include analytics, marketing, design and engineering from the start improve positioning and development decisions.
- A three-year painted picture plus an annual strategy gives direction while a rolling six-month roadmap keeps teams adaptable.
- Scaling OKRs can create overlap and process overhead; trimming levels and limiting objectives sharpened focus.
- Staged product reviews with clear templates, plus async Talktracks, keep high-stakes decisions efficient and raise quality standards.
- Simple quality heuristics and codified product principles help teams make consistent tradeoffs at large scale.
02Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.