Same organisation. Same quarter. Comparable inventory. Identical market conditions.
One prioritised velocity — held pricing, moved units, kept broker relationships warm. The other held margin — protected pricing, accepted slower movement, maintained positioning.
Both had sound reasoning. Both could defend their call in any review. Both were genuinely strong.
But together, they sent the market a signal that undermined both projects.
The issue wasn't capability. It was that no one had told them which of those two things mattered more when they conflicted.
That's not a people problem. That's a decision architecture problem.
And it's far more common in high-performing organisations than anyone admits — because high performers fill gaps. They make the call. They move forward. And in doing so, they mask the absence of a shared framework that should have made the call for them.
Uneven outcomes in capable teams almost always trace back to the same source: different people optimising for different things, with genuine conviction, in the absence of a clear priority stack.
The instinct is to solve it through alignment — more communication, more reviews, more culture work. These help. They're not sufficient.
What actually creates consistency is something more specific: an explicit, agreed, tested answer to the question — when the things we care about conflict, what do we protect first?
Most organisations have values. Few have a decision-making logic.
Values tell people what to care about.
Decision-making logic tells them what to do when two things they care about pull in opposite directions.
That's the gap. And it shows up — reliably, expensively — in the outcomes of good teams.
