Prioritize a Backlog with Conflicting Stakeholder Demands

In a previous role, I managed a backlog of 30 items requested by four different department heads, each claiming urgent priority. Instead of making unilateral decisions, I initiated a structured prioritization process aligned with our Q3 OKRs. First, I introduced a weighted scoring model focusing on Customer Impact, Revenue Potential, and Strategic Alignment. I worked with each VP to quantify their requests using historical data and projected outcomes. Next, I facilitated a collaborative session where we visualized the trade-offs. For instance, one VP wanted a feature to improve retention, while another demanded a sales tool. By applying our framework, we realized the sales tool had a 40% higher immediate revenue impact but lower long-term retention value. We agreed to prioritize the sales tool for Q3 to meet financial targets, with a commitment to revisit the retention feature in Q4 once resources allowed. This approach ensured transparency and data-driven decision-making. The result was a unified roadmap that satisfied all stakeholders because they understood the 'why' behind the choices. We delivered two major features ahead of schedule, and stakeholder satisfaction scores improved by 25% due to the clear communication of constraints and priorities.