Prioritizing Competing Work When Team Capacity Is Constrained

How do you decide what to prioritize when your team has more work than it has people, time or budget to deliver? ```hint Judgment over frameworks A scoring method only helps if you can say what it ranks against and what happened to the items that ended up below the line. ``` ### Clarifying Questions - Are you asking about choosing among items on one product roadmap, or about requests from several teams competing for my team's time? - Is the scarce resource engineering capacity, a fixed deadline, or budget? - Would you like my general method, a specific example from my own experience, or both? ### What a Strong Answer Covers - Priorities anchored to explicit goals rather than to who asks loudest - A realistic view of capacity, including committed work, skills and dependencies on other teams - A consistent way to compare value, urgency and effort, applied with judgment rather than treated as an exact score - How decisions, including the work that will not get done, are communicated to stakeholders, and how conflicts are escalated - A concrete example with its outcome and lesson, plus how priorities are revisited when circumstances change ### Follow-up Questions - Tell me about a time you turned down or delayed a request from an executive or a large customer. How did you handle it? - How do you decide how much capacity goes to reliability and technical debt instead of new features? - Two items come out almost even on your scoring. What breaks the tie?