Read the original at Lenny’s Newsletter ↗lennysnewsletter.com · subscriber post
By Lenny Rachitsky · lennysnewsletter.com · @lennysan on X · YouTube · LinkedIn
A community roundup from a paid PM newsletter covering threads on sprint cadence for tiny startups, where PM and designer responsibilities overlap, and how to run PM team and leadership meetings. It also touches on running blameless post-mortems and finding product coaches, plus a short list of recommended reads.
Subscriber post — summary only01Key takeaways
- Teams of two to three people often do better with continuous shipping or Kanban than formal sprints.
- Six-week cycles were praised as a middle ground between drifting quarters and cramped two-week sprints.
- Product and design work best as co-design, with PM owning customer context and design owning the experience.
- Leadership meetings should separate tactical weekly check-ins from strategic monthly or yearly planning.
- Blameless post-mortems work best when participants get time to reflect beforehand and focus on three key themes.
“A bad system will beat a good person every time”Edward Deming (quoted by Tal Raviv) · Lenny’s Newsletter
02Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.