Choosing Between a Facebook Android Engagement Feature and a Tech-Debt Library Upgrade

You are a product manager on Meta's Facebook app for Android. Two pieces of work are competing for the same team's time: - **A customer-facing feature** that is expected to raise engagement by some amount, call it X. - **A technical task**: upgrading the app's libraries to get rid of long-standing legacy bugs. The upgrade has no impact that users would notice right away. How would you decide which one to prioritize? Walk through how you would compare the two, what you would recommend, and how you would explain the decision. ```hint Put both on one scale The feature's value already comes as a number. Work out what the bugs and the outdated libraries cost the app today and what they put at risk later, so the upgrade can be weighed in comparable terms. ``` ### Clarifying Questions - How large is X, how confident is the estimate, and which engagement metric does it move? - What do the legacy bugs do today: crashes or freezes, slow startup, security exposure, or mainly slower development? Are any of the outdated libraries near end of support or about to fall behind an Android platform requirement? - What is the team's goal for this planning period, and does either item have a fixed deadline, such as a competitive launch? - Does the team have to pick one outright, or can it split capacity or sequence the two? ### What a Strong Answer Covers - Clarification of what X really is and of what the legacy bugs and outdated libraries cost now - A way to express the upgrade's hidden value (stability, risk, development speed, work it unblocks) in terms that can be weighed against the feature's engagement gain - A comparison that accounts for effort, confidence and the cost of delaying each item, tied to the team's current goal - A clear recommendation, including how the two items are ordered or shared, and the conditions that would reverse it - How the call is explained to leadership and engineering, and how both outcomes are measured afterward ### Follow-up Questions - If engineering says the upgrade would also make future feature work faster, how would you size that benefit, and does it change your call? - Leadership wants the engagement win this quarter. How do you make the case for the upgrade, or decide it can wait? - How would you set up a standing rule so this kind of trade-off is not re-argued every planning cycle?