The Executive Conflict Protocol

The leadership team says it is arguing about the forecast. Three months later, it is arguing about the transformation roadmap. Then the hiring plan. Then the customer commitment. Different slides. Different numbers. Same people in the same positions, making the same moves.

One executive pushes harder and adds evidence. Another questions the premise. A third goes quiet. The CEO summarizes what everyone already knows, asks for alignment, and schedules another discussion. The meeting ends with less trust and no clearer decision.

The problem is not that the team has conflict. The problem is that the team has no shared architecture for using it.

Conflict Is Information

Executive disagreement is predictable. Each leader sees a different part of the enterprise, carries different risks, and is accountable for different outcomes. A CFO should notice economic exposure that a product leader may discount. A CIO should see technical debt that a commercial leader cannot. A CHRO should surface capacity and incentive problems that do not appear in the business case.

Those differences are an asset until the team treats them as evidence that someone is not committed. At that moment, the argument moves from the work to the people doing it.

The goal is not less conflict. It is conflict that produces a better decision and then ends.

The Three Fights Hidden Inside One

Most recurring executive conflicts combine three questions without distinguishing them.

What problem are we solving?

One leader believes the problem is near-term execution. Another believes it is strategic positioning. Both bring relevant facts, but the facts cannot resolve a disagreement about the question itself.

What evidence are we using?

Teams mix facts, estimates, assumptions, and preferences into one category called data. The argument becomes endless because an operating result and a belief about the future are treated as if they carry the same certainty.

Who owns the call?

When decision authority is unclear, influence becomes a contest of endurance. The leader with more data, more status, or more willingness to keep debating can become the de facto decision owner.

The Issue-Evidence-Decision Protocol

Before the debate begins, put three fields where everyone can see them. The discipline is simple. The practice is not.

1. Issue

Write the decision question in one sentence. Not the topic. Not the history. The choice. If leaders cannot agree on the sentence, that disagreement is the first issue to resolve.

2. Evidence

Sort inputs into what is known, what is estimated, and what is assumed. Then name the evidence that would materially change the decision. This stops the team from using more analysis to avoid a judgment that no amount of analysis can remove.

3. Decision

Name the owner before the discussion, the deadline for the call, and the trigger for revisiting it. A decision without a defined owner is a negotiation. A decision without a revisit trigger is vulnerable to being reopened by anyone who disliked the outcome.

Separate Dissent From Commitment

Executives often soften their disagreement because they fear being labeled uncommitted. That produces false alignment before the decision and quiet resistance afterward.

A stronger norm is explicit: dissent is required before the decision; coordinated execution is required after it. The right to challenge the evidence is not the right to ignore the call. The obligation to execute is not an obligation to pretend the decision was unanimous.

Commitment after a decision is credible only when dissent before it was real.

What the CEO Must Stop Doing

CEOs often become the emotional regulator for executive conflict. They translate sharper statements, add context, and search for a compromise that lets every leader leave with something protected. This can lower the temperature while preserving the pattern.

The CEO's higher-value role is structural. Keep the issue specific. Require assumptions to be labeled. Protect the decision owner from status pressure. Refuse to let a settled call return without the evidence or trigger the team agreed would justify reopening it.

When the CEO repeatedly rescues the team from conflict, the team never develops the capacity to use conflict.

Run the Protocol on the Fight You Already Know

Choose the disagreement everyone can predict before it begins. Do not wait for the next heated meeting. Write down:

1. The exact decision the team keeps failing to close.
2. The known facts, estimates, and assumptions being mixed.
3. The person who owns the call.
4. The evidence that would justify revisiting it.
5. The behavior expected from every executive afterward.

Use that structure in the next conversation. The team may still disagree. That is not failure. Success is a disagreement that becomes clearer as it proceeds, reaches the right authority, and does not need to be performed again next month.

Conflict Reveals Readiness

In the Four A's, recurring executive conflict sits at the intersection of Alignment and Authority. Alignment determines whether leaders share the operating assumptions. Authority determines whether the disagreement can become a decision.

When either condition is weak, organizations compensate with more meetings, more analysis, more escalation, and more private coalition-building. None of those resolves the underlying design.

Name the issue. Separate the evidence. Assign the decision. The team does not need to eliminate the conflict. It needs to build a bridge strong enough to carry it.