Launch-or-hold decision framework for a feature inherited as a new PM
Company: Meta
Role: Product Manager
Category: Product / Decision Making
Difficulty: medium
Interview Round: Other
You have just joined a team as its product manager. Your predecessor had been driving a feature, and whether it launches is now your call. What framework would you use to make that go/no-go decision?
```hint Mind the gap you inherited
You were not there when this feature was conceived. Think about what you need to reconstruct before judging it, and which findings should stop a launch on their own instead of being traded off against good numbers.
```
### Clarifying Questions
- Has the feature already been exposed to users through an experiment or a beta, or is it built but untested?
- Has a launch date already been promised to leadership or partner teams, or is the timing mine to set?
- Is the previous PM still reachable, and are the engineers and designers who built the feature still on the team?
- Do I make the final call, or do I bring a recommendation to my manager or a launch review?
### What a Strong Answer Covers
- Rebuilding the original problem, hypothesis and success criteria before judging the build, and closing the context gap a newly arrived PM has
- Evidence of user value and metric impact, including guardrail metrics and whether any experiment result can be trusted
- Readiness checks that block a launch outright, such as privacy, integrity, quality and a rollback path, kept separate from the factors that are weighed against each other
- Whether the feature still fits current goals, what it costs to maintain, and how reversible the launch is
- A decision with more than two possible outcomes, communicated with conditions and rollback triggers, and reasoning that resists both sunk cost and a reflexive reset
### Follow-up Questions
- The experiment shows the primary metric up but one guardrail slightly down. How do you make the call?
- Leadership was promised this launch for next week, and your review turns up an unresolved privacy question. What do you do?
- How would your framework change if the feature never ran an experiment and there is no time to run one?
Overview: A Meta product manager interview question about making the launch decision on a feature you inherited after joining a team. It tests how you rebuild missing context, judge experiment evidence and launch readiness, separate hard blockers from trade-offs, and reach a clear, well-communicated decision.