Your product has two competing feature requests: a new analytics dashboard for power users and a simplified onboarding flow for new users. With limited resources, how would you decide which to prioritize? Explain your decision‑making process.

Framework: RICE + stakeholder impact. 1) Define Reach, Impact, Confidence, Effort for each feature. 2) Calculate RICE score. 3) Map scores to OKRs and product roadmap. 4) Validate with cross‑functional stakeholders (engineering, design, sales, support). 5) Make a data‑driven trade‑off decision, documenting assumptions and risk mitigation. 6) Communicate the rationale and next steps to the team. (≈130 words)

I would start by applying the RICE framework to quantify each feature’s value. First, I’d estimate Reach (percentage of users affected), Impact (scale of benefit), Confidence (certainty in estimates), and Effort (person‑weeks). I’d calculate a RICE score for both the analytics dashboard and the onboarding flow. Next, I’d map those scores against our current OKRs and the product roadmap to ensure alignment with strategic goals. I’d then validate the scores with cross‑functional stakeholders—engineering for effort, design for feasibility, sales for reach, and support for impact—to surface hidden assumptions. After consensus, I’d choose the feature with the higher RICE score that also satisfies the highest priority OKR, document the trade‑offs, and communicate the decision and timeline to the team. This structured, data‑driven approach balances quantitative analysis with stakeholder alignment, ensuring a defensible prioritization that drives business outcomes.