How would you decide whether to build a feature or fix a bug (assuming both take the same engineering effort)?

Introduction

The decision between building a new feature or fixing a bug is a critical trade-off that product managers face regularly. This scenario requires careful consideration of various factors, including user impact, business goals, and resource allocation. I'll outline my approach to making this decision, considering both short-term gains and long-term product health.

Step 1

Clarifying Questions (3 minutes)

• What is the severity and impact of the bug we're considering fixing?

• Why it matters: The severity of the bug directly affects user experience and potentially product reliability.
• Hypothetical answer: It's a moderate bug affecting 15% of users, causing occasional data sync issues.
• Impact on approach: A high-severity bug might take precedence over a new feature, especially if it's impacting core functionality.

• What is the expected impact of the new feature on user engagement or revenue?

• Why it matters: Understanding the potential upside helps weigh the opportunity cost of not implementing the feature.
• Hypothetical answer: The feature is expected to increase user engagement by 10% for active users.
• Impact on approach: A high-impact feature might be prioritized if the bug isn't critical and the feature aligns with strategic goals.

• Are there any upcoming deadlines or market pressures influencing this decision?

• Why it matters: External factors can sometimes dictate priorities, especially in competitive markets.
• Hypothetical answer: We're approaching our annual user conference in two months, where we typically showcase new features.
• Impact on approach: The conference deadline might lean us towards building the feature if the bug isn't severely impacting users.

• What's the current state of our technical debt, and how does this bug relate to it?

• Why it matters: Accumulating technical debt can slow down future development and increase long-term costs.
• Hypothetical answer: We have moderate technical debt, and this bug is symptomatic of an underlying architectural issue.
• Impact on approach: Fixing the bug might be prioritized if it helps address technical debt and prevent future issues.

• How does each option align with our current quarter's OKRs or strategic initiatives?

• Why it matters: Aligning decisions with overarching company goals ensures we're moving in the right direction.
• Hypothetical answer: The new feature aligns closely with our goal of increasing user engagement, while bug fixes contribute to our reliability metrics.
• Impact on approach: If increasing engagement is a top priority this quarter, it might tip the scales towards building the new feature.