Main idea

A conflict of priority that no meeting settled doesn't cancel itself out. It leaves with the teams, each carrying its own reading of the decision, and it reappears at execution — but in another form and under another name.

Nobody will then say: we didn't arbitrate. They will say coordination was poor, that the teams didn't communicate enough, that priorities moved, that the field didn't follow, that the product wasn't ready. These diagnoses are often accurate about the facts observed; they are wrong about the root, which is older and located elsewhere — in the session where the organization preferred a weak agreement to a clear contradiction.

The consequence is practical: the remedy applied bears on the symptom. You reinforce communication, add a ritual, redo a plan, while the original contradiction still hasn't been settled.

Why it matters

This provides a line of backwards diagnosis: faced with a recurring coordination problem between two teams, go back to the decision that put them in a position to diverge, rather than to the way they work together.

It also protects the execution teams from an unfair charge, by showing that their divergence is the product of a decision not made, not of a lack of professionalism.

Nuances and limits

Not all coordination problems come from a dodged arbitration: some are genuine problems of tooling, time zones, workload or team turnover.

And going back to the root isn't always actionable: when the original decision is several months old and the sponsor has changed, reopening the arbitration can cost more than compensating.

Open questions

• What clues distinguish ordinary execution friction from a priority contradiction disguised as a coordination problem?