I have experienced working in a project team where team members have had interpersonal issues in the past. The first step to solve this is for the Project Manager to address the conflict in a private meeting and focus on discussing shared project goals and how personal differences can be set aside. During this meeting, the project manager and team member should each have space to explain their perspectives and concerns. When I had conflict with a team, the main issue was unclear expectations from the team leader. Having this type of meeting allowed for the leader to redefine each team members roles and responsibilities, leading to a more collaborative team environment as we finished the project. If the project manager is unable to resolve tension amongst the team through conversations, having a meeting with the team and a neutral third party, such as someone from HR, could help to reframe the discussion around how mutual goals for the project can be completed. In order to prevent any further impact to the project timeline, the project manager and team together should establish standards for how disagreements and conflicts are resolved going forward.

I’ve seen similar situations too, and I think the biggest shift comes from moving the conversation away from “who’s right” and toward “what’s best for the project.” One effective approach is setting clearer boundaries around roles and decision-making, so technical experts feel respected while the project manager still maintains overall direction. I’ve also noticed that regular, low-pressure check-ins can help surface concerns early, before frustration turns into open conflict. In some cases, having both people collaborate on a shared deliverable can rebuild trust because it forces them to see each other as partners rather than obstacles. Ultimately, when both sides feel valued and understand how their strengths contribute to the bigger picture, the conflict often becomes a source of better ideas instead of a threat to the project timeline.

The emphasis placed on shifting the focus away from personalities and back onto the project itself is really good point that was made. To seg28's point, clarifying expectations and roles early is huge, many conflicts aren't personal but instead are the result of in the moment, small frustrations that build up between team members and comes out as conflict or argument. Sometimes, private one on one conversations are the least disruptive way to reset that. Sami also brings up a good point of shared deliverables which 'force' collaboration between people working on the project as it shares responsibility more evenly and can build camaraderie between workers. 
One point that's missing however is the the use of team leads below project managers. In my experience, a team lead can be an additional effective tool used by project managers to better delegate how work can be completed. A team lead can introduce a more personal team member who can solve more intricate problems that a project manager may not have time to deal with (depending on the scale of the project). In this sense, team leads can actually be used as an extension of a project manager while being a more accessible and relatable person who can be used to reduce conflict issues within a team. 

I certainly agree that most interpersonal conflict may arise from misalignment rather than dispositional differences. Misalignment may stem from expectations or from the styles of communication employed. Thus, PMs should first try to understand the root cause of the conflict rather than just address the "symptoms." Based on my experience, role clarity could be a key factor in these situations. 

At times, skilled technical contributors/team members may feel frustrated when their expertise is not given due respect, while, on the other side of the coin, PMs may perceive contributions with a certain tone as hostile or rooted in anti-authority sentiments. In such a case, a private, structured conversation may be effective, as mentioned in a previous post, as it enables all parties to articulate their concerns without defensiveness. Then, grounding the discussion in shared project goals would also be critical and help guide the process forward. 

Overall, in terms of choosing who should adapt more in certain scenarios. I am curious what people think about how much responsibility should fall on project managers to adapt, as compared to team members. 

When a conflict between a project manager and a highly skilled member of the team arise, it's important to understand there isn't always a one size fits all. In one aspect, it depends on the competence of either member, but assuming they are equally so, one method could be to get a mediator between them. Being able to neutrally think on what the best solution is could help qualm scenarios like this. Additionally, as the project manager, you are taking a leadership role, so it would be beneficial as well to discuss with the other team members perhaps how certain decisions would affect them. With that said, it is important in these discussions to not mention the conflict and to keep it professional through and through. Lastly, but perhaps the most important, could be to formalize pathways for decision making, marking when technical leadership overrides that of managerial authority (and vice versa). Communication is probably something that should be practiced as well in these sort of environments too.

Another angle is that ongoing conflict can sometimes point to a process issue rather than a people issue. If a project manager and a highly skilled team member keep clashing, it may mean there isn’t a clear or consistent way for technical concerns, or disagreements to be raised and resolved.

In one group project I worked on, tension dropped noticeably once we defined how and when technical disagreements were formally discussed, instead of being debated informally during deadlines. That shift helped keep disagreements from feeling personal and made them part of the workflow instead. Instead of trying to change personalities, adjusting the system helped keep both leadership and technical expertise without hurting the project timeline.

As an individual within a project team who was in direct involvement with team conflicts, I believe that engaging all members is important to relay the situation at hand and come to a swift conclusion. I have come to learn personally that communication is absolutely key to the progression of projects within a timeline, and a certain individual I was partnered with in leading a project ended up contributing little to its development and resulted in missing key deadlines for LT stakeholders.

In conjunction with other posts on how mediating tension within teams in a professional manner while also being direct is important, I would like to add that keeping all discussions documented is essential when leadership escalation is needed. For example, my project partner's continued lack of effort within the project was later documented by myself and our team manager via email in order to push for development for the project, with major progress following all efforts made by the team. My personal project experience has thus further solidified my position that communication is king to the success of a project.

I don't have direct experience working with a project manager but I do have experience with dealing with problems that have do with my job at target between be and the upper management to either miscommunication or problem that within the team. When there is tension it can sometime be hard to slice or cut in a way that doesn't end upsetting at least one person in some reguard. But the hard conversation must happen to ensure that the problem is solved and can create for less tension or for a better work environment for everyone else. Rather then blaming people or placing blame, it can allow for a better solution to be found and talking through problems can allow for the problem to either solved or more manageble for everyone to find one or more solution. When there is no comunicaiton it can lead to further problems and can result in one or more people to not get their job done on time and for futher team problem later and a no trusting environment. 

Team conflict with a project manager often arises from unclear expectations, communication gaps, differing priorities, or perceived micromanagement, especially in interdisciplinary environments like biomedical projects. Such conflict can lead to reduced trust, delays, and lower team morale if not addressed early. An effective project manager should handle conflict by actively listening to team concerns, clarifying roles and goals, acknowledging expertise across disciplines, and facilitating open, respectful dialogue rather than imposing authority. By focusing on collaboration, transparency, and problem-solving instead of blame, a project manager can turn conflict into an opportunity to strengthen team alignment and improve overall project performance.

First, communication should be a priority. Both the team member and the project manager should explain all their reasoning as to why they feel a particular way. The PM may have some company data that the team member does not know about, which may be affecting their choices, while the team member my have past experience with similar cases and may predict a specific outcome.

Please ignore the odd formatting on the second section of my post. I am unsure as to why that paragraph is aligned to the right side.

Yes, I have encountered situations like this in some project teams in my past. They have arisen in teams where all members already knew each other, but most commonly when the team members weren't acquainted with each other prior. Group dynamics and roles are unfamiliar at this point, and conflict early on is predictable as a louder presence often takes on team-leading positions. Quieter members are then often overshadowed and don't find a means of getting their opinions across. Team members may pick sides, or members may be in constant disagreement, slowing project progression and leading to ineffective team discussions. In my experience, the best approach is to discuss these concerns with the entire team, including the team leader, as they arise and frequently in scheduled group meetings. Don't attempt to corner a single member as the problem, because it often doesn't lead to a productive conversation and may push them to argue defensively. Have the project in mind and the goals set straight, bring up your points, and explain why they present a better approach. Then attempt to reach a group decision. This isn't easy and isn't a one-and-done solution, but without addressing your concerns openly and professionally, the project is harmed. That said, as a team member on neutral ground, how do you approach these disagreements? How can you mediate a calm and open conversation if the opposing parties choose not to initiate? 

An intersting extension to the proposed question gk376, the best way to mediate such an opposing conversation is to do just as you had said, stay neutral. Ultimately any dispute between an expert in the field and a project manager should fall in the direction of the PM as the primary leader of the project. In most cases the PM would have authority over others working on the project; while ideally the PM would take the points of their experts into consideration when deciding the next course of action, this is not always the case. To help that expert mediate the disagreement as a neutral party, perhaps the best solution may be to present the expert's opinion in a manner that is easier to digest for the PM. When people clash regularly they are less likely to submit to one another, knowing that you can intervene as a third party to help push for what is best for the project on either end. This kind of interpersonal dispute management will inevitably make you a better project manager in the long run, or make you better suited for the role if you are not in it yet.