Release-Readiness Call: Known Defects Versus Losing Ground to a Rival's Launch

You are the product manager for a product that is nearly ready to launch, but some known bugs are still open. A competitor is expected to launch a similar product soon, and fixing every bug first could push your launch past theirs. How do you decide between launching on schedule with the bugs and delaying? Walk through how you would make the decision and what you would do once it is made. ```hint Size both costs, then question the choice Estimate what each open bug would cost users and the business, and what arriving after the competitor would really cost in this market. Then ask whether launching everything on time and waiting for every fix are truly the only two options. ``` ### Clarifying Questions - What kinds of bugs are open: crashes, data loss, security or billing errors, or cosmetic and edge-case problems, and how many users would run into them? - How long would the fixes take, and how confident are we in the competitor's launch date? - In this market, does arriving second carry a lasting cost, such as network effects, annual contracts or switching costs, or can customers easily try both products? - How quickly can a fix reach users after launch: within hours through the web or a server-side flag, or only after app-store review or a hardware cycle? ### What a Strong Answer Covers - Bug triage by severity, reach and reversibility, with explicit lines no launch crosses (security, privacy, data loss, billing, safety). - A grounded estimate of what delay costs against this competitor, rather than assuming the first to market always wins. - Options beyond the binary choice, such as cutting scope, a staged or limited rollout, a labeled beta or feature flags. - A clear decision process: who decides, which teams weigh in, and launch criteria agreed before the deadline pressure. - Execution after the call: monitoring, rollback triggers, a dated fix plan, and honest communication with users and the team. ### Follow-up Questions - Your engineering lead says the release is unsafe, while your executive sponsor insists on the date. How do you resolve it? - You launch with known bugs, and in the first week crash reports rise well past the threshold you set. What do you do in the next 24 hours? - How would your process differ for a consumer app compared with software sold to businesses under contracts?