I went straight for 'it depends' which felt safe but I could see the interviewer waiting for me to actually commit to something.
Acknowledge that both schedule and feature correctness matter, but frame the answer around customer value and business impact. Explain that the right balance depends on context—such as market windows, competitive pressures, and product maturity—and that as a PM, you'd use data and stakeholder alignment to decide. Emphasize that shipping the wrong features on time can be more damaging than a slight delay with the right features, but also recognize that missing a critical market window can be fatal.
Pro tip: Show that you understand the cost of delay and the cost of poor quality—quantify trade-offs where possible, and mention that you'd involve engineering, design, and marketing early to avoid false dichotomies.
Start by asking: what is the primary objective of this release? Is it to capture a market window, satisfy a regulatory deadline, or validate a hypothesis? The answer shapes the priority.
Evaluate the cost of delaying the release (e.g., lost revenue, competitive disadvantage) against the cost of shipping subpar or incorrect features (e.g., churn, brand damage, rework).
Determine if you can ship a smaller set of high-value features on time, then iterate. This often resolves the tension by delivering core value without compromising quality.
Facilitate a discussion with engineering, design, marketing, and leadership to agree on the trade-off, ensuring everyone understands the risks and rationale.
Whatever the decision, communicate it clearly and set up metrics to track outcomes, so you can learn and adjust future prioritization.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.