Why the Same Conflict Keeps Happening at Your Organization

Most organizations have a conflict they can't stop having. Different cast, different details, same shape underneath. It produces a particular kind of exhaustion. A kind that won’t show up in any report.

It lives in the hallway conversations after the meeting. In the manager who has stopped bringing certain topics to certain people. In the team that functions, technically, but hasn't had a real conversation in months. Nobody files a complaint about it. Nobody quite knows how to name it. But everyone feels it, and everyone has quietly decided it's just how this place is.

And then someone gets labeled the difficult person.

Sometimes that's true. Sometimes there is a difficult person, and something needs to change. But often, the difficult person is simply the most visible symptom of something the organization built without meaning to.

I've watched this play out from a few different sides: as an employee, as a board member, as a small business owner, and more recently as someone designing conflict resolution programs for organizations trying to understand their own patterns. From each of those vantage points, the same thing keeps becoming clear. The difficult person is rarely the cause. They're the visible end of a chain that runs much deeper into the system.

Don Norman would call it a design failure. I call it the most expensive misdiagnosis in organizational life.

Norman spent decades studying why intelligent, capable people consistently fail when placed inside poorly designed systems. His central argument, developed most fully in The Design of Everyday Things, is deceptively simple. When something goes wrong, the instinct is to blame the person. But more often than not, the system made the wrong action easy and the right action hard. The feedback was missing. The signals were unclear. The environment was set up for failure, and then a human being stepped into it and did exactly what the environment taught them to do.

Norman named two specific gaps that matter here. The first, the Gulf of Execution, is the gap between what you're trying to do and what the system will let you do. Imagine pushing a door that needs to be pulled, or hunting for a button that isn't there. The second, the Gulf of Evaluation, is the gap between what the system is doing and what you can tell about it. Did your action work? What state are things in now? What just happened? Both gaps are where well-meaning people end up struggling inside environments that don't tell them what's true.

Most organizations have never mapped those gulfs in relation to their conflict. They've mapped them for their technology, their workflows, their customer experience. But the human systems get treated differently. How people communicate. How decisions get made. How disagreement is handled or avoided. Those are usually left to chance, personality, and whoever happens to be in the room.

That gap is where chronic conflict lives.

Toyota understood something similar from a completely different direction. Among the principles that built one of the most studied organizational cultures in the world is genchi genbutsu: go and see for yourself. Don't manage a problem from a distance. Don't rely on the report, the secondhand account, or the assumption about what's happening and why. Go see for yourself. Stand where the work actually happens and look at what the environment is asking people to do.

When Toyota applied that principle to production failures, they found that most errors weren't caused by careless workers. They were caused by systems that made errors nearly inevitable. The fix was rarely the person. It was the process that surrounded them.

The same principle applies when a team keeps having the same argument, when a department can't seem to resolve anything without it escalating, when a leader keeps losing good people and can't quite explain why. Go to the source and see for yourself. Not to assign blame. To understand what this environment is teaching people to do.

That question changes everything about where you look.

Here is what I find in organizations with chronic, recurring conflict. Often, something in the design is generating it.

Roles without clear boundaries create spaces where people spend energy protecting turf that was never actually in dispute, because no one defined where one person's authority ends and another's begins.

Feedback channels exist on paper but have never produced a visible result, so people stop using them and start having the real conversations in parking lots and group texts instead.

Accountability applies differently depending on who you are or how long you've been there, so newer people learn fast that the stated standards and the real standards are not the same thing.

Expectations shift without explanation, so people stop making independent decisions and start waiting to be told. Not because they lack judgment, but because the environment has taught them their judgment doesn't stick.

Organizations hire for competence, then build processes that ignore it. Skilled people end up adapting to the system instead of contributing what they were brought in to do.

None of this requires bad intentions. It doesn't even require bad leadership. But it is worth saying plainly. Many of these design failures persist because they benefit someone. Ambiguous roles protect whoever holds informal power. Feedback channels that produce no visible result protect the people who would have to act on what came back. Accountability that applies unevenly is rarely a bug. It's a feature for whoever the system was quietly built to favor. Looking honestly at what an organization has built means being willing to see who it serves.

Which is why this kind of work is harder than it sounds. The people who would need to redesign the system are often the people whose decisions built it. Saying "go and see for yourself" is easy. Asking leadership to look at the source is where the real friction begins, because it requires considering that the source might be them, or the structures they protect.

Norman would recognize the pattern immediately. So would any Toyota engineer who has ever stood on a production floor and watched a process work against the people inside it.

The difficult person, in most cases, is doing something the environment made easy. Avoiding, escalating, withholding, competing. These are rational responses to environments that reward, or at least fail to discourage, them. The solution is not to train that behavior out of individuals while leaving the environment intact. The solution is to look honestly at what the organization has built and ask what it is quietly teaching everyone inside it.

This is harder than sending someone to a communication workshop. It requires a different kind of courage from leadership. The willingness to look at the system rather than the symptom. The willingness to ask what we built here instead of who is causing this.

But it is also more honest. And in my experience, it is the only approach that actually changes the pattern rather than just managing it until it surfaces again.

Norman designed his life's work around the belief that when human beings fail inside systems, the system owes them an honest accounting. That when the design makes failure predictable, redesign is not optional. It is a responsibility.

Organizations that take conflict seriously enough to ask what they built, and what it is teaching people, are the ones that stop having the same conversation over and over again.

That is the work. Not managing people better. Designing systems worthy of them.