Why Organizational Friction Is Usually a Leadership Problem
The meeting had become predictable.
Sales explained that Operations was moving too slowly.
Operations explained that Sales kept changing what customers needed.
Finance raised concerns about commitments being made before the economics were understood.
The project team tried to reconcile the different positions and left with another set of actions.
Everyone agreed that cross-functional collaboration needed to improve.
So another meeting was added.
For a while, the additional coordination helped. People had more visibility. Issues surfaced earlier. Leaders had another place to escalate decisions.
But the underlying tension remained.
Sales was still optimizing for responsiveness.
Operations was still protecting consistency and capacity.
Finance was still trying to preserve economic discipline.
Each function was doing what the organization expected it to do.
The friction wasn’t being created by people who refused to collaborate.
It was being created by reasonable leaders operating within a system that had never resolved how competing priorities should be balanced.
The problem appeared between functions.
Its origin sat above them.
Where friction becomes visible
Organizational friction tends to appear at boundaries.
Between Sales and Operations.
Between Marketing and Finance.
Between Product and Technology.
Between a corporate function and a business unit.
Between the people making commitments and the people responsible for delivering them.
These boundaries receive a great deal of attention because that is where the symptoms become visible.
Work slows as it crosses from one team to another. Decisions require escalation. Meetings become larger. People begin copying additional leaders on emails. Functions create processes to protect themselves from surprises.
Eventually, someone concludes that the teams need to communicate better.
Sometimes they do.
But communication cannot resolve a trade-off the leadership team has never made.
Collaboration cannot clarify ownership the leadership team has left ambiguous.
Trust cannot eliminate the tension created by incompatible goals.
When teams are asked to solve unresolved leadership questions through day-to-day coordination, friction is not an exception.
It is the operating model.
Reasonable functions can create an unreasonable system
Most functional leaders are rewarded for doing their jobs well.
Sales should advocate for customers and growth.
Operations should protect quality, feasibility, and reliable delivery.
Finance should ensure that commitments make economic sense.
Human Resources should consider organizational capability and risk.
Technology should protect security, scalability, and technical integrity.
Each perspective is necessary.
The difficulty begins when leaders assume that functional excellence will naturally produce organizational alignment.
It rarely does.
A decision that is best for one function may create costs somewhere else. Speed may reduce certainty. Standardization may limit responsiveness. Efficiency may restrict experimentation. Local autonomy may weaken consistency.
None of these tensions has a universally correct answer.
They require choices.
When the leadership team has not made those choices explicit, functions make them independently.
Each team applies its own priorities, measures, experience, and understanding of risk. Each decision can be entirely reasonable within the function and still create friction across the organization.
What looks like territorial behavior may actually be people fulfilling different versions of the same organizational expectation.
The questions hidden inside the friction
Repeated friction usually contains a question the organization has not answered.
Who has authority when customer responsiveness conflicts with operational feasibility?
When does an enterprise standard take precedence over the needs of an individual business unit?
Which matters more in this situation: speed, consistency, cost, or risk?
Who owns the outcome when the work crosses several functions?
What can one leader decide independently, and what requires collective agreement?
Without clear answers, these questions do not disappear.
They are negotiated repeatedly—project by project, meeting by meeting, and escalation by escalation.
The organization may believe it has an interpersonal problem because the same people keep disagreeing.
Often, those people are carrying a structural disagreement the leadership team has never resolved.
Replacing them may change the tone of the conversation.
It will not necessarily remove the tension.
Why more coordination is not always the answer
When friction increases, organizations often add mechanisms intended to improve coordination.
More meetings.
More approvals.
More steering committees.
More detailed processes.
More people included in decisions.
These responses are understandable. They create visibility and reduce the risk of someone being surprised.
They can also make the organization slower without making it clearer.
A larger meeting does not determine who owns the decision.
An additional approval does not resolve competing priorities.
A new process does not explain which trade-off the business is willing to accept.
Coordination is valuable when people understand the operating choices within which they are coordinating.
Without that clarity, coordination becomes the way the organization repeatedly negotiates questions that should have been answered elsewhere.
Friction as information
Organizational friction is not always something to eliminate.
Some tension is healthy. Different functions should bring different perspectives. Leaders should challenge assumptions, surface risks, and protect important interests.
An organization without tension may be avoiding the conversations it most needs.
The more useful question is not:
“How do we stop these teams from disagreeing?”
It is:
“What unresolved leadership choice keeps forcing these teams to negotiate the same issue?”
That question changes how friction is understood.
Instead of treating tension as evidence that people are difficult, it treats tension as information about the system.
A decision that repeatedly escalates may reveal unclear authority.
A handoff that regularly fails may reveal different definitions of success.
A conflict between functions may reveal an unresolved strategic trade-off.
A project that needs constant senior intervention may reveal that ownership was never truly established.
The friction points toward the conversation that is missing.
The work of the leadership team
Leadership teams do more than set direction and review performance.
They create the conditions under which the rest of the organization works together.
That means making trade-offs visible.
Clarifying where authority sits.
Ensuring that priorities mean more than shared words.
Aligning goals that would otherwise pull functions in different directions.
And discussing the operating assumptions each leader brings to the table.
When that work remains unfinished, the organization does not stop.
People continue making decisions. Teams create workarounds. Managers negotiate across boundaries. Projects find ways to move forward.
But everything requires more effort than it should.
Organizational friction may become visible far from the leadership team.
That does not mean it began there.
Sometimes the people caught in the friction are not the source of the problem.
They are simply the first ones forced to confront a conversation their leaders never completed.
