Product Management is a natural environment for conflict, as product teams comprise various functions, priorities, and areas of expertise. Customer needs and product strategy might be the product manager’s concern, usability might be the designer’s concern, technical feasibility might be the engineer’s concern, or revenue or deadlines might be the commercial team’s concern. All of these ideas and thoughts are good, but they aren’t necessarily aligned.
A team can be failing without there being any disagreement. Conflict, in many instances, can be healthy and help to make better decisions – it can bring assumptions to light, it can uncover potential risks, and it can help teams to assess whether or not a proposed approach or solution really serves the problem. Conflict resolution is therefore an important skill in effective Product Management, alongside strategy, research, prioritisation, and delivery management. Product managers frequently find themselves in situations where it is essential to have people argue with ideas, not each other, and make decisions based on clear evidence, not on who was the loudest.
Separate Product Problems From Personal Disagreements
In Product Management, one of the most valuable skills for managing conflict is keeping the disagreement on the problem and not the people. A designer might think a feature makes the system too complex, and an engineer might think the proposed alternative will take too much development time. The disagreement can be informative if it stays out of usability, technical specifications, or customer benefits. Issues occur when the conversation shifts from “This approach causes technical risk” to “Engineering always blocks good ideas”, or from “Users may find this confusing” to “Design does not understand the business.”
When someone makes a personal accusation, it can make them feel attacked and lower the quality of the conversation. Product managers can help by rephrasing the disagreement in neutral terms. Rather than asking which department is right, they can state the decision, the constraints, and what evidence would help make the decision. There is also a need for certain language. It is better to say that there are several existing systems and that they need to be tested before the proposed release is made than to describe the engineering team as difficult. When it comes to missed deadlines or inadequate communication, the same applies. Teams should identify the behaviour or process that caused the problem, not generalise about people’s competence or attitudes.
Use Customer Evidence and Product Goals to Break Deadlocks
Many product conflicts persist because multiple solutions seem like a good idea, and every team member has documentation that backs their solution. Product Management can bring conversations back to common goals and customer proof to prevent these disagreements. For instance, sales might request a feature because a significant prospect is interested in it, but the product team may think it’s only of interest to a select few customers. Engineering might then point out that it would take a long time to develop the feature.
Rather than letting it become a competition between departments, the product manager can ask more useful questions. Now let’s say that this is a problem for how many customers? How much does it contribute to retention, conversion or satisfaction? What is the cost of developing the program? Does the request fit the existing product line? If the team valued this, what would need to be postponed?
Shared metrics can also be beneficial. If the team has decided that activation is the next goal, a list of ideas can be developed by considering their potential to support activation, not by asking which stakeholder is best able to argue for them. Another valuable reference point is customer research. Evidence cannot be used selectively, as it may reflect internal opinions rather than user needs. It is not the aim of a team to look for data after one member has decided on a specific conclusion.
Clarify Decision Ownership and Team Responsibilities
If no one is clearly in charge of the decision, a conflict can be harder to resolve. Clear ‘decision ownership’ in Product Management can alleviate tension that arises when product teams disagree. It’s good to have everyone in the group talk about it, but not all decisions require everyone’s agreement. A product manager can be responsible for prioritisation, a designer for detailed interaction decisions, and an engineering lead for the technical architecture. Issues arise when roles overlap without a clear division.
Product managers can get too caught up in the technical implementation; engineers can try to make product-priority decisions; or senior stakeholders can skip agreed processes and make last-minute changes. Clear roles help teams know where to contribute and who makes the decisions. This is not to say that the decision owner should overlook other opinions. The key to Strong Product Management is to seek feedback from the people who know the problem best.
It can be helpful first to determine who is making the decision, who will be involved, who will have the final say, and to document the reasons for the decision later. This is particularly crucial when the selected choice is not the preferred one by some team members. If people know the reasons behind a decision and feel their views have been given due consideration, they will be more tolerant of it.
Build a Culture Where Disagreement Remains Constructive
How a team solves their everyday disagreements will dictate how they handle larger disagreements. Product Management leaders can foster collaboration by normalising ‘disagreement’ in the product-development process. Team members should be comfortable questioning ideas and assumptions without hurting their working relationships. Meanwhile, there should be an expectation to explain the why behind an idea rather than dismiss it. Meeting behaviour can affect culture in many ways.
Product managers can create opportunities for quiet team members to join the conversation, ensure everyone is heard, and encourage people to voice concerns before rushing to solutions. Retrospectives can be used as a formal platform to review recurring conflict. When development scope issues keep arising between product and engineering, it might not be about personalities. Requirements might not be clear yet, technical input might not arrive until later, or deadlines might be set before feasibility is understood.
If you can address the process, then the same disagreement will not happen again. Teams also need to be aware that when there is a conflict, they should discuss it privately rather than publicly at a project meeting. Issues of personal behaviour or broken trust may need a more in-depth discussion between the individuals involved. Product managers can encourage direct feedback rather than frustration going through side discussions or private messages.
Conclusion
In Product Management, conflict is inevitable because people have different responsibilities, expertise, and priorities. The goal should then not be to remove differences but to turn them into a productive process. An important beginning is to keep the conflict focused on the problem. Teams may question designs, ideas, and assumptions, or grieve with technical approaches and/or priorities, without making it personal. Shared evidence can then be used to make difficult decisions. Customer research, analytics, product strategy, prioritisation criteria and agreed metrics provide teams with a shared starting point to assess competing ideas.
GET IN TOUCH WITH THE DIGITAL SCHOOL OF MARKETING
Explore product Management success with the Digital School of Marketing. The Product Management Course equips you with essential knowledge and skills to excel in this dynamic field.


