Conflict resolution in the workplace is usually treated as a people matter handled by human resources. It belongs on the operations agenda at least as much as on that one. Unresolved disputes between capable colleagues register first as slower handoffs, repeated work and quiet duplication, long before anybody in the business describes the situation using the word conflict.
The Problem Gets Reported as Something Else
Almost nobody brings a dispute to a business owner as a dispute. It arrives disguised as a process complaint, a resourcing request, or a suggestion that a workflow needs redesigning.
The finance lead explains that approvals would move faster with an extra checkpoint. The operations lead requests a separate system so that the team stops depending on data from another function.
Each request is coherent, argued in operational language, and technically reasonable. Each one also exists because two people have stopped trusting each other and are building structure to reduce their exposure.
Owners approve these requests because they arrive sounding like improvements. The business acquires an extra approval stage, a parallel spreadsheet, and a standing meeting that would not have been needed a year earlier.
None of that structure gets removed when the underlying relationship is eventually repaired or when one of the parties leaves. The scar tissue stays and continues charging the business for a fight nobody remembers.
Recognising the disguise is most of the diagnosis. A process request that would not have been made if the two people involved got along is a conflict request wearing operational clothing.
The disguise also explains why these situations rarely reach a formal channel. A grievance procedure catches conduct that crosses a line, and almost none of this behaviour crosses one.
The Fingerprint Left in Everyday Work
Avoidance behaviour leaves marks that can be seen without asking anyone how they feel. The marks appear in workflows, calendars and message threads.
The first mark is the handoff that has quietly lengthened. Work that used to pass directly between two people now travels through a third, and the third person adds nothing except distance.
The second mark is the expanded copy list. Messages between two functions acquire additional recipients, because both parties want witnesses for what was said and when.
The third mark is the record that exists in duplicate. Two teams maintain their own version of the same information, each convinced the other version is unreliable, and reconciling the two becomes a standing task for somebody.
The fourth mark is the meeting that keeps growing. A conversation that once involved two people now requires four, since neither will speak to the other without support in the room.
The fifth mark is the request routed upward. Questions that either party could answer are escalated to a shared superior, which converts a peer disagreement into a queue.
Any one of these marks has perfectly innocent explanations. Several of them appearing between the same pair of functions within the same period is a pattern rather than a coincidence.
Reading these marks requires looking at the shape of work rather than at people. A workflow map drawn today and compared with one drawn a year ago shows the accumulation clearly.
Where the Charge Actually Lands
Delay is the largest and least visible line. Work waits at interfaces while people decide how to approach a conversation they would rather not have, and waiting time rarely gets recorded against anything.
Repeated work is the second line of the charge. Where two functions are not exchanging information freely, each produces its own version of an analysis, and one of the versions is discarded after the effort was already spent.
Error correction is the third line and the most visible. Details that would have been mentioned in a normal working conversation are withheld or forgotten, and the resulting mistakes are found downstream by customers.
Staff departure is the fourth and the most expensive. People rarely resign over a dispute directly, and they do resign over the accumulated experience of working inside one for a long period.
Senior attention is the fifth and the easiest to overlook. Senior time absorbed by adjudicating between two functions is time not spent on anything that grows the business, and that substitution goes unrecorded.
Reviewing where operating problems cluster across smaller businesses shows how often these five lines trace back to a relationship rather than a system. The patterns collected in recent observations of how operating problems present in smaller businesses point repeatedly at interfaces between people rather than at the design of the work itself.
None of these five lines appears on a report with a label attached. They surface as generally slower delivery, generally higher effort, and a vague sense that the business has become harder to run than its size warrants.
Why It Survives Without Being Named
The dispute persists because naming it is unattractive to everyone involved. Both parties usually believe they are behaving professionally, and in most respects they are.
Neither person recognises their own conduct as conflict. Each sees a colleague who is difficult to work with and a set of sensible precautions taken in response.
Owners hesitate to name it for a different reason. Both people are competent, both are hard to replace, and raising the matter risks losing one of them over something that has never been formally complained about.
Colleagues around the dispute adapt rather than report. They learn which topics to avoid, which person to approach first, and how to phrase requests so that neither party takes offence.
That adaptation is what makes the situation stable. The organisation absorbs the dispute into its working habits, and once absorbed it stops looking like a problem at all.
Time makes the situation harder to address rather than easier. A disagreement addressed in the week it appeared is a conversation, while the same disagreement addressed after a year is a renegotiation of how two people have learned to work.
Turnover offers a partial reset and a poor one. When one party leaves, the interface usually improves and the structure built during the dispute survives, since nobody remembers why it was added.
Intervening at the Interface Rather Than the Relationship
Attempts to fix these situations usually aim at feelings. Mediation sessions ask people to understand each other, and understanding is a poor target because it cannot be verified afterwards.
A more reliable target is the interface between the two roles. What passes between them, in what form, by when, and who decides when they disagree.
Those questions have answers that can be written down and checked. They also do not require either person to concede anything about character or intent, which removes the main obstacle to starting.
The conversation works best when it is framed around the work that is stalling. Naming a specific delayed output gives both parties something external to examine rather than each other.
Decision rights deserve more attention than any other element. A large share of persistent workplace disputes exist because two roles have overlapping authority and no stated rule about who prevails.
Structured approaches to handling disagreement between colleagues before it becomes operational damage tend to spend most of their effort on those interface rules rather than on the emotional content. The emotional content usually softens once the ambiguity that fed it is removed.
Sequencing the conversation matters as much as its content. Speaking to each party separately first, about the stalled work rather than about the other person, surfaces the real objection before anyone has an audience.
What Resolution Should Actually Produce
A resolved dispute is recognisable by what disappears from the workflow. The extra approval stage is removed, the parallel record is retired, and the meeting shrinks back to the people who need to be in it.
Those removals matter more than any statement of improved relations. Structure built during avoidance will keep generating work indefinitely unless somebody deliberately takes it out.
Speed at the interface is the second observable change. Requests that used to sit for days move within hours, because neither party is composing carefully before sending.
A third change appears in how questions are answered. Escalations to a shared manager fall away, and the manager notices the absence before anyone reports it.
Cordiality between the two is not the measure of success. Two people can dislike each other and still exchange work cleanly, and that outcome is entirely acceptable to a business.
The target is a working interface rather than a friendship. Setting the bar at genuine warmth guarantees failure and gives both parties an easy reason to declare the attempt unsuccessful.
Treating disagreement between colleagues as an operating matter changes who is responsible for noticing it. A dispute described as a personality issue belongs to nobody in particular and waits for someone to complain. A dispute described as a delay at a known interface belongs to whoever owns that part of the workflow and gets examined during the same review as everything else. Businesses that watch their interfaces find these situations early, while businesses that wait for a formal grievance find them after the structure has already been built and paid for.
Frequently Asked Questions
How can an owner tell the difference between a real process problem and a disguised dispute?
The useful question is whether the proposed change would still be requested if the two people involved worked well together. A genuine process problem persists regardless of who occupies the roles, while an avoidance structure exists to reduce contact between specific individuals. Checking whether the same handoff worked smoothly under previous postholders usually settles it. Where the workflow only became difficult after a particular pairing formed, the workflow is not the issue.
Should disputes between capable senior people simply be tolerated?
Tolerating them is a decision with a running charge attached, and the charge grows rather than stabilises. Senior disputes propagate downward, because teams take their cues about who to trust from the behaviour of the people leading them. What begins as tension between two managers becomes a permanent division between two departments within a year or so. The tolerance option is available and should be chosen knowingly rather than by default.
What is the right moment for an owner to intervene?
As soon as the operational marks appear, which is considerably earlier than the point at which anyone complains. An extra checkpoint, a duplicated record, or a growing meeting between the same two functions is enough evidence to ask a direct question. Early intervention is a short conversation about a specific piece of stalled work. Late intervention requires unpicking habits that both parties now consider normal practice.
Does bringing in an outside party actually help?
Outside involvement helps most where the shared superior is implicated in the dispute or has already taken a side. It also helps where both parties are senior enough that any internal facilitator would be junior to them. The value comes from having someone with no stake in the outcome and no history with either person. Where those conditions do not apply, an internal conversation focused on the workflow is usually faster and less disruptive.
What if one party refuses to engage at all?
Refusal converts the situation from a dispute into a performance matter, and it should be treated as such. Working productively with colleagues is part of the role rather than an optional preference, and someone declining that obligation is declining part of the job. Stating the requirement in those terms, once and without drama, resolves a surprising number of refusals. Where it does not, the remaining decision is about employment rather than about mediation.
How should the outcome of a resolution be recorded?
In writing, as a short description of how the interface will now operate rather than as an account of the disagreement. Recording the emotional history invites both parties to dispute the record and achieves nothing operationally. What needs capturing is what passes between the roles, in what form, by when, and who decides when the two disagree. Reviewing that document a few months later shows whether the agreement held or quietly lapsed.
No comments:
Post a Comment