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 Coda's product organization plans, reviews, and builds product, drawing on an interview with CPO Lane Shackleton. The post covers Coda's evolving planning cadence, OKR philosophy, review forums like Catalyst and Design Huddle, a joint product-and-design team, and a first-principles culture that treats preparation and rituals as core to craft.
Subscriber post — summary only01Key takeaways
- Keep planning to roughly 10% of an execution period, and use lightweight check-ins to contextualize the current cycle.
- Derive annual Big Bets from ranked business challenges, then ladder quarterly team commitments to them.
- Treat OKRs as commitments you expect to hit, not strategy, and set goals around inputs the team controls.
- Run review forums with clear roles and reminders so meetings have the right people and useful context.
- Keep a team hub in one flexible document to reduce context silos and build a historical decision record.
- Prepare deliberately through repeated practice, treating product craft more like a professional athlete's training.
02Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.