A product council is a recurring meeting where senior leaders from product, engineering, design, and business functions make cross-cutting prioritization decisions that no single team can make alone. It resolves resource conflicts, approves major bets, and ensures product strategy stays aligned with business goals.
What the Council Decides
Resource allocation conflicts. When two product teams need the same platform engineering resources, the council decides who gets priority based on strategic impact, not who lobbied harder.
Large bets. Investments above a threshold (typically 2+ engineering quarters or $X impact) require council approval. This prevents teams from quietly committing to massive projects without cross-functional buy-in.
Strategy pivots. When market conditions shift or key metrics change, the council decides whether to adjust priorities across teams or stay the course.
Dependency resolution. When Team A's roadmap depends on Team B's platform work, the council mediates timelines and priorities.
Who Sits on It
Keep it small: 5-8 people. Typically:
- VP/Head of Product (chairs the meeting)
- VP/Head of Engineering
- Head of Design
- VP of Sales or Revenue
- VP of Customer Success
- CFO or COO (for budget-level decisions)
PMs present to the council but do not sit on it permanently. Rotate PMs in based on which product areas are being discussed.
How to Run It
Cadence: Monthly for strategic decisions. Biweekly if you are in a fast-moving environment. Weekly is too frequent and turns it into a status meeting.
Format: Each agenda item gets a PM presentation with clear ask. Use the RICE Calculator or weighted scoring output to make proposals data-driven. The PM presents the opportunity, the resource requirement, the tradeoff, and their recommendation. The council decides.
Time limit: 60-90 minutes maximum. Three to four decisions per meeting. More than that, and decision quality drops.
Output: Written decisions distributed within 24 hours. Each decision includes: what was approved, what was deprioritized, who owns execution, and when the next review happens.
Common Mistakes
Too large. Councils with 12+ people become discussion forums, not decision bodies. If you cannot decide with 8 people, adding more will not help.
No authority. If the council makes "recommendations" that executives override, it serves no purpose. The council must have real decision-making power over resource allocation.
Only reacting. Councils that only respond to escalations miss the proactive work: reviewing portfolio health, identifying strategic gaps, and reallocating resources before problems arise. Use the roadmap building guide to structure proactive portfolio reviews.
No data. Decisions made on opinions instead of metrics create political dynamics. Require every proposal to include impact estimates and prioritization scores. The team health check provides data on team capacity and morale that should inform allocation decisions.