Cut everything that is not on the single path that proves the hypothesis. Keep the core flow end to end, even if it is ugly, and cut breadth, settings, edge case polish, and anything you can do manually behind the scenes for the first few weeks. Never cut the instrumentation, because a launch you cannot measure teaches you nothing and you will end up shipping it twice.
Why interviewers ask this
Cutting scope is the most common real decision a product manager makes, and the interviewer wants to know your default direction. The right instinct is cut breadth, keep depth, since a narrow complete flow produces learning and a wide half flow produces nothing. They also listen for whether you keep tracking, whether you are willing to do things manually, and whether cut work gets written down rather than silently dropped.
How to structure your answer
- State the rule: keep one complete path, cut breadth.
- Name the categories you cut first.
- Mention doing things manually instead of building tooling.
- Protect the instrumentation and say why.
- Record deferred items and tell stakeholders before they notice.
Example answer
I cut breadth and keep depth. The thing I protect is one complete path from start to value, even if it is ugly and only works for one kind of user, because a half finished flow proves nothing. So settings go, bulk actions go, the second and third integration go, and anything I can do manually behind the scenes for a few weeks definitely goes. On one launch we did account provisioning by hand for the first thirty customers rather than build the admin tooling, and that bought us five weeks. The one thing I never cut is the tracking, because a launch you cannot measure means shipping it again to learn anything. I also make sure the cut items are written down as explicitly deferred rather than quietly dropped, and I tell the stakeholders which ones went and why before they notice on their own, because finding out later is what actually damages trust.
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 decide between cutting scope and moving the date?
- What have you shipped that was more manual than users realized?
- How do you stop a deferred list from becoming a graveyard?
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