Explain Your Method for Ranking Competing Product Requirements

An interviewer asks how you prioritize requirements. Walk through the process you follow when there are more candidate requirements than your team can build: what you take into account, how you compare one requirement with another, how you settle on an order and get others to accept it, and an example of the process at work. ```hint Separate value from timing Before you name any scoring scheme, decide what makes one requirement worth more than another for the product right now, and then ask, as a separate question, what it costs to wait on each one. ``` ### Clarifying Questions - Is this about ordering requirements within one release, or ranking larger initiatives on a quarterly roadmap? - Are some requirements fixed commitments, such as legal, security or contractual obligations, that should be handled outside the ranking? - Does the interviewer want the general method, or the method applied to a product I have worked on? - Whose requests are competing for capacity: customers, sales, support, engineering, leadership? ### What a Strong Answer Covers - How the product's current goals define what counts as value - A repeatable way to compare value against effort that accounts for uncertainty and names the method's limits - Handling of deadlines, dependencies and the cost of waiting - How the order is agreed with engineering and other stakeholders, communicated, and revisited - A concrete example in which the method shapes a real decision ### Follow-up Questions - A senior sales leader insists that one large customer's request goes to the top. How do you respond? - How do you rank work with no visible customer value, such as paying down technical debt or improving reliability? - When would you set your scoring model aside and decide on judgment, and how would you explain that choice?