Introduction
PostHog grows mostly through self-serve signups. A new team creates a PostHog Cloud account, installs an SDK and, if things go well, creates its first insight within the first week. That "week-1 activation" is one of the most watched numbers in a product-led company, because teams that activate are far more likely to become paying customers months later. In this case, week-1 activation fell from 42% to 34% in three weeks, an 8-point drop (about 19% relative). I'll clarify the situation, rule out external factors, map the journey, break down the metric, form and test hypotheses, and finish with a decision framework and resolution plan.
Root cause questions reward structure: confirm the data is right, rule out external causes, split the metric into funnel steps and segments, and only then form hypotheses. Resist naming a cause in the first two minutes.
Step 1
Clarifying Questions (3 minutes)
- Why it matters: A changed event definition can create a fake drop.
- Hypothetical answer: An organisation that creates at least one saved insight on its own ingested events within 7 days of signup. No definition change.
- Impact: We must still check that the events behind the metric fire correctly.
- Why it matters: A sudden drop points to a release; a gradual one points to mix or market change.
- Hypothetical answer: It fell sharply over about four days, then stayed flat at 34%.
- Impact: Suggests a specific change around that date.
- Why it matters: A big change in who signs up changes activation without any product change.
- Hypothetical answer: Signups rose about 25% over the same period.
- Impact: Mix shift is a serious candidate.
- Why it matters: Narrows the hypothesis space.
- Hypothetical answer: A new onboarding product picker, a PostHog Desktop launch that drove a spike of signups, and SDK updates.
- Impact: We have three possible causes to separate.
Practice similar questions
Subscribe to access the full answer