A monthly growth review should decide whether to continue, adapt, stop or investigate—not repeat updates people could read. Send a concise evidence pack in advance, organise the meeting around the current growth constraint, compare observed results with expectations and end each discussion with a decision, owner and review date. Include customer evidence and guardrails, not only a dashboard.
Define the decisions before the meeting
Write two or three questions the review must answer. Examples include: “Is activation still the primary constraint?”, “Should the assisted setup test continue?” or “What evidence would justify entering a second segment?”
If an item does not require interpretation, challenge or a decision, put it in the pre-read. This protects meeting time and makes preparation more honest.
Build a concise evidence pack
Share the same structure each month:
- objective and current constraint;
- baseline, expected movement and actual result;
- underlying counts and relevant segments;
- customer interviews, support themes and observed behaviour;
- work completed and experiments changed;
- cost, quality and risk guardrails;
- open decision questions.
Link to source material in a maintained customer research repository. Separate observation from interpretation so participants can challenge the reasoning without disputing the record.
Read numbers with context
Compare like periods and state material changes in tracking, audience, product or seasonality. Segment only when the groups are meaningful and the sample supports interpretation. Present absolute counts beside rates.
Do not use a green arrow as an argument. Ask what changed in customer behaviour, which alternative explanations remain and whether the result is large enough to alter a decision. Where evidence is weak, record uncertainty rather than filling the gap with confidence.
Bring customer evidence into the room
Select concise extracts that represent a pattern or a useful contradiction. Do not treat a vivid quotation as a vote. Explain who the participant was, the situation discussed, how the evidence was gathered and whether it appears elsewhere.
Protect personal data and follow consent. The purpose is to help the team understand why behaviour may have changed, not to decorate metrics with anonymous fragments.
Illustrative scenario: replace reporting with a decision
Illustrative scenario: a team’s dashboard shows that trial activation rose after a new onboarding email. The status meeting might celebrate and move on. In a decision review, the team sees that completion increased only among existing partner referrals, while direct sign-ups were unchanged.
Interview notes suggest referred users arrived with a completed data file. The team decides to test a preparation checklist for direct sign-ups before scaling email promotion. The example is hypothetical; the point is to connect segmented evidence to an owned next decision.
Use a 60-minute agenda
A practical agenda is:
- 5 minutes: restate objective, constraint and decisions required.
- 10 minutes: clarify the evidence pack; do not present it again.
- 20 minutes: examine expected versus observed results and competing explanations.
- 15 minutes: decide continue, adapt, stop or investigate.
- 10 minutes: confirm owners, dates, dependencies and what is not changing.
Use the current 90-day growth plan as the frame. Park unrelated ideas for the next priority review rather than allowing them to consume the agenda.
Record a decision log
For every decision, capture:
- the choice and accountable owner;
- evidence considered;
- assumptions and dissent;
- action and due date;
- success, stop or escalation condition;
- next review date.
Begin the following meeting by checking whether previous decisions were implemented and what they taught. This creates accountability without confusing activity with impact.
Facilitate productive challenge
Ask the person closest to the evidence to speak before the most senior person when appropriate. Invite a credible alternative explanation. Distinguish disagreement about facts, interpretation, risk tolerance and priorities; each needs a different resolution.
The goal is not unanimous confidence. It is a transparent choice that the team can execute and revisit through the process for choosing the next growth priority.
Limitations and trade-offs
Monthly cadence may be too slow for a short launch and too frequent for a long enterprise sales cycle. Adjust the operating checks while keeping a stable decision rhythm.
Dashboards can contain tracking errors, and qualitative research can reflect recruitment bias. Important safety, legal or customer-harm issues should escalate immediately rather than wait for the meeting.
Frequently asked questions
Who should attend the review?
Invite the decision owner and people responsible for customer evidence, delivery and material risks. A large audience encourages reporting rather than discussion.
What happens when evidence is inconclusive?
Choose the smallest reversible next step that reduces the most important uncertainty, and name the evidence required at the next review.
Should every metric have a target?
No. Some measures diagnose context or protect guardrails. Give targets only when they support a decision and the baseline makes them meaningful.
Your useful next step
Rewrite the agenda for your next monthly meeting as three decision questions. Send a one-page evidence pack 24 hours in advance and remove slide-by-slide status presentations. End the meeting by reading every decision, owner and review date aloud.
