Claim and evidence
This rapid experimentation continues, with Popsa running up to 10 growth experiments weekly.Popsa · review.firstround.com · undated
Secondary
A reputable third party analysed it (Lenny's Newsletter, First Round Review, Reforge, an Ahrefs study).
Working · 2026-11 Described in a founder-led growth playbook; no date shown on the page.
What the numbers show
run by Popsa during its founder-led growth phase (as reported by First Round)
review.firstround.comWhy it works
A short fixed window forces focus on a single outcome and makes the goal learning rather than shipping. Posting experiments in a shared channel adds light accountability.
How to run it
- Pick one outcome for the sprint
- Time-box to one or two weeks
- Run the smallest tests that answer the question
- Post each experiment in a team channel
- Review the learning and choose the next sprint
Ways to run it
Design options to test, not promised results.
- Option AOne-week sprints
A fixed weekly rhythm with a single learning goal, as teams like Popsa use for rapid testing.
- Option BTwo-week sprints
A slightly longer window for tests that need more traffic or build time.
- Option CPublic experiment channel
Post each test's hypothesis and result in a shared channel for light accountability.
Dated examples
- —
Popsa
Reported as running up to 10 growth experiments a week
“This rapid experimentation continues, with Popsa running up to 10 growth experiments weekly.”
✓ quote checked word-for-word on the pagereview.firstround.com · undated
Does it still work?
Described in a founder-led growth playbook; no date shown on the page. source
Risks
- Short sprints bias toward small optimizations
- Page has no byline or date
Sources
- review.firstround.com
“Growth sprints apply a concept from Agile software development to a single outcome: learning.”
✓ quote checked word-for-word on the page - review.firstround.com
“Growth sprints typically take one week, maybe two.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (ops-ai)