Gate for signal
LINEAR / PRODUCT / SEED
Admit the users your product is ready to teach you from
Linear collected roughly 10,000 waitlist emails, but invited only about ten people a week. Saarinen handpicked them from survey responses and sent each invitation himself.
Why it compounds.
A narrow cohort prevents the same known defect from flooding the team with duplicate feedback. It also makes every new user legible, so behavior can be connected to role, expectations, and prior workflow.
Ask two qualification questions at signup. Admit one coherent cohort at a time. Resolve the blockers that cohort shares before widening the aperture.
Artificial scarcity is not the play. If the cohort is not tied to a learning question and a release decision, the waitlist is theater.
SAVE TO ELENA
Turn the observation into an experiment.
Elena adapts the play to your company, scopes the first sprint, and watches the signal that tells you whether to keep going.
- Run it when
- The product is useful for a narrow segment but known blockers would overwhelm broad access.
- Owner
- Founder or product lead
- First sprint
- Add two qualification questions, admit ten matched users, contact each personally, and clear shared blockers before the next cohort.
- Leading signal
- Cohort activation, daily use, feedback duplication, and time from issue to fix.
- Stop rule
- Open access or change the segment if controlled cohorts stop producing new learning for three rounds.