Weekly Tester Activity Report — Template
Copy this file to reports/weekly-activity-YYYY-MM-DD.md each cycle. Fill every field; use "not measurable" + the reason rather than an estimate.
Week of: · Prepared by: Executor/QA · As-of: (timestamp, America/New_York)
Status: DONE-RECEIPTED / DONE-UNRECEIPTED / DRAFTED-AWAITING-APPROVAL / IN FLIGHT / BLOCKED / FAILED-NEEDS-DECISION
1. Data sources checked
| Source | Tool / evidence | Observed state |
|---|---|---|
| Activity export / dashboard | ||
| Feedback channel | ||
| Workspace files |
2. Activity metrics (real data only)
| Metric | Value | Source | Confidence |
|---|---|---|---|
| Registered testers (cumulative) | |||
| New registrations this week | |||
| Weekly active (≥1 run in rolling 7d) | |||
| Activation rate (first run ≤7d of signup) | |||
| Week-2 retention (actives in week 2 ÷ cohort) | |||
| Drop-off: registered → first run started | |||
| Drop-off: first run started → completed | |||
| Recharges past $3 free credit |
3. Drop-off identification
- Largest stage loss:
- Evidence:
- Cohort size (n): — if n < 20, state "not yet significant"
4. Feedback gathered
| Source | Count | Themes | Verbatim quotes (optional) |
|---|
5. One bounded improvement proposal
- Proposal (docs / demo / onboarding — pick one):
- Scope bound (what it explicitly does NOT include):
- Hypothesis (never a claim):
- Pre-registered measurement: metric · cohort comparison · success threshold · invalidation rule · guardrail · minimum n
- Result from LAST cycle's proposal: measured value vs. threshold → KEEP / ITERATE / DROP
6. Follow-through tracker
| Item | Waiting on | Chase date | Flag |
|---|
7. Next cycle
- Report due:
- Data needed before then:
Rules: no claim of improvement without a measured before/after; no fabricated users, quotes, or metrics; raw exports preserved unmodified; every number traces to a named source.