Resolve Workplace Conflicts Fairly Without Escalation

I have been running Paperless Pipeline since 2009. Remote since day one. When two people on a small team are in conflict, you cannot wait for it to resolve on its own. There are no hallways, no coffee runs, no shared lunch where the temperature drops naturally. Whatever is tense at 9am is going to be more tense at 5pm.

My approach. I ask each person, separately, the same question. "Tell me what happened, factually, and what you wish had happened instead." No "she always" or "he never." Specific events. Specific desired outcomes. I read my notes back to confirm I have it right.

What I learn nine times out of ten. The two people are not actually disagreeing about the thing they think they are disagreeing about. The surface fight is a missed deadline or an unclear handoff. The actual fight is about respect, or one person feeling overworked, or an old grievance no one has named. Until that underlying thing surfaces, mediating the surface argument is pointless.

Then I bring the two of them together with the underlying thing named out loud, by me, not by either of them. "Here is what I think is actually going on between you two. Tell me if I have it wrong." Putting the unspoken thing in the open removes the political risk for either side of being the one who said it. They can now agree or disagree with my framing without having to attack each other. The conversation that follows is usually about 30 minutes and ends with a small operational change. A weekly check-in. A clearer ownership line. An apology, sometimes.

The approach that keeps me from looking like I am taking sides. I never deliver the framing as my conclusion. I deliver it as my hypothesis. "Tell me if I have it wrong" is the most important sentence in the meeting. It lets either person correct me without losing face. It also lets me be wrong, which I sometimes am.

The mistake I made in the early years was treating conflict as something to suppress. I would tell people to "work it out" and watch the resentment compound. Naming the thing directly, in writing, with both people in the room, is faster and kinder than the alternative.

My default move is to intervene early as a clarifier, not as a judge. When I notice tension building between two people or two teams, the first thing I do is meet with each side separately and ask the same three questions: what specifically happened, what outcome would feel fair to you, and what do you think the other side wants. Almost every time, the gap between the two stories is smaller than either party assumes, and the conflict is being amplified by missing context rather than genuine misalignment of interests. Reflecting that back — here is what I'm hearing from both sides, here is where you actually agree, here is the one real point of disagreement — usually defuses 70 percent of the heat without anyone feeling like a decision was imposed on them.

The approach that has worked most reliably is moving the conversation off positions and onto shared operating principles. Instead of asking "who is right," I ask "what is the rule we want to follow next time a situation like this comes up." That reframes the discussion from a zero-sum personal contest to a forward-looking system design problem the team can solve together. People who were defensive five minutes earlier will collaborate on writing a norm, because the norm protects future-them as much as it constrains current-them.

A few mechanics that keep it neutral: I never quote one person to the other without permission; I summarize the disagreement in plain language and let both sides correct my summary before any decision; I document the agreed-on rule somewhere everyone can see, so the resolution becomes a team artifact rather than a private deal. Fairness, in my experience, isn't about being neutral on the substance — sometimes one side has the better argument and you have to say so — it's about being scrupulously neutral on the process. If people trust the process, they can accept an outcome that didn't go entirely their way and keep the relationship intact.

The approach that's worked most reliably for me when tension grows between team members is what I call the listen-twice principle—I sit down with each person separately, hear them out in full, and then sit with them again the next day before doing anything.

The first conversation is for the surface story. Most people come into a tension conversation with a rehearsed version of what's wrong. They've been thinking about it for days. They'll lay it out cleanly, name a villain, frame themselves as the reasonable party. That version is useful but never sufficient.

The second conversation, twenty-four hours later, is where the actual situation lives. Most people, having said the surface version once and felt heard, will arrive at the second conversation a quarter softer. They'll concede something they wouldn't have the day before. They'll mention a detail that complicates the clean version. They'll often, unprompted, name something they could have done differently. That's the conversation I make decisions from.

The other discipline: I don't take a position until I've done both conversations with both sides. The temptation to align with whoever came to me first is enormous, especially when their version of events is coherent and sympathetic. Almost every time I've succumbed to that temptation in my own clinic, the eventual decision had to be walked back when the other side's version surfaced.

The fair outcome isn't the one that splits the difference. It's the one that emerges after both people have been listened to enough to soften from their rehearsed version. By then, the actual problem is usually visible, and the solution is often something neither person would have proposed on day one.

Listen twice. Decide once. The relationships stay intact when you don't move faster than the listening.

When I see tension building, I step in before it turns into a "who is right" debate. I usually start with separate one-on-one conversations, not to collect complaints, but to understand what each person believes is at risk. Most workplace conflict is not about one email or one comment. It's often about missed context, unclear ownership, or someone feeling ignored.

One approach that has worked well for me is what I call the shared facts, separate feelings method. I bring both sides together and first lock the facts: what happened, what was expected, what was missed, and what impact it had. Then I let each person share how it affected their work, without blaming language. This keeps the conversation grounded instead of emotional.

The fair outcome usually comes from agreeing on the next working rule, not forcing an apology. For example, who owns the decision, when updates happen, and what needs to be documented going forward. That way people leave with clarity, and the relationship stays intact because the focus is on fixing the process, not labeling someone as the problem.

Most workplace tension does not start with bad intentions. It starts with unclear expectations, incomplete communication, and assumptions that quietly grow.

By the time leaders notice visible tension between colleagues or teams, the first disagreement is rarely the real problem. The deeper issue is the story each side has started to tell themselves. One team believes they carry more of the load. Another feels that their concerns are being ignored. Silence is read as resistance. A short response feels like disrespect.

That is why leaders have to step in early. Not to referee. To slow the story down before it hardens.

The approach that has worked for me, as a superintendent and as an executive coach, is what I call a Separate Listening Round before any joint conversation.

The common mistake is pulling both parties into the same room too fast. People perform. They protect. They listen for ammunition. You walk out with a polite truce, but the same tension remains underneath.

A Separate Listening Round works differently. Meet with each person one-on-one, ideally the same day. Ask the same three questions in the same tone. What is actually happening from where you sit? What would a fair outcome look like? What part of this, if you're honest, might be yours to own?

You take notes. You don't react. You don't validate one side. You don't repeat what the other person said.

Before the joint meeting, go back to each one privately with what you heard. Not their words. The pattern underneath. Most of the time, both sides are protecting something reasonable. Workload. Reputation. A standard they care about. Naming that quietly lowers the temperature before the room fills up.

When the joint conversation happens, it is no longer a confrontation. It is an alignment. The relationship survives because nobody was ambushed. The outcome holds because both parties helped shape it.

This is something that I teach through the Loden Trust Framework. Fairness is not created by treating each side identically. It is created when people are listened to, respected, and brought back to a common purpose. Strong leaders don't rush to take sides. They restore the insight before tension turns into identity.

Are you trying to resolve the tension, or are you seen as fair while it resolves on its own?

The first thing is realizing that most workplace tension isn't actually about the thing it appears to be about.

Two teams fighting over roadmap priority are rarely fighting about the roadmap. They're fighting about whose work gets seen, whose judgment gets trusted, who has standing in the room. Stepping into that conversation as a neutral party trying to adjudicate the surface issue misses what's actually happening underneath.

What I do is meet with each person separately before any joint conversation and ask one question: what would need to be true for this to feel fair to you? Not what do you want, but what outcome would make you feel the process was legitimate.

The answers are almost always more reasonable than the conflict itself suggests, and they usually reveal that both parties want versions of the same thing that aren't actually incompatible.

By the time everyone is in the same room, I'm not mediating a dispute. I'm reflecting back what each side already told me they needed and asking whether we can find it together. Taking sides becomes irrelevant when the goal is no longer winning.

I used to think the job was to figure out who was right. I am less sure now. When two people on a team stopped talking to each other, I spent a week trying to establish what actually happened and got two stories that could not both be true. Both people believed theirs completely. Neutrality there is mostly fiction, you cannot step in without someone reading it as a side. What worked was getting them to agree on the next concrete thing that had to happen, not on the past. You skip the history entirely. The working relationship recovered before either of them felt heard, which still bothers me a little because it suggests being heard mattered less than I assumed.

We help founders manage friction with investors too, and the pattern repeats. People want resolution. Mostly they need the thing to keep moving.

Structured Mediation Reduces Emotional Escalation

I think when interpersonal or cross-functional tension starts to emerge within organizations, leaders need to step in early enough to prevent emotional narratives from calcifying into organizational fragmentation. A method that has proven successful at Northwest AI Consulting is to separate emotional interpretation from operational analysis in conflict resolution processes.

Many workplace conflicts fester because people feel personally invalidated before the actual workflow or communication problem is objectively looked at. I normally start by independently holding separate contextual conversations with the parties involved to understand the gaps in perception, the process failures and the underlying points of operational friction. This makes you less defensive and able to communicate more honestly.

Once patterns are identified, I guide the conversation away from competing personal perspectives toward common organizational outcomes. A particularly effective technique is to focus discussions on future operating agreements rather than on retrospective blame allocation. When the conversation is about "how do we improve going forward" versus "who caused the problem," teams are much more collaborative.

Another important factor is consistency of procedure. In conflict situations, workers observe leadership behavior closely and perceived inconsistency is a serious penalty for long-term trust. The best resolutions are when people feel their concerns have been heard in a fair, transparent way and not subject to political favoritism.

Ultimately, effective conflict resolution is less about authority and more about creating psychologically credible processes that restore alignment and operational trust.

You want to anchor your conversation around the deliverable the parties are jointly serving, not on their personalities. Show up, within 48 hours of smelling smoke, and have each side walk you through their timeline/business outcome they are responsible for and where their dependencies from the other side exist.

Fact: 70 to 80% of conflict at work is due to mismatched expectations around handoffs, timelines, or decision rights, not actual disdain for someone. Taking the conflict public next to a whiteboard filled with dates, owners, and inputs changes the game. Be meticulous on this. Positioning falls away and problem-solving kicks in.

Creative Teams Need Space to Feel Understood First

This is especially true in creative environments where tension can arise not from malice but from a high level of caring for work, and communication styles can get emotional when under pressure. At Motif Motion, one tactic that has helped maintain good working relationships is to slow down the conversation early before frustration becomes personal.

When there are conflicts between team members or between departments, I try not to jump into problem-solving mode right away. People are much more willing to cooperate when they first feel like their perspective has been understood correctly. One thing that has worked particularly well is asking each side to explain not just what frustrated them, but what they were originally trying to achieve. Often this shows that both sides wanted similar things but approached the situation differently.

I also tend to try to avoid public conflict resolution when I can. Private conversations offer a safer space for honesty and greatly reduce defensiveness. And another important part is reaffirming that disagreement itself is not unhealthy. Thoughtful dissent can make ideas better, especially in creative work — when it's respectful and collaborative.

The point is to keep frustration from becoming a conflict of personal identity.

I have learned that fairness is not about making everyone equally happy. It's about ensuring that everyone feels respected, heard and treated consistently throughout the process.

In our experience, the fastest way to look like we are taking sides is to interpret emotions. Instead, we focus on being editors of the process for both people involved. We bring both people to a shared document that maps the timeline and friction points. We also record decisions made or avoided to create a neutral reference point.

We end conversations with clear operating rules instead of only apologies together. Each person commits to one behavior to start, one to stop, and one to continue. We agree on a check-in after two weeks to review progress together. This structure makes outcomes visible and helps trust stay strong over time, clearly.

The worst approach to resolving tension between two team members: being the informal intermediary who hears both sides separately and tries to broker a resolution through back-channel conversations. This approach makes you the bottleneck, gives each person a distorted picture of the other's position (filtered through you), and produces agreements that neither party fully owns.

The approach that works: bring both parties into a structured three-way conversation with a clear agenda and a clear goal.

The structure I use at ChainClarity:

1. Before the conversation, ask each person separately to answer one question in writing: "What specific outcome would make this situation workable for you?" Not "what's bothering you" -- what outcome do you want. This shifts both people from grievance mode to negotiation mode before they walk into the room.

2. Open the conversation by sharing both written responses. This immediately establishes that both people have a stake in resolution, not just the person who complained first.

3. Focus the conversation on the gap between the two desired outcomes, not on the history of the conflict. The history is usually less important than people think.

The "not taking sides" piece: I avoid making a judgment about who was right in past interactions. That judgment is usually impossible to make accurately and it makes one person feel vindicated and the other feel accused -- which guarantees future conflict.

What I do take sides on: the behavioral agreement going forward. If we agree that communication happens through a specific channel, I enforce that. Clear behavioral expectations going forward are more valuable than a verdict on the past.

When tension starts building between colleagues or teams, I try to step in before people become attached to a fixed narrative about who is "right." In my experience, most workplace conflict comes from misaligned expectations, communication gaps, or pressure.

One approach that has worked especially well is separating the discussion into two parts: facts first, emotions second. I usually speak with each side individually to understand their perspective, and I focus the conversation on concrete examples, timelines, and shared objectives rather than personalities. That helps people feel heard without turning the process into a blame exercise.

Then, when bringing everyone together, I frame the discussion around solving the operational problem collectively instead of revisiting past frustrations. The goal is not to "win" the disagreement but to restore trust and clarity so people can work effectively again. At Tinkogroup, where we manage distributed teams across different functions and time zones, maintaining that sense of fairness and psychological safety is essential for long-term collaboration.

When tension starts growing between colleagues or teams, I try to address it while the issue is still small and specific rather than waiting until frustration becomes personal. Most workplace conflicts escalate because assumptions build up faster than communication.

One approach that has worked well is focusing the conversation on shared goals and process friction instead of personalities or blame. I usually speak with each side separately first to understand where expectations, communication, or ownership became unclear before bringing people together.

A practice that consistently helped preserve trust was making sure both sides felt equally heard before discussing solutions. People become less defensive when they believe the goal is improving collaboration rather than deciding who is right or wrong.

In many cases, the fair outcome came from clarifying responsibilities, timelines, or decision-making authority rather than forcing agreement on every detail. Clear structure often resolves tension faster than trying to settle every emotional frustration directly.

One tactic I find that almost always safeguards working relationships is divorcing "intent" from "impact" at the resolution meeting. Often times employees feel cornered into thinking that acknowledging negative impact sounds the same as acknowledging intention to do harm, and let's face it, no one wants to be typed that way. So instead I might have each person own up to their operational impact without having to place character judgement on the other employee. This actually defuses the emotional thermometer quite quickly because individuals stop trying to defend who they are and start talking about results. Quite frankly, teams bounce back quicker when the conversation about conflict allows them to walk away with their dignity intact.

The best tool I've found is to disconnect the individuals from the process issue as soon as you can. Conflict between employees tends to escalate when frustration is directed towards a person rather than the workflow, schedule, or responsibility confusion. I always meet 1-on-1 with everyone involved first and have them explain the point of failure using examples rather than assumptions. Making that distinction allows you to focus on the facts and reduces emotional defensiveness instantly.

Equitable solutions are also reached when everyone feels heard before brainstorming. Group meetings are much more effective after each individual has had the opportunity to speak openly and be heard. Folks are also quicker to recover when you clarify expectations and responsibilities in writing afterwards. Minor frustrations that occur over the course of a few months can do more harm than one significant conflict.

I step in early by facilitating a short, structured conversation that focuses on facts and shared goals rather than assigning blame. In interviews I ask colleagues to walk through similar scenarios, and I use that same step-by-step approach in practice to keep discussions calm and clear. I give each person uninterrupted time to explain what happened, ask clarifying questions, and then restate the agreed facts so the conversation stays neutral. From there I help the group identify a small, practical next step and schedule a quick follow-up so we can review progress and preserve working relationships. The most important aspect to maintaining work relationships is communication. Once that goes by the wayside, things can start to deteriorate very quickly.

When there is tension or disharmony among teams or colleagues, there are three things I always try to keep in mind:

1. Which policies & procedures are applicable in that particular circumstance.

2. What are the roles & responsibilities of those involved and how do those things interconnect with the issues that are happening.

3. How do all these different dynamics impact the end goal -- whether that be a desired outcome, quality of services or financial targets.

These guiding principles can help steer the conversation about what formal approaches can be taken to resolve the issues that are occurring. For instance, utilizing a dispute resolution policy is not only a good practice from a potential liability standpoint, but also good in terms of having the process be consistent, impartial (regardless of the parties involved) and outcome-based (i.e., we are trying to resolve this issue by doing x, y and z).

Helping individuals explain and understand each other's roles & responsibilities and perhaps where the discrepancies are stemming from in terms of communications, expectations, etc. is another good way to clarify any misunderstandings and/or misconceptions.

Finally, having those involved understand how all these aspects interconnect and how those things impact the organization's goals, mission and vision -- is vital! It's not only important for people to see things that are affecting them directly (micro-level) but also important to help them zoom out and see how those situations are impacting the bigger picture (macro-level).