PM Scenario - #3: New Theme New Horizon

A situational PM question. You’re in the PM’s seat, and there’s a call to make.

The situation: You’re the PM for a consumer productivity app with 2.3 million monthly actives. The user-facing theme editor has shipped 6 weeks ago and currently supports 12 presets; engineering bandwidth is 2 full-time engineers for 8 weeks. User engagement dropped 8% after the latest UI refresh, and 4 key themes are driving 60% of theme usage. A beta release of a new theme library with 18 presets is planned for next sprint, but it requires 3 weeks of backend cache restructuring and 1 week of QA time.

What you know:

  • MAU 2.3M
  • eng team 2 FTE
  • themes in use 12 presets
  • eng beta library 18 presets planned
  • eng cache restructuring 3 weeks

Your call: Should we deploy the new theme library in the next sprint or push to the following sprint to ensure cache stability and a smoother rollout?

There’s no single right answer. Reply with what you’d do and why, and I’ll follow up with a question or two.