Strategy question

As a product manager for an existing product, how do you choose between launching a new feature and fixing an existing bug?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Whether the candidate can apply a repeatable framework to prioritize between new value and stability, rather than answering with a blanket rule.

State that the decision depends on severity and reach, not a fixed rule of always fixing bugs first or always shipping features.
Assess the bug: how many users are affected, whether there is a workaround, and whether it blocks a core workflow or revenue.
Assess the feature: its expected impact (new users unlocked, revenue), and whether the opportunity is time sensitive, such as a competitor launch or seasonal window.
Use a simple framework, such as comparing estimated user-impact hours lost to the bug against expected value gained from the feature.
Decide with a concrete example: a bug silently corrupting user data always outranks any feature, while a minor visual bug can wait.

Rejects a blanket rule and instead gives a clear decision framework based on severity, reach, and time sensitivity.
Uses a concrete example to show where the line falls, such as data loss bugs always winning.
Notes that a small, fast bug fix can often be done in parallel without delaying the feature.

Chapters of the AI PM course that teach what this question tests.