03 / Decisions & Accountability

The Recurring Decision Is a Missing Decision Right

When the same tradeoff keeps coming back to the executive meeting under different customer names, the meeting is not exercising judgment — it is standing in for a decision right no one has assigned.

The example below is illustrative.

Every week the executive team decides whether a newly sold urgent job can displace work already in production. The customer changes. The revenue Sales wants to protect changes. The underlying tradeoff never does: someone must decide when protecting one customer justifies breaking a promise to another.

Sales can book a premium job. Operations can protect its schedule. Finance can estimate the rush premium. But the decision to sacrifice one commitment to make another belongs to no single function, so it defaults to the meeting. A meeting is the right venue for a genuinely unusual exposure. When the same shape of case returns every week, the company should ask what authority it keeps borrowing from that room — and why it has never been granted.

Write the recurring settlement as a decision

Pull the last several cases and express each as a choice between complete company commitments: move an existing job, incur recovery cost, and send an agreed customer notice — or hold the existing promise and offer the new customer a later date. Include the cost of serving both accounts, the demand that can actually be won, and any credible service or contractual constraint.

Then ask whether the cases share an economic structure and a boundary. If every case exposes a different material risk, keep the flexible forum and improve the decision packet. If the same tradeoff recurs within definable limits, name an owner who can act inside them.

Price the whole settlement

Assume the urgent order contributes $18,000 after its own variable production costs. Taking it requires $4,000 in incremental overtime and freight and moves an existing job to a slot carrying $6,000 in documented recovery cost. The remaining $8,000 is the contribution from accepting the rush before any downside tied to the displaced customer. If the move would breach a service term carrying a $12,000 credit, the trade flips to $4,000 adverse unless the team can renegotiate the terms or find another route. The figures are illustrative; the decision owner needs the actual cost, likelihood, and terms from the people who can verify them. But the shape is the point: the two customers are not symmetric, and a rule written only as a revenue threshold would treat them as if they were.

Those two cases belong at different levels of authority. The first can fit a documented scheduling right if both commitments are honored and the recovery cost stays within limits. The second needs someone who can authorize a breach, obtain an agreed change, or decline the rush.

Give the owner a usable right

Part of the rightWhat it must establish
TriggerThe new order competes for the same confirmed production window
Decision ownerThe person able to authorize the re-sequence and assign its recovery cost
EvidenceCurrent sequence, named customers and terms, feasible alternate dates, contribution after recovery
Protected conditionsExisting contractual or safety commitments, and the delegated cost and service limits
HandoffWho releases the new sequence, communicates with both customers, records execution
EscalationThe named owner of any exposure beyond the ceiling, and the deadline for a choice

Separate evidence rights from veto rights: a department must be able to challenge a false fact about its own capacity without holding a general power to reopen a sound decision. Decide in advance which kinds of new evidence permit reconsideration.

Replay the next decisions

Run prior cases through the proposed right and find where the owner would have delayed, escalated, or chosen differently. Then use it on the next set within bounds. Track delays measured to the point when the company can actually honor the revised plan, not merely to the meeting's end. If local approvals get faster while more dates get renegotiated, the owner cannot really bind the whole company — refine the bounds before pushing the decision farther down.

When the same case keeps returning despite a usable right, the returning-decision review separates incomplete authority from missing information. And When Every Department Is Right and the Company Is Wrong is the synthesis of why separately correct functions still produce a wrong company outcome — the structural reason these settlements exist at all.

Take this to your team. Which decision has been approved at the last three meetings under three different customer names — and who could own it inside written bounds instead?

← Back to Decisions & Accountability