Free template
Weekly growth review template
The 30-minute ritual that keeps a growth team honest: metrics against targets, experiment verdicts, blockers with owners, and next week's bets.
Markdown — paste it into Notion, Linear or any doc
# Weekly Growth Review — Week of [date] **Facilitator:** ... **Attendees:** ... **Timebox:** 30 minutes ## 1. North star and key metrics (10 min) | Metric | Target | This week | Last week | Trend | |--------|--------|-----------|-----------|-------| | North star metric | ... | ... | ... | ↑ / → / ↓ | | Signups | ... | ... | ... | | | Activation rate | ... | ... | ... | | | Retention (W4) | ... | ... | ... | | | MRR | ... | ... | ... | | - Biggest surprise in the numbers: ... - One-sentence explanation (verified, not guessed): ... ## 2. Experiments (10 min) | Experiment | Status | Metric | Result so far | Next step | |------------|--------|--------|---------------|-----------| | ... | Running | ... | ... | ... | | ... | Concluded | ... | Ship / Kill | ... | - Experiments concluded this week and their verdicts: ... - Learning worth sharing outside the team: ... ## 3. Blockers (5 min) - Blocker: ... — Owner of the unblock: ... — By when: ... ## 4. Next week's bets (5 min) - Bet 1: ... (owner: ...) - Bet 2: ... (owner: ...) - Explicitly NOT doing: ... ## Parking lot - Topics raised but deferred: ...
How to run a weekly growth review that people don't dread
The weekly growth review is the heartbeat of a growth process. Without it, experiments drift, metrics get checked only when someone is anxious, and the roadmap quietly becomes whatever the loudest person wants. With it, the team makes one small, evidence-based course correction every week — and those corrections compound faster than any single big win.
The timebox is the feature. Thirty minutes forces preparation: the facilitator fills the metrics table before the meeting, so the time is spent interpreting numbers, not reading them aloud. The rule for section 1 is "explained, not guessed" — if signups dropped and nobody knows why, the action is to find out, not to speculate for ten minutes.
Section 2 reviews experiments against their written hypotheses (see the growth experiment template). Concluded tests get a verdict — ship, kill or iterate — and the verdict is recorded, because unwritten conclusions get relitigated. Blockers must leave the room with an owner and a date; a blocker without both is a complaint.
The most underrated line in the template is "explicitly NOT doing". Naming what you are deliberately ignoring this week protects focus and makes trade-offs visible to stakeholders. And the parking lot keeps the meeting on rails: interesting tangents are captured, not chased. Run it every week, same day, same time — consistency is what turns a template into a culture.