The same conflict....

There's a pattern that leaders in almost every growing organization recognize, even if they don't call it that. A conflict arises—between two departments, between headquarters and a local office, between an established team and a new management level. It's addressed. Discussions are held, agreements are reached, perhaps someone is let go. For a while, things are quiet. And then the same conflict returns—with different parties involved, in the same place.

Most organizations treat this conflict as a personnel issue. This is understandable, because conflicts have faces. You see the people clashing, hear their arguments, feel the friction. What you don't see is the underlying structure—the decision-making and accountability logic within which these individuals operate. And that is often precisely where the root cause lies.

The symptom is deceptive.

When a conflict disappears with one person and returns with the next, this is the clearest indication that the cause does not lie with those involved. A new person then inherits not only a role, but also an unresolved structural tension—and reacts to it predictably similarly to their predecessor. Not because they have the same character, but because they are in the same constellation.

This applies regardless of industry or size. A hotel group experiences it, caught between corporate guidelines and the individual logic of each property. A growing medium-sized company experiences it, caught between its established core team and a newly appointed management level. A scale-up experiences it, caught between the original founding team and the professionals who join later. And a board of directors experiences it, caught between departments that each act correctly but still regularly clash. Four very different contexts, one identical pattern.

Why both sides can be right

A structurally caused conflict has a telltale sign: both sides see the other as the problem—and both are right from their own perspective. Headquarters acts correctly when it insists on standardization. The site acts correctly when it insists on local specificities. The established team acts correctly when it preserves what has worked. The new leadership acts correctly when it changes what doesn't scale.

When two sides both act correctly and yet clash, it's not a clash of two individuals, but rather of two legitimate logics. This isn't a character problem that can be solved by replacing the two parties. It's a question of architecture—that is, who is authorized to decide what, when a decision is binding, and where the actual boundaries of responsibility lie between the different levels.

The invisible gap

This very structure is often lacking. No one can clearly define who is authorized to make which decision. "We were in agreement" means a binding decision for one side, but a polite gesture for the other. A promise is considered either given or non-binding, depending on whom you ask. In this ambiguity, each side fills the gap with its own assumptions—and these assumptions inevitably clash.

As long as this gap remains unnamed, it remains invisible. Only its symptoms are visible: the recurring friction, the protracted coordination, the escalations that always occur at the same interface. The symptoms are treated—and then one is surprised when they reappear.

Why the distinction matters

The difference between a personal and a structural conflict is not merely academic. It determines whether the chosen solution is effective or ineffective.

If a conflict is truly interpersonal—a question of behavior, competence, or an unfavorable constellation of individuals—then classic management tools come into play: dialogue, development, and, if necessary, replacement. These tools are appropriate and effective when the diagnosis is correct.

If the conflict is structural, however, any personnel measures are ineffective. You replace the person, the tension remains, and the next person ends up in the same situation. What's needed then is not another person, but a clearer logic: explicit decision-making rights, clearly defined boundaries of responsibility, and a shared definition of when something is binding. Work on the structure, not on the behavior.

The costly mistake is misdiagnosis. Addressing a structural cause with personnel costs time, trust, and skilled people—and solves nothing. Conversely, "structuralizing" a personnel issue complicates what a clarifying conversation could have accomplished. The correct diagnosis is the prerequisite for the correct intervention.

How to make the distinction

The honest answer is: don't go with your gut. When you're in the middle of a conflict, you naturally see the people involved first—that's human nature. It helps to ask a few objective questions that shift the focus away from the individuals and onto the situation itself. Does the conflict resurface when the person involved changes? Does it always escalate at the same point of contact? Are both sides acting correctly from their own perspective? Is it unclear when a decision becomes binding? Is the conflict described with labels like "personality" or "chemistry"? Are the boundaries of responsibility nowhere explicitly defined?

The more often the answer is "yes", the more likely the cause is structural — and the less a change in personnel will change it.

We have developed a concise diagnostic framework specifically for this initial assessment: six questions that reveal whether a recurring leadership conflict in your organization is personnel-related or structural. It doesn't replace a full diagnosis, but it highlights areas that warrant closer examination—and prevents you from implementing the same measures that failed last time.

---

→ Receive the diagnostic grid as a free PDF

Six questions that reveal whether your recurring conflict is personal or structural. Applicable to a specific case in your organization — in ten minutes.

Diagnostic Grid