When Disagreement Becomes Conflict

Two teachers disagree about how to handle a difficult transition.

One thinks the group needs more structure. The other thinks the children need more flexibility.

They talk about it. They may even disagree pretty strongly.

But disagreement alone isn't necessarily conflict.

Now imagine the same conversation a few weeks later.

One teacher says:

“It doesn't matter what I suggest. We always end up doing it her way.”

Something has shifted.

The conversation may still be about the transition, but the transition isn't the only issue anymore. Now it's also about feeling heard.

Or fairness.

Or respect.

Or something that has happened between them before.

The disagreement has acquired meaning. And that's often where conflict begins.

What We See May Be the Symptom, Not the Cause

When conflict shows up, people usually bring us the part they can see.

“She didn't do what we agreed to do.”

“He changed the schedule without asking me.”

“She never helps with cleanup.”

“They made that decision without including us.”

Those things may absolutely need to be addressed. But sometimes they're symptoms of something else.

“She never helps with cleanup” might be a symptom of: I don't think the workload is fair.

“He changed the schedule without asking me” might be a symptom of: I don't feel like my role is respected.

“They made that decision without including us” might be a symptom of: Decisions keep getting made for us instead of with us.

The conflict isn't imaginary. What happened still matters. But if we only respond to the symptom, we may miss what's actually causing the conflict.

How Did We Get From Here to There?

Sometimes the shift happens because of one significant interaction.

More often, it builds.

A conversation that never quite gets resolved.

An agreement that isn't followed.

A concern that gets dismissed.

A responsibility that repeatedly falls to the same person.

An assumption about someone's intentions.

One interaction gets connected to another, and people begin creating a story about what those experiences mean.

She doesn't respect me.

He doesn't pull his weight.

They don't value what I bring.

Nothing I say makes a difference anyway.

At that point, the team may no longer be arguing only about the situation or what happened.

They're responding to what they believe the situation means.

Look Beyond the Symptom

This is where leaders can make an important shift.

When someone brings us a conflict, it's tempting to start solving the problem immediately.

Who was supposed to do what?

What did the agreement say?

What needs to happen next?

Those questions may eventually matter. But before jumping to a solution, we need to understand whether what we're seeing is the symptom—or the cause.

You might ask:

“What about this is most frustrating for you?”

“Is this about what happened today, or has this been building?”

“What feels most important to resolve?”

The goal isn't to turn every disagreement into something deeper than it is. Sometimes cleanup really is just about cleanup.

The goal is to make sure we're addressing the cause, not just managing the symptom.

A Leadership Pause

Think about a conflict you've been asked to help resolve.

What symptom did people initially bring to you?

And what, if anything, was contributing to it?

Fairness?

Trust?

Feeling unheard?

An unclear expectation?

A pattern that had been building over time?

Before deciding what to do about conflict, it helps to understand what might actually be causing it.

Because if we only address the symptom, we shouldn't be surprised when the conflict comes back.

Coming Next

If conflict can have different causes, it makes sense that we shouldn't approach every conflict the same way.

Next week, we'll look at different types of conflict—and how recognizing what you're dealing with can help you decide what to do next.