Claim and evidence
They got it to 10 tests per week.Twitter · saastr.com · undated
Primary
The company or founder describes the tactic and its result themselves: own blog, talk, filing.
Working · 2026-11 Still the default operating model; AI-assisted teams push the volume higher (Fyxer 2026). Testing speed alone does not fix weak hypotheses.
What the numbers show
testing pace Twitter's growth team reached, per Sean Ellis's talk (anecdotal)
saastr.comrun by Fyxer's growth engineers, more than two per work day (as reported to Growth Unhinged)
growthunhinged.comrun by Popsa (as reported by First Round)
review.firstround.comWhy it works
Growth is found by trial; more shots on goal per week means faster learning and more compounding wins. A backlog plus a fixed weekly rhythm removes the stalls between ideas, so the team learns from losses as well as wins.
How to run it
- Build a backlog of ideas from data, research and team input
- Score and rank ideas (ICE, RICE or similar)
- Commit to a weekly cadence of launches and reviews
- Assign an owner to every test
- Log the result and learning, then feed it back into the backlog
Ways to run it
Design options to test, not promised results.
- Option AWeekly launch target
Commit to a set number of launches each week and review them in one standing meeting, as Twitter's growth team did.
- Option BAI-assisted analysis
Let engineers use AI for data analysis so each test needs fewer hand-offs, as Fyxer did.
- Option CSmall tests by default
Favour the smallest test that answers the question so the weekly rhythm holds.
Timeline
- 12016 first documented: Sean Ellis, SaaStr Annual talk (year per transcript page text)
- 22016 Twitter — Growth team raised its testing pace as described by Sean Ellis in a conference talk
- 32026 Fyxer — Growth engineers ran 514 experiments in a year, with AI help for data analysis
- 42026-11 status checked: Working
Dated examples
- 2026
Fyxer
Growth engineers ran 514 experiments in a year, with AI help for data analysis
“Their secret: running 514 (!) experiments, more than two per work day.”
✓ quote checked word-for-word on the pagegrowthunhinged.com · 2026-03-04
- 2016
Twitter
Growth team raised its testing pace as described by Sean Ellis in a conference talk
“They got it to 10 tests per week.”
✓ quote checked word-for-word on the pagesaastr.com · undated
- —
Popsa
Reported by First Round 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?
Still the default operating model; AI-assisted teams push the volume higher (Fyxer 2026). Testing speed alone does not fix weak hypotheses. source
Risks
- Volume without quality hypotheses produces noise and false positives
- Needs enough traffic; low-traffic products cannot read many tests
Sources
- saastr.com
“The goal of the growth team is to test at a high tempo.”
✓ quote checked word-for-word on the page - growthunhinged.com
“Their secret: running 514 (!) experiments, more than two per work day.”
✓ quote checked word-for-word on the page - review.firstround.com
Change log
- 2026-11-20 — harvest v0.1 (ops-ai)