Weekly Review Template
Growth is not doing many things every day.
Growth is running experiments, reading data, listening to users, and improving judgment.
That is why weekly review matters.
Without a weekly review, it is easy to:
Do many actions without knowing what worked
Look at many metrics without making decisions
Collect feedback without extracting patterns
Stay busy every week without clearer growth
The goal is not to write a report.
It is to decide what to continue, stop, double down on, and adjust next week.
What to Review
A growth weekly review should cover six things:
Goal: what did we try to validate?
Actions: what growth actions did we take?
Data: what changed in the core metrics?
Feedback: what did users say or do?
Judgment: which assumptions were validated or rejected?
Next week: what experiment comes next?
Do not only write, "We published five articles and contacted 30 users."
That is activity.
Ask:
What result did those actions create?
What does the result mean?
What should we change next week?
Template 1: Weekly Goal
Start with the goal.
Weekly goal:
1. Core assumption to validate:
2. Target user:
3. Main channel:
4. Expected metric:
5. Success criteria:
Example:
Assumption: Reddit has B2B founders looking for cold email deliverability help.
Target user: SaaS founders with teams under 10 people.
Main channel: r/SaaS, r/startups, cold email communities.
Expected metric: 10 useful conversations, 3 trials.
Success: at least 3 people share domain setup screenshots for diagnosis.
The more specific the goal, the more useful the review.
Template 2: Weekly Actions
Group actions by channel:
Channel 1:
- Action:
- Volume:
- Output:
- Link / record:
Channel 2:
- Action:
- Volume:
- Output:
- Link / record:
Example:
Reddit:
- Answered 18 relevant questions
- Published 1 lesson-style post
- Got 6 comment interactions
Cold email:
- Manually found 50 leads
- Sent 25 personalized emails
- Received 7 replies, including 3 positive replies
Actions should be traceable.
Otherwise next week cannot be compared.
Template 3: Core Metrics
Do not track too many metrics.
Pick five to eight:
Visits
Signups
Activations
Trials
Bookings
Paid users
Retention
Conversion rate
Positive replies
Quality conversations
Use a table:
Metric | Last week | This week | Change | Notes
Visits | 800 | 1200 | +50% | YouTube grew
Signups | 40 | 52 | +30% | SEO article converted well
Activations | 12 | 18 | +50% | onboarding improved
Bookings | 3 | 7 | +133% | cold email replies increased
Metrics should support decisions.
Not decoration.
Template 4: User Feedback
Record exact wording.
High-frequency feedback:
1. User quote:
- Context:
- Implied problem:
- Possible action:
2. User quote:
- Context:
- Implied problem:
- Possible action:
Do not only write:
Users liked the feature.
Users want it simpler.
Write the quote:
"I do not struggle with writing cold emails. I struggle with knowing why they land in spam."
This may mean users need deliverability diagnosis more than copy generation.
Template 5: Channel Judgment
Score channels weekly:
Channel | User fit | Cost | Conversion | Feedback quality | Continue?
Reddit | High | Medium | Medium | High | Continue
X | Medium | Low | Low | Medium | Adjust
SEO | High | High | Low | Low | Keep building
Cold email | High | Medium | High | High | Double down
This prevents single-metric mistakes.
For example:
X gets likes but no signups
Cold email is smaller but gets bookings
SEO is slow but compounds
Reddit has fewer interactions but better feedback
Channel judgment should include user quality.
Template 6: Next Week's Experiments
The review must produce experiments.
Next week experiments:
Experiment 1:
- Assumption:
- Action:
- Success criteria:
- Owner:
- Deadline:
Experiment 2:
- Assumption:
- Action:
- Success criteria:
- Owner:
- Deadline:
Do not run too many.
One to three experiments per week is enough early on.
Each experiment should be small enough to finish in one week.
Full Weekly Review Template
Copy this:
# Growth Weekly Review
Period:
Weekly goal:
Core assumption:
## 1. Actions
- Channel A:
- Channel B:
- Product actions:
- Content actions:
## 2. Core Metrics
Metric | Last week | This week | Change | Notes
## 3. User Feedback
- Quote 1:
- Quote 2:
- Quote 3:
## 4. Main Findings
- Validated assumptions:
- Rejected assumptions:
- New problems:
## 5. Channel Judgment
Continue:
Stop:
Double down:
Adjust:
## 6. Next Week Experiments
Experiment:
Action:
Success criteria:
Deadline:
Do it at the same time every week.
Keep it under 60 minutes if possible.
Common Mistakes
Common mistakes:
Only listing actions, not results
Only reading data, not user language
Only tracking growth, not cost
Setting weekly goals that are too big
Tracking too many metrics and making no decisions
No next-week experiment after review
Reviewing failures but not successes
Review is not to prove effort.
It is to improve judgment for the next week.
Summary
Weekly review is a growth decision tool, not a status report
Review goal, actions, data, feedback, judgment, and next experiments
Group actions by channel and use metrics for decisions
Keep exact user quotes
Judge channels by user quality, not only traffic size
Run only one to three small weekly experiments
Answer: continue, stop, double down, or adjust?
Next, we will cover which growth metrics to track.
评论
0分享你对这一章的想法