Prioritization Framework: Fixing a Known Bug Versus Shipping New Feature Work

You are the product manager for a product that customers already use. Two pieces of work are competing for the same team: launching a new feature, or fixing a bug that is already in the product. Assume the team cannot do both right away. How would you decide which comes first? Lay out the framework you would use and show how you would apply it. ```hint Compare on one scale A fix removes pain and a feature adds value, so the two are hard to compare directly. Think about what would let you put both on the same yardstick, and which kinds of bug should never enter that comparison at all. ``` ### Clarifying Questions - How severe is the bug: does it break a core flow such as sign-in, payments or checkout, lose or corrupt data, or create a security or compliance exposure, or is it an irritant with a workaround? - Roughly how many users or sessions run into the bug, and how many people would use the feature in its first few months? - Is the feature tied to a commitment, such as a contract, a regulatory date, a launch event or a gap against a competitor, or is it a nice-to-have? - Do both items need the same engineers, or could the fix ship inside a release that is already planned? ### What a Strong Answer Covers - A severity gate that sends serious bugs (outage, data loss, security, money movement, legal exposure) to the front without a cost-benefit debate. - A shared yardstick for the remaining cases: reach, impact on key user journeys, strategic value, confidence and effort for each option. - The hidden costs on both sides: churn, support load and trust damage from leaving the bug, regression risk from fixing it, and the opportunity and maintenance cost of the feature. - A clear decision rule plus options beyond a strict either/or, such as time-boxing the fix or bundling it into a scheduled release. - How the decision is explained to stakeholders and checked afterward with metrics. ### Follow-up Questions - The bug affects only a small share of users, but they are your highest-value accounts. Does your answer change? - Sales has promised the feature to a large customer by a fixed date while support keeps escalating the bug. How do you resolve it? - How would you stop this argument from repeating every planning cycle?