Two Reasonable Decisions. One Enterprise Failure.

Nobody behaved badly, which is exactly what makes this pattern hard to catch.

A customer wants a delivery date three weeks inside the standard lead time. The deal is significant.

The commercial leader commits to the date. From their position, the call makes sense: the account is winnable, the competitor is credible, and delivery has flexed before.

Operations declines to flex. That call also makes sense: the plant is at capacity, expediting this order pushes other commitments late, and the overtime consumes the margin that made the deal attractive.

Both leaders are competent. Both are doing what they were hired to do. The company misses the commitment, absorbs the margin hit, and damages the customer relationship it was trying to win.

A shared scoreboard can expose this conflict. A leadership forum can surface it. Neither resolves it unless the enterprise has a decision rule and one accountable owner.

Communication is not the problem

The default diagnosis is that the two leaders did not communicate enough. Sometimes that is true. Often they have talked repeatedly, escalated appropriately, and each made a clear case.

They are not failing to communicate. They are optimizing against different definitions of a good outcome, and no standard exists above either function to arbitrate.

That distinction points to a different fix. If it is a communication problem, improve the relationship. If it is a definition problem, a better relationship may only produce two well-aligned people who still disagree for valid reasons.

Functional logic can still produce enterprise failure. There is no bad actor, so there is no obvious person to correct.

Two things are missing

The first is an enterprise decision rule.

Not a broad statement about putting the customer first. Both leaders can use that statement to defend their position.

The rule has to answer the trade-off. When a delivery commitment conflicts with capacity, what governs? Contribution margin? Strategic account status? The cost of disrupting existing commitments? Service risk?

Whatever the rule is, it should exist before the deal is on the table. Written afterward, it becomes a justification for what already happened.

The second is a named owner for the decision.

When two functions each hold half the authority, the decision does not get made. It gets negotiated. Negotiated decisions take longer, often resolve toward organizational weight rather than enterprise value, and tend to reopen.

The relationship workaround

Many companies solve this informally.

Two leaders who trust one another work it out. One gives ground, the enterprise gets a reasonable result, and everyone concludes the system is functioning.

Then replace either leader. Put both under enough pressure that neither can afford to give ground. Or scale the business until the conflict arrives every week instead of every quarter.

Results that depend on personal relationships rather than the operating structure are not a system. They are a dependency the organization has not priced.

The test is simple. If the same recurring conflict resolves differently depending on who is in the seats, the people are producing the result, not the structure.

Writing the rule

Identify the recurring cross-functional conflicts. Not hypothetical ones. Start with the few that have occurred repeatedly and cost the business time, money, or customer confidence.

For each conflict, define what a good enterprise outcome looks like when the functional interests collide. Make the rule specific enough that two reasonable people applying it independently would reach a similar conclusion.

Then name one accountable owner. Not the CEO by default; that recreates the bottleneck. The owner should sit close to the trade-off and have enough enterprise perspective to make the call.

Name who must provide input, what they must provide, and by when. Then make it explicit that being consulted does not confer a veto.

Inputs inform. Owners decide.\

The objection worth taking seriously

Leaders raise a legitimate concern: every situation is different, and a rule written in advance cannot anticipate every circumstance.

True. The answer is not a rule instead of judgment. It is a rule plus a named owner with the judgment to apply it.

The rule handles the recurring pattern. The owner handles the exception and remains accountable for the call.

The alternative - no rule, no owner, every case negotiated from scratch - does not produce better judgment. It produces slower and less consistent judgment.

Where to start

Take the last cross-functional conflict that cost the business real money or customer confidence.

Write down what each leader was optimizing for and why each was right within their own responsibility.

Then answer two questions: who should have decided, and against what enterprise standard?

If you cannot answer them, you have found the fix.