How do you handle conflicting or changing requirements from product sponsors?

1 Clarify the roles and responsibilities

One of the first steps to handle conflicting or changing requirements from product sponsors is to clarify the roles and responsibilities of each party involved in the product planning process. This means defining who is the product owner, who are the product sponsors, and what are their expectations, goals, and authority levels. You should also establish a clear communication channel and a feedback mechanism to keep everyone informed and aligned throughout the product development cycle.

2 Prioritize the requirements

Another key step to handle conflicting or changing requirements from product sponsors is to prioritize the requirements according to their value, urgency, and feasibility. You can use various tools and frameworks, such as the MoSCoW method, the Kano model, or the RICE score, to evaluate and rank the requirements based on different criteria. You should also involve your product sponsors in the prioritization process and explain the trade-offs and implications of each decision.

3 Validate the requirements

A third step to handle conflicting or changing requirements from product sponsors is to validate the requirements with data and user feedback. You should not rely solely on assumptions or opinions, but rather test and verify the requirements with real users and market research. You can use various methods, such as surveys, interviews, prototypes, or experiments, to gather and analyze data and feedback. You should also share the results and insights with your product sponsors and show how they support or challenge the requirements.

4 Negotiate the requirements

A fourth step to handle conflicting or changing requirements from product sponsors is to negotiate the requirements with them and reach a mutual agreement. You should not accept or reject the requirements without discussing them with your product sponsors and understanding their rationale and perspective. You should also not compromise your product vision or quality for the sake of pleasing your product sponsors. You should aim for a win-win solution that balances the needs and interests of both parties.

5 Document the requirements

A fifth step to handle conflicting or changing requirements from product sponsors is to document the requirements and their changes clearly and consistently. You should use a tool or a system, such as a product backlog, a user story map, or a requirement specification, to capture and organize the requirements and their details. You should also update and communicate the changes to the requirements to all the relevant stakeholders and ensure that they are reflected in the product roadmap and scope.

6 Review the requirements

A sixth step to handle conflicting or changing requirements from product sponsors is to review the requirements regularly and evaluate their impact and value. You should not assume that the requirements are fixed or final, but rather monitor and measure their performance and feedback. You should also solicit and incorporate feedback from your product sponsors and other stakeholders and check if the requirements are still relevant, feasible, and aligned with the product vision and goals.