When conflict shows up in an organization, most leaders respond to it as an event.
Something went wrong. People are in disagreement. Now we need to manage it, resolve it, move through it.
That’s a reasonable response. It’s also mostly too late.
Because by the time conflict is visible — by the time it’s loud, disruptive, or landing in someone’s inbox as a complaint — the conditions that made it worse than it needed to be were established a long time ago. The culture that made people afraid to speak up earlier. The undefined expectations that left people navigating by assumption. The relationships that were never built strongly enough to survive honest disagreement.
Healthy conflict isn’t something you manage. It’s something you design — long before you ever need it.
Here’s what makes this complicated. Every person on your team arrived with a different understanding of what conflict means, what’s safe, and how disagreement is supposed to work. Those understandings came from families, schools, communities, and every workplace culture they’ve been part of before yours. Some of them were taught to speak up. Some were told to sit down and be quiet. Some learned that disagreement means something is wrong. Some learned it means something is being figured out.
When all of those people show up in the same room, you’re not starting from a blank slate. You’re laying your version of culture on top of theirs. And the holes don’t always align.
That’s not a people problem. That’s a design problem.
If you want conflict to be productive in your organization, you have to define what it looks like before you have it. What does healthy disagreement sound like? How do we challenge an idea without attacking the person who brought it? What’s the expectation around speaking up — and what’s the expectation around how leadership responds when people do?
Those aren’t conversations you have once at a retreat and check off a list. They’re conversations that happen in the day-to-day, woven into the normal work of leading and operating. The leaders who handle conflict well don’t treat these lessons as separate from the business. They treat them as integrated into it — happening in real time, in context, whenever the opportunity arises.
And when they use accountability, they use it to build, not to punish. Because the moment accountability becomes punitive — the moment it’s used to assign blame rather than understand and improve — it poisons the very culture that makes honest conflict possible.
I’ll say something that leaders don’t always love to hear: a lot of this sounds like kindergarten. Like we’re teaching adults things they should have learned long ago. In a way, we are. But not because people failed — because nothing that came before was consistent or comprehensive enough to give everyone the same foundation. And that’s okay. That’s just honest.
The work of building a culture where conflict is healthy isn’t glamorous. It’s slow, repetitive, and often invisible. But it’s the only thing that actually works — and it always starts before you think you need it.
If this kind of cultural work is something you’re trying to build in your organization, let’s talk.
Photo by Imagine Buddy on Unsplash
