Last time, we talked about why we avoid conflict — and why that avoidance tends to cost us more than the conflict itself. If you missed it, you can find it here.
This week, I want to offer you a reframe. Because I think many of us have been operating with a fundamentally flawed belief about what conflict means. And once we shift that belief, we open up way more possibilities.
If you get to the end of this article and think you might benefit from a conversation about how conflict is harming your organization, reach out. I’d be delighted to help.
Conflict Isn’t a Problem. Silence Is.
A few years ago, I was invited in to work with a team that was struggling. The manager was frustrated. Morale was low. Everyone was working in silos, going around each other quietly.
“Nobody ever pushes back on anything,” she told me. “I can tell that they aren’t happy, and our clients are starting to notice. But I can’t get them to talk to each other.”
She didn’t have a conflict problem. She had a lack of conflict, or a silence problem.
The conflict was still there — it was just happening in hallways, in hushed side conversations, and in the quiet resentment of people who felt that they couldn’t use their voices without retribution. The tension didn’t disappear because nobody named it. It just became murky. And murky problems are the hardest ones to solve.
What Productive Conflict Actually Looks Like
When most people picture conflict, they imagine raised voices, hurt feelings, or maybe someone storming out of a room. Those are things that happen when we’re engaged in unproductive conflict. It’s not what we’re aiming for.
Productive conflict looks more like this: two people with different perspectives are both willing to say what they actually think — and both willing to listen. There’s disagreement. There might be some discomfort. But there’s also something getting worked out that really needs to be worked out.
Productive conflict is how teams make better decisions. It’s how blind spots get discovered. It’s how the person who sees the problem no one else is talking about finally gets to say, out loud, “I think we need to look at this.”
Silence, by contrast, is how teams make the same mistakes over and over again. Team members disengage. Morale drops. People feel like speaking up is too risky, either to the relationships involved, or too risky to the outcomes that need to be achieved. We don’t speak up because we’re trying to manage that risk.
The Research Is Clear
Patrick Lencioni’s work on team dynamics identifies the absence of trust as the foundational dysfunction of any team — and he defines trust not as “believing people are nice” but as feeling safe enough to be vulnerable. To admit when you’re wrong. To disagree. To say the hard thing.
Google’s Project Aristotle, one of the most cited studies on team performance, found that psychological safety — the belief that you won’t be punished for speaking up — was the single strongest predictor of team effectiveness. Not talent. Not resources. Not experience. Psychological safety.
What that research tells us is simple: the teams that can have hard conversations are the teams that perform. Not despite the conflict, but because of it.
Conflict as a Signal
I invite you to try something. The next time conflict surfaces on your team, instead of bracing for impact, get curious. Ask yourself: What is this conflict really about?
Here’s a two-step process that can help you navigate:
1. Clean up the relational static. Separate intent from impact.
For example, let’s say someone is pushing an idea really hard in a meeting to the point it shuts down the conversation. You might want to call out the behavior. Instead, try acknowledging that this person most likely had good intentions and was passionate about their idea. And then name the impact, which was that the other team members stopped talking because no one felt like they could finish a thought.
2. Re-anchor the work. Make it about the decision, not the person.
Following the same example above, ask some questions. What decision are we trying to make? How can we make sure everyone has a chance to ask questions and give input in order to feel ready to make that decision? By when does this decision need to be made?
Because conflict without a decision inevitably leads to frustration. And frustration breeds disengagement. And that’s where silence lives.
What Leaders Can Do
If we want teams that can navigate conflict well, we have to model what it looks like to do that. That means inviting dissent while also seeking a balanced view of the problem in front of us. Here are a few questions that might prove useful:
“If we go in this direction, what are all the ways it could go right?”
“If we go in this direction, what are all the potential risks?”
“What else do we need to feel ready to make this decision?”
“What have we not considered?”
It means letting people speak their true opinions and perspectives — even when it’s uncomfortable. Especially then. Because if we don’t make space for people to share those things without cutting them off or cutting them down, we are inadvertently training them to stay silent.
It also means being willing to be wrong. Publicly. Out loud. Because nothing signals psychological safety faster than a leader who says, “You know what, you’re right. I hadn’t thought about it that way.”
Bottom line?
Conflict isn’t the enemy of a healthy team. It’s the evidence of one. When people feel safe enough to disagree, to name what isn’t working, to push back on ideas — including yours — that’s not dysfunction. That’s exactly what you’ve been trying to build.
The goal isn’t a team without conflict. It’s a team that knows what to do with it.
Next time, we’ll get practical: simple, concrete ways to engage with conflict when it shows up — so you can move through it instead of around it.
Talk soon, Ellen
Want to learn more about how I support and work with clients? Let’s chat. Booking now for spring 2026.
