Conflict Is Information. Most Leaders Delete It.

There’s a moment in every conflict where you stop being curious. That’s the moment it stops being a conversation and starts being a battle. Everything after that makes things worse.

A while ago, I found myself in a conflict during a project. The other person was pushing things forward — drafting documents, writing proposals, creating momentum. From the outside, that looks like initiative. Exactly what you’d want.

The problem was that I didn’t want us to move yet. Not because their intentions were wrong. But because I felt we were skipping conversations that mattered. I wanted alignment before action. They wanted action before alignment. Neither of us was unreasonable. And yet — tension.

We were both arguing about the visible layer. The documents, the decisions, the process. Neither of us was looking at what was actually driving the friction. That’s not unusual. It’s the default.

---

The surface layer — and what sits underneath

When leaders are in conflict, the conversation tends to stay at the level of behavior:

“You made that call without me.” “Why didn’t you loop me in?” “That wasn’t your decision to make.”

These complaints aren’t wrong. But they’re symptoms. What sits underneath is usually one of four things: an unmet need, a competing interest, a different priority, or a different working style. Effective conflict resolution in leadership starts by distinguishing between the two — because as long as you’re arguing about the visible issue, the real driver stays invisible.

Understanding which layer you’re actually on is the first diagnostic move. Most conflict conversations never make it.

---

What actually drives most conflicts at work

Three needs show up in almost every workplace conflict. Research on motivation calls them autonomy, competence, and relatedness. In a leadership context, they’re less abstract than they sound — and more recognisable than most leaders expect.

Autonomy shows up when someone goes quiet in a meeting after a decision got made without them. Not aggressive. Just — gone. They’re still in the room. Their investment isn’t.

Competence shows up when someone starts over-explaining, justifying, or getting defensive about work that nobody questioned. The threat isn’t visible yet. But it’s already there.

Relatedness shows up when a normally direct colleague suddenly gets formal. Emails instead of Slack. “As per my last message.” The issue hasn’t changed — but the relationship has shifted underneath it.

You don’t need to name the framework to use it. You just need to notice: is this person arguing about the decision — or about something the decision meant to them?

---

Speed versus clarity — the real tension nobody names

In my case, the conflict wasn’t only about autonomy. It was a genuine clash between two approaches: the other person was optimising for momentum. I was optimising for alignment. Both reasonable. Both completely invisible to each other.

I saw the same dynamic recently in a 1:1 coaching session with a founder. Three years into his company, good team, solid working relationship with his co-founder — suddenly every product decision became a negotiation. On the surface: roadmap priorities. Underneath: he felt his co-founder had stopped trusting his judgment. That’s what we worked on. Once that was named, the roadmap took twenty minutes.

That’s the structural layer. And it’s where most conflict resolution falls short — because it focuses on the human side while leaving the strategic tension unnamed. Once you can see that you’re solving for different things, the personal friction largely dissolves. The disagreement doesn’t disappear. But it becomes workable.

This is Konfliktmanagement in the real sense — not a process for smoothing things over, but the capacity to diagnose what’s actually happening before trying to fix it.

---

Conflict competence isn’t about being nice

There’s a version of conflict advice that says: be more empathetic, communicate better, listen harder. I’ve watched leaders do all of that — and still find themselves back in the same dynamic six months later.

The reason is usually this: they were treating the other person better without understanding what the other person was actually after. Empathy without curiosity about interests is just nicer friction.

Real conflict competence means holding your own position while genuinely exploring theirs — and tolerating the discomfort of not resolving it prematurely. That’s the hard part. Not the conversation itself. The patience to stay in it long enough to find what’s real.

---

One shift that changes most conflict conversations

Before problem-solving, try two questions.

First: What need of mine isn’t being met right now?

Second — harder: What is the other person actually trying to achieve? Not what are they doing. What are they after?

In my experience as a leadership coach in Berlin, that second question is where most breakthroughs happen. Not because it produces an answer immediately — but because it moves you from defending a position to understanding a situation.

Bring one open conflict into your next 1:1 with that question instead of your usual stance. Don’t announce it. Just ask it internally first. See what you notice.

That’s what it looks like when conflict becomes information instead of noise.

---

Leadership Coaching Berlin: working with conflict as a leader

If you’re navigating a recurring conflict — with a peer, a direct report, a board member, or within a team — it often helps to look at it from outside the system. Not to find out who’s right, but to understand what’s actually happening and where the real leverage is.

I’m Niv Nowbakht, Business & Leadership Coach based in Berlin. I work with leaders in Berlin, Barcelona, and online — in German and English. My background combines a Master’s degree in Communication Science with 11+ years of coaching experience and ICF certification. Conflict dynamics are one of the areas where that combination matters most: what people say, how they say it, and what’s driving both.