The organization behind the org chart
Every company has an official version of itself: an org chart, job titles, meetings, and statements about its culture. But the way authority actually works becomes clearer when a disagreement reaches the table. Who makes the decision? Who avoids it? Who keeps the work moving while everyone else waits? Conflict exposes whether responsibility follows authority or whether the two have been kept apart by arrangements no one has had to explain.
I see conflict as a test of the organization. That does not mean every disagreement is useful or that people should work in a constant state of confrontation. A difficult situation can, however, reveal dependencies that ordinary routines have concealed. A friendship may have stood in for a decision. Someone may have absorbed work that had no clear owner. Silence may have allowed incompatible expectations to coexist.
When those accommodations stop working, what looks like a problem between people can also reveal a management choice. The disagreement matters, but so does the arrangement that allowed it to develop.
Define the question beneath the dispute
Imagine business partners arguing over an expense. One emphasizes caution; the other emphasizes growth. They may genuinely disagree about how to use the company's resources. But they may also be unsure who has the authority to commit those resources in the first place. Unless that uncertainty is addressed, the next expense can become another setting for the same argument. Approving or rejecting a particular request does not necessarily settle the question of who gets to decide.
That possibility is not a license to assume hidden motives. Looking for interests is different from inventing psychological explanations for someone else's position. The person leading the conversation can ask what each side wants to protect, what consequence each fears, and what information each considers necessary. Those answers deserve to be heard and tested against the actual problem. The negotiator's interpretation should not automatically replace the explanations of the people involved.
This is where I would begin: what happened, what did each party understand the agreement to be, and what decision needs to be made now? Those questions give emotion a context without allowing it to determine the outcome on its own. Someone can be frustrated and raise a valid objection. That same person can also be frustrated and demand a solution the other side cannot reasonably accept.
Responsibility needs room to act
A company becomes particularly difficult to manage when someone is accountable for a result but cannot decide on the conditions needed to achieve it. Conflict makes that gap visible. Asking for more commitment may sound decisive, but it does not supply missing information, resources, or authority. Before treating a problem as a failure of effort, I would want to understand what the person was actually able to do.
The reverse deserves equal attention. Someone who retains control over a decision cannot step away from its consequences simply because someone else carried out the work. If a direction changes, a priority shifts, or a promised condition never materializes, that intervention belongs in the assessment of the result. Holding a team responsible for what it could not control may end the current argument while preserving the cause of the next one.
None of this removes individual responsibility. A person can have clear conditions and still fail to honor an agreement. Someone can withhold information or exploit ambiguity. The distinction is whether that conclusion follows an examination of the commitment and the events, or whether it was chosen as the explanation before the conversation began. A rigorous assessment protects the organization without needing an accusation as its starting point.
Agreement has to change the work
Some conflicts are closed by shifting their cost onto whoever has the least power to keep objecting. The meeting ends, everyone agrees to move forward, and someone continues carrying the very condition they came to discuss. That silence can be mistaken for understanding. To judge a resolution, I prefer to ask what has changed in the work and what difference each party will be able to recognize after leaving the room.
Consider a hypothetical team that accepts requests from another department outside the usual process. If the proposed solution requires the team to keep absorbing every exception while no one takes responsibility for the underlying problem, the agreement may bring temporary relief without improving cooperation. The conversation needs to address what makes an exception permissible, who authorizes it, and how its effect will be observed.
Goodwill should not be treated as an unlimited resource. An agreement needs to address the condition that created the difficulty, especially when the same people are expected to keep absorbing its consequences.
Listen carefully, then make the decision
The strongest objection is practical: a company cannot turn every disagreement into a lengthy investigation. I agree. The depth of the review should match the importance of the decision and its consequences. Some situations need only a brief clarification. Others require a closer look at responsibilities or a conversation with people who have not yet been heard.
What does not help is treating every difficulty as an emergency that leaves no room for understanding, then wondering why the same discussion keeps returning. Speed alone does not resolve an unclear commitment or a disputed boundary of authority.
When consensus is out of reach, someone with the authority to decide needs to make the choice. That person should explain the criterion used, what is now expected, and what circumstances would justify revisiting the issue. Delaying a decision simply to avoid an uncomfortable reaction can prolong the conflict and allow contradictory informal commitments to take hold. Listening prepares the decision. It does not remove the obligation to make it.
Recognize when a working relationship has reached its limit
Some relationships need to be reorganized or brought to an end. I do not argue for keeping them intact at any cost. I argue for handling a separation, a change in responsibilities, or a revised commitment with attention to the people, the work, and the professional requirements of the situation.
Recognizing that a relationship has reached its limit does not justify turning everything that came before into an argument over the worth of the people involved. A decision about whether an arrangement can continue should be handled with the same care used to understand why it stopped working.
Authority becomes credible through accountability
After a decision, the company should be able to learn something. Which responsibility was unclear? What information arrived too late? Which agreement allowed incompatible interpretations? If the only conclusion is that someone was difficult, the organization loses an opportunity to correct a condition that could produce another conflict with someone else.
Learning from a dispute does not require ignoring individual behavior. It requires examining the conditions under which that behavior had consequences as well. The assessment remains incomplete if it stops at a person's conduct without considering the commitments, information, and authority surrounding the work.
A company reveals how it is governed when it must choose between preserving the appearance of harmony and addressing a difficulty clearly. The person who truly holds authority is not simply the person who can bring the meeting to a close. It is the person willing to answer for the decision, prepare for its execution, and check what changed.
Authority gains substance when people understand what has been asked of them, how much room they have to act, and where to turn when that room is no longer sufficient. That is the connection between power and responsibility that conflict puts to the test.