Pushing back when leadership wants to launch before the product is ready
Company: Google
Role: Product Manager
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Other
You are a product manager on a team that is close to a launch date. Either the team or leadership has decided to release the product on schedule even though parts of it are unfinished. You believe the right call is to delay the launch. How would you handle this?
Explain what you would do from the moment you learn about the decision through launch and afterward, including how you would raise your concern and what you would do if the decision stands.
```hint Unpack "incomplete" first
Before arguing for a delay, sort what is missing by how much harm it would cause users and the business if it shipped as is, and ask yourself whether the only choices really are launching everything now or postponing everything.
```
### Clarifying Questions
- What is driving the date: a commitment to a partner or customer, a public event, a competitor, a regulatory deadline, or an internal goal?
- What exactly is unfinished: a secondary feature, known bugs, untested performance at scale, or incomplete privacy, security or accessibility work?
- Who made the decision, and what is my role: the product manager who owns the launch, or a team member whose recommendation was overruled?
- Would you like my general approach, or a time I faced this situation?
### What a Strong Answer Covers
- Learning why the decision makers chose the date and what risk they consider acceptable before contesting the call
- Classifying the gaps by severity and reversibility, separating true launch blockers from issues that can ship with mitigations
- Options between a full launch and a full delay, such as reduced scope, a limited or staged rollout, or a beta label, each with its cost
- Raising the disagreement directly with the decision maker using evidence, then committing to the final decision, with escalation reserved for safety, privacy, security or legal risks
- Safeguards and follow-through for whatever ships: rollback criteria, monitoring, support readiness and a retrospective
### Follow-up Questions
- Leadership hears your case and still launches on the date. What do you do the next morning?
- What would make you escalate above your manager instead of committing to the decision?
- You win the delay, and a competitor launches first and gains the users you wanted. How do you judge whether your call was right?
Overview: A Google product manager behavioral question about what to do when your team or leadership decides to launch an unfinished product to hit a deadline and you think the launch should wait. It tests judgment about launch risk, constructive disagreement, options between shipping and delaying, and committing once the decision is made.