Which three data sources would you analyze to improve activation?

This tests whether you ground hypotheses in diverse evidence before experimenting. A strong answer names qualitative feedback, funnel metrics, and behavioral analytics as distinct inputs.
WHAT THIS TESTS: The interviewer wants to know if you treat growth experimentation as a structured, hypothesis-driven process rather than random A/B testing. Specifically, they are checking whether you triangulate across qualitative, quantitative, and behavioral data to identify why users fail to reach the activation milestone, which is the highest-leverage point in the SaaS funnel. Candidates who understand activation know that running experiments without diagnostic data is just guessing.
A GOOD ANSWER COVERS: A good answer hits three distinct sources in order. First, qualitative research such as user interviews, support tickets, and survey responses to uncover the why behind user friction. Second, quantitative funnel analysis using signup-to-activation conversion data and cohort retention metrics to pinpoint exactly where users drop off and quantify the leak. Third, behavioral observation through session recordings, heatmaps, or product analytics path analysis to see what users actually do, click, or ignore before they experience core value. The best candidates also explain how these sources work together: qualitative data generates hypotheses, funnel analysis prioritizes which drop-off matters most, and behavioral data validates the specific mechanics to test.
COMMON WRONG ANSWERS: A major red flag is naming only A/B test results or conversion rates as a data source, since those are outputs of experiments rather than inputs that generate ideas. Another mistake is listing only surface-level vanity metrics like page views or total signups without connecting them to the activation milestone. Some candidates also propose purely demographic or firmographic data without explaining how it reveals behavioral barriers to value. Finally, confusing optimization with experimentation is a problem: suggesting you would only tweak an existing onboarding checklist rather than questioning whether the checklist is the right mechanism at all.
LIKELY FOLLOW-UPS: An interviewer might ask how you would turn one of these data sources into a specific hypothesis, how you would prioritize experiment ideas once you have them, or what your primary success metric would be for an activation experiment. They may also probe whether you would run qualitative research before or after a quantitative funnel review, or how you would define the activation milestone itself for a specific product.
ONE CONCRETE EXAMPLE: Suppose funnel analysis shows that 60% of new users drop off after starting the onboarding checklist but before inviting a teammate, which is your activation event. Qualitative interviews reveal users feel they do not know anyone to invite. Behavioral analytics show they open the invite modal but abandon it after 30 seconds. A strong experiment idea would be to test adding a pre-written invite template or allowing solo project creation first, using the invite modal completion rate as the success metric and retention at day 7 as a guardrail metric.
Source: appcues.com
Read the original → appcues.com
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.