03 / Decisions & Accountability
Three Reasons a Delegated Decision Comes Back
A decision that keeps returning upstairs is sending one of three different signals — missing information, incomplete authority, or a history of reversal — and the same remedy cannot fix all three.
The example below is illustrative.
A sales director can approve a service credit up to $25,000. A customer requests $18,000 after a missed delivery. The director forwards it to the CEO. It is the third credit the CEO has seen this month, and the easy conclusion is that the director lacks nerve.
The easy conclusion is often wrong. The same email could have reached the CEO because no one could establish what Sales actually promised, because settling the dispute also required a concession only Operations could make, or because the last director who issued an unpopular credit was overruled in front of the customer. Three different failures, each wearing the costume of timidity. A leader who prescribes "be more decisive" for all three fixes none of them. There is a fourth possibility worth ruling out first: the escalation was correct, and the decision genuinely belonged upstairs. Set those aside before diagnosing the rest.
The information test
Ask the director to reconstruct the decision from the records available before the escalation. What did the customer buy? What did the company promise? Who changed that promise? Could anyone have established the answer while the credit was still useful?
Suppose the original order says standard delivery, but a revised date was agreed in a call that never made it into the account record. The CEO remembers the exception — and that recollection is exactly what makes a credit commercially sensible or not. The problem recurs for as long as the business acts on commitments its decision-makers cannot retrieve. Hand the director and another qualified manager the same file independently: if they diverge because both must reconstruct the promise from incomplete records, you have a records problem. If the file contains the facts and the director consistently misreads their implications, you have a capability problem — and the fix for one makes the other worse. The cornerstone on delegating judgment sets out how to test whether that reasoning can travel at all.
The authority test
An authorization to credit an invoice can sit right next to zero authority to promise a replacement date — and the two may be commercially inseparable. If the customer will accept $18,000 only with an expedited replacement, deciding the credit alone leaves the dispute open and the director with no choice but to escalate.
Write down the complete commitment the company would make, and for each part name who can say yes, who can say no, and who owns the result when the parts conflict. If each department makes a sound local decision while the combined promise stays unworkable, the company needs a decision at the boundary — the mechanism When Every Department Is Right and the Company Is Wrong traces across several operating settings. The practical fix is usually a named operating owner, a response deadline, and a set of recovery options the director can offer without improvising.
When the same tradeoff keeps returning after you identify the missing authority, use The Recurring Decision Is a Missing Decision Right to price both sides and give the choice a durable owner.
The consequence test
Suppose the facts are available and the operating commitment is within the director's authority. Now look at what happened the last several times a director made a defensible decision that senior leadership disliked — a pattern, not a single instance.
There is a real difference between learning from an outcome and reopening a permissible decision because a more senior person would have chosen differently. If sound decisions are routinely reversed after the customer sees them, forwarding the next one is not timidity — it is rational self-protection. Approval becomes insurance against reversal, and the cost compounds: every escalation adds days, and a $9,000 credit that could have closed a dispute on Tuesday becomes a $15,000 problem by the following Monday once the customer has stewed and the account is at risk. Review the choices on the information available when they were made: if the director crossed a known limit or missed a fact she was expected to check, address that. If the reasoning was sound and within bounds, let it stand — because consistency in letting sound decisions stand is the only thing that proves discretion actually exists.
Run the review on ten decisions
Select ten recent decisions that came back, plus a comparison group of similar ones resolved at the intended level. For each returning decision, record the actual request, the last moment an answer would have mattered, the missing fact or action, and why the manager sought review. Set aside escalations genuinely required by safety, contract, or defined exposure limits. Then change the single condition the evidence supports for one recurring class, and compare the next set on time-to-binding-answer, unwanted reversals, repeat contacts, realized concession cost, and required approvals. A drop in CEO emails only counts if the customer still receives sound commitments and the controls still hold.
Take this to your team. If the next manager reaches a sound answer that differs from yours, will the company act on it and let it stand?