# PM Scenario - #3: New Theme New Horizon

**URL:** <https://forum.kirupa.com/t/pm-scenario-3-new-theme-new-horizon/683991>\
**Category:** talk\
**Created:** [November 10, 2026, 4:05pm UTC](https://forum.kirupa.com/t/pm-scenario-3-new-theme-new-horizon/683991 "2026-11-10T16:05:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yoshiii](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/yoshiii/32/31156_2.png) [@Yoshiii](https://forum.kirupa.com/u/Yoshiii)\
**Post date:** [November 10, 2026, 4:05pm UTC](https://forum.kirupa.com/t/pm-scenario-3-new-theme-new-horizon/683991/1 "2026-11-10T16:05:07Z")

</div>

_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.