Pushing a decision back up to the manager, openly and with a recommendation, puts the call with the person who carries its accountability.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
A senior analyst on a retail bank's anti-money-laundering team was asked to clear a backlog of borderline alerts, cases where a customer's pattern sat between routine and suspicious. The money laundering reporting officer, not the analyst, was personally accountable to the regulator for those calls. The analyst sorted the backlog into three groups: clear cases the analyst closed, clear cases filed as suspicious, and forty-one gray cases. Each gray case went up with a one-paragraph summary, a recommendation, and the reason it sat above the analyst's authority. The officer pushed some back at first. The analyst asked for a written rule on which patterns the team could close alone. The officer wrote one, the gray cases fell to about a dozen a month, and the next regulatory exam found the files in order.
Why it works
Escalating puts the decision with the person who carries its accountability, which makes it look like the better course, and it costs the subordinate only a message. Owning a call that sits above one's authority carries real blame if it goes wrong, so deciding alone looks costlier. It works when the manager feels obliged to engage escalations, role charters are ambiguous, and the culture punishes being wrong harder than being slow.
The thinking behind it
Jonathan Baron Outcome Bias in Decision Evaluation (1988), by Baron and Hershey, found that people rated the same decision, made on the same information, as better and its maker as more competent when the outcome happened to be good. Whoever makes a borderline call will be judged by how it turns out, whatever the quality of the reasoning. That is why subordinates push risky calls up, and why the clean form asks the person who carries the accountability to own them, with a recommendation attached.
Herbert A. Simon Herbert Simon's Designing Organizations for an Information-Rich World (1971) argues that information consumes the attention of its recipients, so attention becomes the scarce resource. Every escalation draws on a manager's limited attention. Grouping cases and asking for a written rule on a whole class of them spends that attention once, where forty separate requests would spend it forty times and slow the whole team.
When it fits
Accountability that sits above your role is the test: a decision you are asked to make whose consequences your manager will answer for, or a role whose authority is unclear. It needs a reachable manager, a recommendation you can stand behind, and a willingness to take back decisions that really are yours.
How to use it well
Send the decision up with your recommendation attached, never bare.
- Say in one sentence why it sits above your authority.
- Group similar escalations so the manager can rule on a class of cases at once.
- Ask for a written rule on which decisions you may make alone.
- Accept the decisions that come back, and make them.
Track your own escalation rate against your peers'. A rate far above theirs means you are pushing up work that is yours, and your manager will see it before you do.
What it costs and where it backfires
Escalating often makes you look unsure, slows your team, and fills your manager's calendar, which they will notice at review time. It stays legitimate only while the decision genuinely belongs above you. Pushing up calls that are yours to avoid blame, or to bury a manager in detail until their own work suffers, turns the move into sabotage of your manager's work.
When it is used on you
Hand decisions that belong to the role back with a question: what do you recommend? Write explicit role charters that say which decisions belong where, and count escalations by person for a month so you see the pattern as well as the latest request.