Team friction
Team Friction Isn't Failure — It's Information
Quick answer: Most recurring team conflict isn't a character problem — it's a combination problem: two reasonable working styles that spark under specific conditions. The fix is to depersonalise: move the problem from "you" ("you're too slow") to the pairing ("we're a fast–slow combination — how do we manage that?"). A problem owned by a combination can be managed; a problem pinned on a person can only be resented.
When two people clash repeatedly at work, everyone around them quietly picks a side: one of them must be the difficult one. Here's the pattern worth noticing first: the same "difficult" colleague is often no trouble at all with a different partner. If the person were the problem, the problem would follow them everywhere. It doesn't — because what you're watching is usually a combination reacting to context, not a character flaw.
Why "who's right?" is the wrong question
Adjudicating a clash produces a winner, a loser, and a grudge — and changes nothing structural, so the same pair sparks again next quarter. The productive question is different: what is it about this pairing, in this situation, that predictably produces heat? Fast versus deliberate. Big-picture versus detail. Blunt versus diplomatic. Challenge versus harmony. None of these styles is wrong; certain pairings of them are simply flammable under deadline pressure.
The depersonalising move, step by step
- Name the pattern, not the person. "We're a fast–slow pairing" replaces "you drag your feet". The first is a fact about a combination; the second is an accusation.
- Locate the trigger context. Most flammable pairs are fine 80% of the time. Find the 20%: deadlines? ambiguous ownership? public settings? The context tells you what rule to write.
- Write one small rule. Not therapy — logistics: "big decisions get a 48-hour buffer"; "handovers go in writing"; "we disagree in private, align in public."
- Review the rule, not the relationship. A month later, ask whether the rule held. If it did, credit the pair. If it didn't, adjust the rule — still no verdicts on persons.
Managers report the strangest thing about this move: the two people often start defending each other — because the enemy is now the combination's pattern, and they're on the same side against it.
Seeing the whole map at once
Doing this pair by pair, reactively, is slow. A team map generates the full picture upfront: every pairing in a team of 2–20 flagged for natural affinity, mutual support, or pressure-point tension — each flag with a discussion card for how that combination is managed. Teams typically bring it to an offsite (agenda template here) and open with one question: does this ring true for us? For the two-person founder version of this problem, see co-founder compatibility.
FAQ
Is all team conflict just a combination problem?
No — boundary violations (personal attacks, sabotage, disrespect) are behaviour problems and need direct management. Depersonalising applies to the far more common case: two decent professionals who repeatedly grind.
Doesn't this let people avoid accountability?
The opposite. Vague blame ("be less difficult") is unactionable; a combination rule ("48-hour buffer on big decisions") is a commitment you can hold both people to.
What if one person refuses to engage?
Start asymmetrically: agree the rule with the willing party and model it. Rules that visibly reduce friction recruit the sceptic faster than persuasion does.
elematch turns the five-element framework into a shared team language — the friction matrix flags every pairing's affinity and tension on one page. Generate your first team map free →
Last updated: July 2026.