Prioritization and Trade-Off Decisions Questions

Making and defending a ranked decision about what to work on among competing options under conflicting goals, incomplete data, and time pressure. Covers explicit prioritization frameworks (RICE, ICE, MoSCoW, Kano, weighted scoring, impact vs effort, cost of delay, WSJF) and how to make their inputs honest: handling low-confidence estimates, testing whether a ranking is stable, and guarding against gaming, sponsor seniority and recency bias. Also covers backlog and request triage, feature and scope trade-offs, technical debt, reliability, security, compliance and accessibility work versus new features, large-customer and sales-driven requests versus the roadmap, sequencing a limited set of options, urgent interruptions and incidents versus planned work, deciding whether a single initiative on the list should continue or stop, saying no or not now and communicating a deprioritization, documenting a call and later checking whether it was right, and the governance and escalation used to settle prioritization disputes. Assesses whether a candidate can make and stand behind a defensible call rather than treating everything as equally important. Excludes architecture and technology-selection trade-offs, supplier and sourcing decisions, experiment and metric design, portfolio budget and headcount allocation, and delivery trade-offs inside an already committed project.