Conflict Resolution in PM: Techniques and Strategies

Scope of the Topic: The purpose of this document is to provide project managers with guides on the possible techniques and strategies for resolving the conflicts and the disagreements within the teams, and how to succeed in transforming the conflicts in the team to be a catalyst for advancement through applying the techniques to identify the conflicts, use the proven ways to resolve them, and use the techniques in the real world.

Every project team will have conflict, and within any group of individuals, there will always be disagreements, and this is part of group dynamics, whether it be competing with limited resources, a difference of opinions, or conflicts of priorities. The good thing about conflict is not always bad. If carefully managed, it can be a catalyst for innovation and advancement for the team.

Due to differing team member opinions, goals, and differing ways of working, there will be conflicts, and this is part of what is project management. There will be conflicts, and this is part of project management. There will always be tension due to differing task assignments, competing due to deadlines, and resource issues in project management and understanding what project management is can identify conflicts. These tensions should be considered as project management checkpoints, and they indicate features to gaps in the objectives of the project or the requirements of the project. The professionals who have mastered the training provided during the Project Management Professional (PMP) Certification through PMP training will be able to use their skills with the frameworks to address the challenges and or gaps.

When team members have differences in their interpersonal ways and or styles of communication, this is called interpersonal shortcomings, and this is part of task-related conflicts. There is a difference when it comes to conflicts of tasks, as there may be disagreements on the ways of accomplishing the goals of work, or there may be disagreements on work assignments. Conflicts of resources can occur when teams are competing for the limited resources, such as budget allocations, equipment, and human resources. Each conflict scenario will require its own unique approach to solving the conflicts.

Almost all projects have timelines and budgets that need to be adhered to. Conflicts that are unresolved can cause disputes that delay projects, lead to budget overruns, and decrease morale. When unresolved disputes persist, productivity declines, and important members of teams can choose to leave.

Maintaining team cohesion through the proper resolution of conflicts is important. When teams address conflicts positively through collaboration, they end up strengthening their working relationships. Conflict resolution improves communication, and team members develop greater levels of mutual respect. This enables a more cohesive team that fosters a safe space to raise emerging concerns that can become more serious issues.

Innovative problem-solving is another benefit of conflict resolution. Disagreements can, if properly managed, present the opportunity to showcase different perspectives and can lead to better outcomes. Having different viewpoints helps teams think outside the box and come up with new, creative solutions.

The Benefits and Impact of Conflict Resolution

Team Cohesion: Stronger collaboration and trust.

Project Efficiency: Reduced delays and cost overruns.

Problem Solving: More innovative solutions.

Team Morale: Increased satisfaction and retention.

Communication: clearer expectations and feedback.

Resource Allocation Conflicts occur when different teams need to share the same resources. In a software project, two teams need the same developer to fulfil urgent tasks. If this situation is left unchecked, it leads to stalled progress, and team members experience high frustration levels.

Scheduling and Deadline Conflicts explains why this occurs in project task prioritization. There are varying perspectives and timelines. One team wants more time to hit their milestones, while another is under pressure for a quick turnaround. Knowing the types of project risks can help explain the tensions that exist in schedules.

Personality Clashes can exist when team members have different working styles. For instance, a detailed planner might have a problem with a colleague who wants to leave the options open for a more flexible approach. These differences in styles can create misunderstandings, and in the worst case, impact team spirit.

Technical Opinion Differences appear in the more specialized projects. Engineers are notorious for disagreeing when it comes to the selection of tools, frameworks and the best approaches to solving project challenges. If these disputes are not properly facilitated, they can become a major source of project delays.

Unclear roles and responsibilities explain the confusion that occurs about who is responsible for a task, and where a team member's responsibilities end. This can lead to team members working on the same task, and others assuming the work will get done by someone else. This results in frustration and impacts the timelines defined for the project.

For me, catching conflicts before they escalate has been very helpful in preventing disruption. Some signs include:

• Team members ignore each other in meetings
• Lack of participation in discussions
• Passive-aggressive comments or other behaviours
• More formal written communication instead of casual interactions
• Deadlines are being missed without any explanation
• Declines in the quality of submissions

Shifts in communication are a result of brewing conflict. Stakeholders might suddenly become overheads on an email, suggesting a further escalation. The tone of communication becomes very defensive and formal. Collaboration and sharing of information diminish as team members continue to guard information and protect their positions.

Declining performance is also an indicator of underlying tension. Before open conflicts start, there is a drop in productivity, an increase in mistakes, and a rise in absenteeism.

When there is a conflict, a Collaborative Problem-Solving approach in which parties come together to find a solution beneficial to all is encouraged. This approach is most effective when you need a creative solution and when relationships in play are likely to matter in the long run. One such session could involve parties each presenting their situation without any interruptions, after which they can set their focus on the elimination of the underlying issues for the creation of goals and other beneficial solutions.

The other important part of resolving a conflict is Active Listening and Empathy. This means listening without judging. In communication, there is a tendency to explain something to a party so that they understand it. But it is important to first listen, and then repeat what you heard, for the other party to understand and then acknowledge the emotions that are involved. This approach works best when there is a lot of conflict, as it makes people feel as though their side has been heard, and this subsequently opens them to other positions.

To clarify, Finding Common Ground has to do with focusing on interests rather than positions. Instead of demanding an answer to what each party wants, be curious about what each party truly needs. Even when there appears to be a lack of consensus, there may be some overlapping interests worth discovering, and project leadership techniques may help to find these shared interests.

Mediation techniques refer to how, once direct negotiation has failed, a neutral third party may be brought in to help. The third-party mediator guides the discussion, keeps an even hand, and helps the parties find consensus. This is particularly useful for all kinds of interpersonal disputes and strong emotions.

Not every set of circumstances is the same, and each has a different approach. Recognizing these five distinct styles of conflict management helps achieve the desired outcome the most.

In competing, one party makes a strong push to assert its position. This is useful during times of emergency, when quick decisions must be made, and when there are unpopular actions to take. The downside is that excessive use of this approach can lead to the deterioration of relationships.

In Collaborating, the parties seek to satisfy all of their needs and wants. Although this approach can be time-consuming, it is the most favourable outcome in the long run. This approach is most effective in situations that are complicated.

In Compromising, it is possible to find a middle ground to satisfy all of the parties in the short run. This is best when the time is limited. This is a "give and take approach." The limiting factor in this approach is that no one walks away with their ideal outcome.

In avoiding, one party takes a step back from the contention. Sometimes, an issue needs to cool off and gives time for things to resolve on their own. Don't use this approach, as letting problems go unaddressed can increase.

Accommodating means placing relationship maintenance above winning the argument. This tactic works for small issues or when you are wrong. Goodwill is built during an accommodation, which can be used for leverage later.

Conflict should be dealt with immediately. Letting disputes fester is counterproductive, and while you may be concerned about tensions, the sooner you intervene, the better. A private conversation should be scheduled within 24 hours of the conflict.

Interests, Not Positions. Always look beneath the surface of the demands presented to understand the real needs. A person may be requesting a specific team member when, in fact, what is needed is the skill of that team member rather than that person.

Set Specific Ground Rules. Establish a team charter that explains how you will approach your disagreements. You should be specific about the lines of communication, how decisions are made, and how disagreements are escalated. Make sure to review these agreements.

Keep a Record of Everything. Record and keep track of conflicts, conversations, and agreements. This shortcut prevents misunderstandings and promotes accountability. It also helps you identify patterns that need corrective actions and develop other systems.

Consistent Follow-Up. Resolution is a process and involves many steps. You need to supervise implementation, stay in touch with the parties involved, and make changes if necessary. This shows you are committed to the process and prevents any slippage.

The project manager's role is to wear many hats. Sometimes you are the mediator, and you facilitate the conversation. Other times,s you are the coach and teach the team how to resolve issues. Sometimes, you are the decision-maker when a consensus cannot be reached.

Set the tone for your team by modelling the behaviour you want to see. Always act calm and professional. Encourage positive, respect-filled disputes and appreciate when team members work through problems collaboratively. Do not ignore when team members work through problems independently and appreciate that as well.

There is no way to learn the proper way to manage disputes without training. One training that offers good techniques for managing team conflicts is PMP certification training.

There is nothing better than being proactive. One way to be proactive is to use RACI matrices to define roles. This will clear up any confusion surrounding who is Responsible, Accountable, consulted, and informed for tasks, and will avoid disputes.

Keep your team in sync through regular meetings. Encourage openness and concern through safe spaces, and implement anonymous feedback systems if needed.

Make sure to use team-building activities to create personal bonds. Teams that have good relationships are able to feel better about having constructive disagreements as they are willing to extend grace and assume good things about each other.

Give your entire team basic conflict resolution training. Do not wait for conflicts to arise and give everyone basic negotiation, communication, and emotional understanding training. Teams are able to work better together with an understanding of the benefits of project management.

In one instance, I oversaw a software project in which two senior developers argued over differing approaches to software architecture. One promoted microservices, while the other advocated for a monolithic design. Their conflict left the project stalled for a period of two weeks.

I organized a meeting in which each developer would explain their reasoning individually, without interruptions. I was able to steer the conversation towards their common objectives of project scalability, maintainability, and timely delivery. I assigned each of the developers a different approach and asked them to evaluate each one to see how it would achieve the common objectives.

As a result, one of the developers was able to design a microservices architecture for the customer-facing features and the other was able to design a monolithic architecture for the internal tools. Neither of the software developers got their ideal design, but both of them felt that their opinions were valued and were able to accept the compromise. The additional benefit of achieving a timely project delivery was the architecture that both developers were able to support.

There are several metrics that can be used to evaluate the success of a compromise. One such metric involves measuring the time it takes to resolve a problem, which extends from the time it is identified to the time a resolution is achieved. Other metrics include monitoring the recurrence of the problem, which can be used to identify systemic problems, and conducting periodic satisfaction surveys to evaluate the health of the organizational climate.

The most apparent success of a compromise is an increase in team productivity, which is usually accompanied by improved communication and collaboration, and a reduction in the time it takes to complete a given project. These are the objectives that project managers are most interested in achieving. When a project is completed on time, team members are likely to experience improved morale and project stakeholders will feel more confident in the project leadership.