How would you diagnose why a new feature isn't being adopted?
This tests your ability to diagnose a flat KPI. A great answer outlines a funnel (awareness, activation, usage) and combines quantitative data with qualitative insights from session replays. A red flag is proposing solutions without a diagnostic plan.
What's really being asked
This question assesses your ability to move from a lagging indicator (e.g., monthly active users of a feature) to a diagnostic plan based on leading indicators. It tests your structured thinking: can you break a vague problem ('it's not working') into a testable, multi-stage funnel? Interviewers want to see you combine quantitative and qualitative methods to isolate the 'why' behind the 'what'.
The full answer
A strong answer outlines a diagnostic plan in three phases. First, define the user adoption funnel, typically Awareness (did they see it?), Activation (did they try it?), and Engagement (did they find it useful?). Second, for each stage, propose specific metrics and tools. For Awareness, this could be impressions on a feature announcement or clicks on the feature's UI element, measured with heatmaps. For Activation, it's the funnel conversion rate from first click to successful use, looking for drop-offs. For Engagement, it's usage frequency or task completion rates. Third, emphasize combining quantitative data (e.g., from Amplitude) with qualitative insights (e.g., from session replays) to understand user friction and intent.
The mistakes people make
A major red flag is jumping straight to solutions ('We should send an email blast' or 'Let's redesign the UI'). This shows a lack of diagnostic discipline. Another weak answer focuses only on one type of problem, like blaming discoverability, without considering the full funnel from awareness to usability to value proposition. A junior answer might list tools without connecting them to specific hypotheses or funnel stages. A senior answer frames the investigation around hypotheses.
What usually comes next
'Let's say your funnel analysis shows a 90% drop-off after the first click. What's your next step?' (Answer: Dive into session replays for that specific user segment). 'What if all your funnel metrics look healthy, but usage is still flat?' (Answer: This points to a value proposition problem; the feature doesn't solve a real user need. The next step is qualitative feedback via surveys or user interviews).
A concrete example
'Our primary adoption KPI is flat at 5% after launch. First, I'd check Awareness: are users even seeing the feature? I'd look at a heatmap to see if less than 20% of users are even hovering over the new button. If awareness is fine, I'd check Activation: of the users who click, how many complete the core action? If we see an 80% drop-off in the setup modal, I'd watch session replays of users who bailed to see if it's a bug, a confusing UI, or a missing prerequisite. If the funnel is healthy but repeat usage is zero, the feature itself isn't valuable, and we need to talk to users.'
Interview question
A newly launched feature shows low adoption. What is the most effective initial step to diagnose the root cause?
- a.Launch an email campaign to ensure all users are aware the feature exists.
- b.Propose a UI redesign to make the feature more intuitive for new users.
- c.Map the user journey into a funnel and analyze conversion rates for each stage.Correct
- d.Watch session replays of users who interacted with the feature to find usability issues.
Why? this is the answer
The best first step is to create a structured diagnostic plan, like a user funnel (e.g., Awareness, Activation), to quantitatively isolate the problem. Jumping to solutions like an email campaign or a redesign, or diving into qualitative analysis like session replays without a specific hypothesis, is less effective.
Just read this? Test yourself on what you have been reading.
Read the original → screeb.app
- #analytics
- #product sense
- #metrics
- #data-driven
- #funnels
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on analytics — each one lists the topics its interview covers.
See open roles