Prioritizing conflicting feature requests from two strategic customers

Two of your most important customers each ask your team for a different feature. How do you handle it, and how do you decide which feature to build? ```hint The ask behind the ask Each request is one customer's proposed solution. Work out what each customer is trying to accomplish and what happens to them if it waits before you compare the two features. ``` ### Clarifying Questions - Are the two VIPs separate customer accounts, or senior people such as two executives at one client or inside our own company? - Does the team have room for only one of these in the next planning cycle, or is the question really about order? - Has either customer tied the request to a renewal, an expansion or a contractual commitment? - How do the two requests relate to the current roadmap and to what other customers ask for? ### What a Strong Answer Covers - Uncovering the underlying problem, users and urgency behind each request before judging the features themselves - An explicit prioritization basis (breadth of need, strategic fit, retention and revenue exposure, effort and ongoing cost) rather than whoever is loudest or biggest - Looking for options beyond "A or B", such as one capability that serves both or the wider customer base, and avoiding one-off custom builds - How the decision is aligned internally and communicated to both customers, especially the one who does not get their feature now - Follow-through: timelines, interim workarounds and how the outcome is measured ### Follow-up Questions - The customer whose request you deferred says they may not renew. What do you do? - Sales already promised one of these features to close the deal. How does that change your approach? - How would you tell whether one large customer's request reflects a broader market need?