Product All-Hands Meeting Template

Biweekly for teams of 10-30 people. Monthly for teams of 30+. Weekly is too frequent and leads to "meeting about a meeting" syndrome where there is not enough new content. Less than monthly and teams drift out of alignment. The [product operations handbook](/product-ops-guide) covers how to set cadence based on team size and velocity.

Three tactics. First, always use video and screen sharing for demos. Second, provide an anonymous question submission tool (Slido, Google Form, or a shared doc) so remote attendees can ask questions without the social friction of unmuting. Third, post a recording and notes within 24 hours so async team members can catch up.

Strategy should be 10-15% of the meeting (5-10 minutes). Demos should be 25-30% (15-20 minutes). Q&A should be at least 15-20% (10-15 minutes). The remaining time goes to metrics, dependencies, and announcements. The demos are what people remember. The Q&A is what builds trust. The strategy is what provides direction.

Invite 1-2 guest leads from sales, support, or marketing on a rotating basis. Their perspective surfaces customer context that product teams miss. But keep the core audience to product, engineering, design, and data. If the meeting grows beyond 50 people, it becomes a presentation, not a meeting. Consider separate cross-functional forums for broader audiences. For ongoing cross-functional communication, the [Internal Product Newsletter](/templates/product-newsletter-template) scales better.

Do not use the all-hands for surprise announcements. If a sensitive topic needs to be communicated, brief managers first and let them inform their teams in smaller settings. The all-hands can then address questions and provide additional context. For org changes that affect [product team structure](/glossary/prioritization), coordinate with HR on the communication plan. ---