How to run a product council at a growth stage company requires answering three questions before the first meeting: what decisions does this group make versus inform, who has authority to override the council's output, and how do you prevent the council from becoming a 12-person committee where consensus is impossible?
Product councils at growth-stage companies exist because the product surface is now too large for one PM or one executive to hold in their head. But the structural failure mode is predictable: the council becomes a coordination meeting, not a decision-making body. Everyone is consulted; no one is responsible.
This guide gives you the structure that makes a product council useful rather than ceremonial.
What a Product Council Is (and Isn't)
H3: What It Is
A product council is a recurring forum where the most consequential product decisions — strategic bets, investment allocation, major trade-offs across product lines — are surfaced, debated, and decided by the people who have the authority and context to decide them.
At a growth-stage company (Series B–D, 50–300 employees), this typically includes:
- CPO or VP Product (chair)
- 2–4 group PMs or product leads
- CTO or VP Engineering
- Head of Design
- CEO (for strategic decisions) or a delegate
H3: What It Is Not
- A status meeting (no project updates unless they drive a decision)
- A roadmap review (unless the roadmap decision needs cross-functional input)
- A forum for escalating problems that should be resolved at the team level
- A group where everyone gets a vote on everything
Setting Decision Rights
H3: The RACI for the Product Council
Before the first meeting, define decision rights explicitly:
| Decision type | Who decides | Who is consulted | Who is informed | |--------------|-------------|-----------------|----------------| | Strategic direction (bets) | CPO + CEO | Council | Engineering, Design, Sales | | Resource allocation | CPO | Council + Finance | Eng teams | | Prioritization across product lines | CPO | Council | PMs, Eng leads | | Feature-level decisions | PM owns | May consult council | Council informed |
Feature-level decisions should not reach the product council. If a PM is escalating a feature decision to the council, either the PM lacks authority or the decision has cross-cutting impact that was not flagged early enough.
According to Lenny Rachitsky's writing on product leadership, the most common dysfunction in product councils is that they become escalation dumping grounds — PMs bring decisions to the council because they want cover, not because the decision genuinely requires cross-functional authority. Define escalation criteria explicitly and enforce them.
The Meeting Structure
H3: Meeting Cadence
Growth-stage product councils typically meet:
- Monthly: Strategic decisions, investment allocation, major trade-offs
- Bi-weekly: Cross-cutting prioritization questions, new initiative reviews
- Ad hoc: Critical escalations that cannot wait for the monthly cadence
Do not meet weekly unless the council is in a rapid decision-making phase (e.g., planning season, major strategic pivot). Weekly cadence creates scheduling pressure to fill the meeting even when there are no decisions.
H3: The Agenda Format
Every council meeting should have:
- Pre-read (shared 48 hours in advance): The decision to be made, context, options, and a recommended option with rationale
- Quick context (5 minutes): The decision author presents the recommendation — not the full background
- Discussion (15–20 minutes): What questions does the council have? What assumptions need to be stress-tested?
- Decision (5 minutes): The chair calls the decision. One of: approve, approve with conditions, reject, or defer with explicit reason
- Documentation (post-meeting): Decision and rationale logged within 24 hours
The chair must call the decision in the room. "Let's discuss offline" is not a product council output.
H3: What Goes in the Pre-Read
The pre-read should be structured as:
- The decision: One sentence stating what is being decided
- Context: 2–3 paragraphs explaining why this decision is coming to the council now
- Options: 2–3 options with pros, cons, and resource implications
- Recommendation: The PM's or CPO's preferred option and why
- What we need from the council: A vote? Feedback on one specific assumption? A budget approval?
According to Shreyas Doshi on Lenny's Podcast, the pre-read is where most product council efficiency is won or lost — councils that skip the pre-read spend the first 20 minutes of every meeting getting people up to speed, leaving no time for the actual decision. Pre-reads are not optional.
Preventing Council Dysfunction
H3: Committee Creep
As the company grows, more people want to be "in the room." Resist this. The council should have the minimum number of people needed to make the decision with the right authority and context. Every additional person increases discussion time and decreases decision quality.
H3: Consensus Seeking
Some decisions have clear correct answers; most strategic decisions involve trade-offs with no objectively correct answer. The council chair should call the decision even when consensus is not reached. Document the dissenting view for the record, but make the call.
H3: Post-Decision Accountability
Every decision should have a named owner who is responsible for executing it and reporting back on outcomes. The council should review the outcomes of major decisions at the following month's meeting: did the decision produce the expected result? What did we learn?
According to Gibson Biddle on Lenny's Podcast, the most effective product councils treat their decisions as experiments — they commit to a direction, measure the outcome, and use the council forum to review whether their strategic thesis was correct. This feedback loop is what transforms a product council from a governance body into a learning institution.
FAQ
Q: What is a product council? A: A recurring decision-making forum for the most consequential product decisions — strategic bets, investment allocation, and major trade-offs — attended by the people who have the authority and context to decide them.
Q: Who should be in a product council at a growth-stage company? A: CPO or VP Product as chair, 2 to 4 group PMs, CTO or VP Engineering, Head of Design, and CEO for strategic decisions. Keep the group small enough to make decisions — typically 6 to 8 people maximum.
Q: How often should a product council meet? A: Monthly for strategic decisions and investment allocation, bi-weekly for cross-cutting prioritization, and ad hoc for critical escalations. Avoid weekly cadence unless in an active planning phase.
Q: What is the biggest failure mode of a product council? A: Becoming a committee where consensus is required for every decision, or an escalation dumping ground where PMs bring decisions for cover rather than because the decision requires cross-functional authority.
Q: How do you prevent a product council from becoming a status meeting? A: Ban status updates unless they directly drive a decision. Require pre-reads 48 hours in advance. The chair must call a decision in the room — "let's discuss offline" is not an acceptable output.
HowTo: Run a Product Council at a Growth Stage Company
- Define decision rights before the first meeting — what decisions the council makes versus informs versus is consulted on, and who has authority to override the council's output
- Set the council membership at the minimum number needed for the right authority and context — typically 6 to 8 people — and resist expansion as the company grows
- Require pre-reads shared 48 hours in advance for every agenda item including the decision, context, options, recommendation, and what the council is being asked to provide
- Structure every meeting as 5 minutes context, 15 to 20 minutes discussion, 5 minutes decision — the chair must call the decision in the room, not defer to offline discussion
- Document every decision and rationale within 24 hours with a named owner responsible for execution and a follow-up review at the following month's meeting
- Enforce escalation criteria explicitly so feature-level decisions remain with the PM and the council handles only strategic bets, investment allocation, and cross-cutting trade-offs