Amplitude

1How Rise and a quiz-funnel team use Amplitude

• Start experiments from the biggest drop-off in Amplitude, then agree on the problem. The team finds the biggest drop-off in the web quiz and app onboarding in Amplitude. They then list every reason the page might not convert, such as lack of trust or an unclear value proposition, agree as a team on the biggest problem, and only then list solutions.

  Everything is written down so a failed test can be diagnosed and iterated on. About 70% of their experiments fail on the first try, and they iterate on the failures to find winners. Quote: "we're obsessed with the problem and not the solution."

  Lenny's Podcast▶ 36:00

• Rise pairs Amplitude with Segment and GrowthBook rather than judging tests in it. Rise uses Segment for tracking, Amplitude for product analytics, and GrowthBook, which sits on the warehouse, for test statistics. Product managers do not judge winners in spreadsheets, and the team does not write its own stats engine, because of pitfalls like sample ratio mismatch.

  GrowthBook was Rise's biggest move toward standardizing experimentation, and it is cheap if the data is already organized. Metrics like trial start rate need clean definitions, since real user journeys are non-linear with reinstalls and returns. Quote: "never write your own statistics engine".

  Lenny's Podcast▶ 56:30