Product Council Meeting Template

Monthly is the standard cadence for most product organizations. Weekly is too frequent (not enough changes between meetings to justify the time). Quarterly is too infrequent (decisions pile up and get made informally). Some organizations run biweekly councils during planning season (Q4 for annual planning, or around major launches) and monthly otherwise. The [Product Operations Handbook](/product-ops-guide) covers how to calibrate meeting cadences to your organization's decision velocity.

The VP Product (chair), all senior PMs or team leads, the CTO or engineering director, and the Head of Design. The CFO or CEO may attend quarterly for strategic discussions. Individual contributors should not attend regularly. They can join for specific decision items where their expertise is needed. Total attendees should be 5-8.

A [sprint review](/templates/sprint-retrospective-template) is a team-level ceremony where the team demonstrates completed work and collects feedback. A product council is an organization-level forum where product leaders make cross-team decisions. Sprint reviews happen every 1-2 weeks within a team. The product council happens monthly across all teams.

The chair (VP Product) makes the final call if the council cannot reach consensus. However, most decisions should emerge from the structured discussion. The decision item format (options, pros/cons, recommendation) is designed to make the trade-offs clear enough that the group converges naturally. If the council frequently needs the chair to break ties, the pre-read is not providing enough data for informed decisions.

Schedule a dedicated session outside the council. The council should identify that the decision exists, assign an owner, and set a deadline for a follow-up meeting. The analytics product investment in the example above shows this pattern: the council deferred to a dedicated 2-hour session rather than trying to make a $1.4M decision in 15 minutes. ---