The Price of Keeping the Peace

There was a time in my life when I confused peace with alignment.

If things felt calm, I assumed things were working.

If meetings were polite, I assumed alignment.

If no one was raising their voice or pushing back too hard, I assumed we were on the same page.

Over time, I’ve learned that this assumption is often wrong in ways that are not immediately visible.

Sometimes what looks like peace is just postponement.

And postponed conversations tend to compound in ways that are difficult to unwind later.

I don’t think I would have described myself as conflict avoidant for most of my career. In fact, I would have said the opposite. Much of my work has involved difficult conversations, negotiation, and navigating disagreement across teams, partners, and customers.

But conflict avoidance is rarely as simple as avoiding confrontation altogether.

More often, it shows up as delay.

Or framing.

Or optimism disguised as patience.

You tell yourself the timing isn’t right yet.

You assume the issue will resolve itself with a little more data or a little more space.

You convince yourself that raising the concern now would create unnecessary friction.

And sometimes, that is true.

But more often than I would like to admit, it is not.

The meeting that said everything except the thing that mattered

A few years ago, I was in a meeting with a partner where everyone in the room understood, implicitly, that the relationship was underperforming.

The data was not ambiguous. The outcomes were not meeting expectations. The friction was not new.

And yet, for nearly two hours, the conversation stayed carefully on the surface.

We talked about reporting structures.

We talked about process improvements.

We talked about cadence, communication, and alignment frameworks.

All of it was reasonable.

None of it was the actual issue.

What stood out to me afterward was not the disagreement we had avoided, but how much effort it took to avoid it. Everyone in the room was intelligent. Everyone understood the underlying problem. And yet, nobody was willing to name it directly.

When we finally did address it weeks later, the resolution itself was not particularly complicated.

What was complicated was everything that had accumulated in the meantime.

By then, the conversation was no longer just about performance. It was also about frustration, misinterpretation, and the assumptions each side had been building in silence.

The original problem was manageable.

The delay made it expensive.

When silence becomes a strategy

I’ve seen a version of this play out with internal teams as well.

In one case, a performance issue with a team member had been recognized early by multiple stakeholders. It was not a question of awareness. People knew there was a gap between expectations and outcomes.

But the conversation kept getting deferred.

Not because anyone was indifferent.

If anything, it was the opposite. People were trying to be considerate. There was a desire to give more time, more context, more support before addressing it directly.

Months later, what could have been a straightforward correction had turned into something heavier. The expectations were no longer aligned. The frustration had grown on both sides. And when the conversation finally happened, it felt abrupt to the person receiving it, even though it had been obvious to everyone else for quite some time.

That gap between private awareness and public silence is where most of the damage tends to happen.

Not in the disagreement itself, but in the time before it is acknowledged.

The illusion of harmony

The part of this that I still find counterintuitive is how often avoidance is rewarded in the short term.

Most environments reward the appearance of alignment.

Meetings that end without friction feel productive.

Relationships that avoid tension feel stable.

Teams that don’t openly disagree appear cohesive.

But absence of conflict is not the same thing as alignment.

It is often just absence of expression.

And over time, that distinction matters.

Because when issues are not surfaced early, they don’t disappear. They accumulate interpretation. They pick up meaning. They start to reflect something larger than what originally happened.

A small gap becomes a pattern.

A pattern becomes a narrative.

A narrative becomes a belief about intent.

By the time anything is said out loud, the conversation is no longer about the original issue.

It is about everything that has been built around it.

The cost we don’t see immediately

What makes this dynamic difficult to recognize in real time is that it rarely feels like avoidance.

It feels responsible.

It feels measured.

It feels like giving things time to settle.

And sometimes it is.

But there is a version of “keeping the peace” that is actually just deferring discomfort in exchange for a larger, less controlled version of it later.

The irony is that most people who do this are not trying to avoid accountability. They are trying to preserve relationships. They are trying to be fair. They are trying to avoid unnecessary damage.

But good intentions do not stop compounding effects.

They just delay them.

A different way to think about conflict

I used to think of conflict as something that needed to be minimized in healthy environments.

I no longer think that is quite right.

The environments that tend to hold up over time are not the ones without conflict. They are the ones where conflict is surfaced early enough that it doesn’t have time to distort into something larger than it needs to be.

The question is not whether disagreement exists.

It always does.

The question is whether it is addressed while it is still proportional to the problem that caused it.

Because the price of keeping the peace is often paid later, in a currency that is harder to recover from: trust, clarity, and time.

Next
Next

"Oh Sure, We'll Figure It Out": What Dick Beedon Taught Me About Building