You are launching a new in‑app messaging feature. With limited engineering capacity, how would you prioritize which messaging capabilities (push notifications, in‑app alerts, email reminders) to build first to maximize user engagement?

Use the RICE framework to score each capability. First, list options MECE‑wise. Second, estimate Reach, Impact, Confidence, and Effort using data and stakeholder input. Third, calculate RICE scores and rank. Fourth, validate top picks with a quick stakeholder alignment session. Finally, outline a phased roadmap with clear success metrics. (120‑150 words)

I would start by MECE‑splitting the messaging options into push notifications, in‑app alerts, and email reminders. Using the RICE framework, I’d estimate Reach (percentage of users who would see the feature), Impact (expected lift in engagement), Confidence (based on data or prior experiments), and Effort (engineering hours). I’d gather data from analytics, user surveys, and stakeholder interviews to fill these estimates. After calculating RICE scores, I’d rank the options and select the top two for the first sprint. I’d then run a quick stakeholder alignment session to confirm buy‑in and adjust for any technical constraints. Finally, I’d define success metrics (e.g., click‑through rate, session length) and set up A/B tests to validate the impact. This structured approach ensures data‑driven prioritization while keeping cross‑functional alignment. (175‑200 words)