Rule out plumbing before you question the idea. Walk the funnel step by step: are people seeing the entry point, clicking it, completing it, coming back. Most zero adoption launches die at discovery or the first step, not at the value proposition. Then watch a handful of sessions and talk to five users who fit the target. End with a written decision: fix, reposition, or remove, with a date.
Why interviewers ask this
This is about how you behave when you are wrong. Interviewers want a diagnostic sequence rather than a feelings answer, and they want to see you check exposure before questioning the concept, since a good idea placed behind a menu nobody opens looks identical to a bad idea. The forced decision at the end matters too, because the common real world failure is leaving the thing alive and unowned.
How to structure your answer
- Walk the funnel from exposure to repeat use.
- Fix discovery problems before rethinking the concept.
- Talk to a small number of target users who tried it once.
- Commit to a written decision with a date: fix, reposition, or remove.
Example answer
I assume it is plumbing before I assume it is the idea. So the first day is the funnel: how many people were even exposed to the entry point, how many clicked it, how many finished, how many came back. Nine times out of ten a zero adoption launch is dying at the first two steps, which is a discovery problem and not a value problem. On one launch we found the entry point sat behind a menu that most accounts never opened, and moving it into the empty state took adoption from almost nothing to a third of new accounts inside a week. If the funnel looks healthy and people are still not returning, then it is the idea, and I want five conversations with people in the target group who tried it once. At the end of two weeks I want a written decision: fix, reposition, or remove, with a date. The failure mode is leaving it alive and unloved.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you tell a discovery problem from a value problem in the data?
- How do you communicate a failed launch upward?
- What is the longest you would give something before removing it?
Related product manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions