Claim and evidence
Hold a fixed weekly growth meeting run by a named growth lead, with a product or project owner on each test.
No dated example yet. Treat this tactic as a hypothesis.
Primary
The company or founder describes the tactic and its result themselves: own blog, talk, filing.
Working · 2026-11 Basic operating rhythm; structure varies by team model.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
A single accountable person and a standing review keep the backlog moving and results visible. Per-test owners stop experiments from stalling.
How to run it
- Name a growth lead to run the process
- Hold one standing weekly meeting
- Review last week's results and next week's tests
- Assign an owner to every test
- Limit overlapping tests on the same funnel step
Ways to run it
Design options to test, not promised results.
- Option ASingle growth lead
Name one person who runs the process and the meeting and keeps the backlog moving.
- Option BOwner per test
Assign a product or project owner to every test so none stalls between meetings.
- Option COverlap limit
Cap the number of tests touching the same funnel step at once to keep results readable.
Timeline
- 12016 first documented: Sean Ellis, SaaStr Annual talk transcript
- 22026-11 status checked: Working
Dated examples
No dated example yet. Treat this tactic as a hypothesis.
Does it still work?
Basic operating rhythm; structure varies by team model. source
Risks
- Meeting becomes a status report without decisions
- Lead role can become a bottleneck
Sources
- saastr.com
“At the very least you should start with a growth master.”
✓ quote checked word-for-word on the page - saastr.com
“Really important, appoint a product manager or a project manager to each test.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (ops-ai)