You can’t prevent team conflict at work by hiring nicer people. Harvard Business School recently redesigned its flagship MBA team-immersion program to test what actually works, and the number of teams needing a faculty intervention for serious breakdowns fell from 45 to one.1 Not fewer people. Not softer feedback. A shared vocabulary for how teammates process information, communicate under pressure, and make decisions differently.
That result is getting attention this week for good reason: it matches what most people already sense about their own teams but rarely name out loud.
Most Team Conflict Isn’t About the Work
Two people can agree completely on the goal and still end up in a standoff over how to get there. One wants to talk it through out loud; the other wants twenty minutes alone to think first. One raises a concern the moment it appears; the other sits on it until the meeting, then delivers it as a fully formed critique. Neither is wrong. Left unnamed, though, those differences in pace, processing, and communication style get read as personality conflicts — or worse, as bad intent.
The researchers behind the redesigned program call the fix “interpersonal competence”: the learnable skill of recognizing how colleagues differ before those differences turn into friction, instead of diagnosing them after a project has already gone sideways. It’s a skill, which means it can be built on purpose, on a schedule, rather than left to whichever teammate happens to be the most patient that week.
How to Prevent Team Conflict at Work Before It Starts
Building it isn’t about fixing anyone’s personality. It’s a structure the team actually uses before things get tense, not after.
- Name the differences on purpose. A short, common assessment — Everything DiSC is one option — gives a team plain language for style differences that would otherwise stay invisible until they cause a problem.
- Translate style into working agreements. Knowing a teammate goes quiet and direct under pressure is trivia unless it changes how the team actually runs meetings, gives feedback, or hands off work.
- Revisit it when the work changes. A new project, a new deadline, a new member — any of these resets the pressure on a team, and the agreement needs a refresh, not a rerun of the original workshop.
Skip the third step and the first two stop working. A team that names its differences once and never brings it up again is no better off than a team that never named them at all.
Agreements, Not Assumptions
That second step echoes a principle worth repeating: teams run better on explicit agreements than on silent expectations, and an unspoken style difference is really just another expectation nobody bothered to state. The teammate who “should know by now” that you think out loud, or that a blunt comment isn’t an attack, almost never does. Somebody has to say it.
None of this promises a conflict-free team — nor should it. The number out of Harvard wasn’t zero disagreements; it was one serious breakdown instead of forty-five. The goal was never to eliminate friction. It’s to prevent team conflict at work by catching it while it’s still a difference of style, before it hardens into a difference of trust. What would change on your team if everyone knew, on day one, how everyone else was actually wired?
Notes
- Leonard A. Schlesinger, Joseph Fuller, and Robert V. Toomey, “Prevent Team Friction from Turning into Dysfunction,” Harvard Business Review, June 17, 2026. hbr.org/2026/06/prevent-team-friction-from-turning-into-dysfunction
Leave a Reply