JUDGMENT DESIGN

The Decision Went Up. The Context Stayed Down.

The decision belonged to the person who understood it best, and that person chose not to make it. Not out of laziness. Out of something that felt, in the moment, like prudence. The call was consequential, the kind that leaves a name attached to it if it goes wrong, so the manager closest to the problem did the responsible looking thing and sent it upstairs. A short note. A clean summary. A recommendation sanded down into options. And the whole matter rose one floor to a leader with a larger title and a thinner grip on the specifics. The problem went up. Everything that made the problem decidable stayed down.

Up on the next floor the decision landed in an inbox already stacked with other people's escalations, each one somebody else's hard call wearing the costume of a request for guidance. The senior leader had authority over the question and almost no contact with it. They had not sat through the vendor meetings. They had not watched the pilot wobble. They did not know which of the three figures in the summary was solid and which was a guess in a good suit. So they did one of the two things the position allows. They sent it back down with a clarifying question, which bought a week and settled nothing, or they decided quickly off the summary alone, which is to say they decided on a compression of the situation written by the one person who had already declined to decide on the full version of it.

Escalation is a transfer, not a safeguard.

Organizations treat escalation as a form of rigor. The hard ones go up. That is the rule, whether or not anyone has written it down, and it feels like diligence because seniority is supposed to track judgment. But escalation does not carry a decision toward better judgment. It carries a decision toward higher rank, and rank and knowledge almost never sit in the same chair. The person with the standing to be safely wrong is rarely the person with the detail to be right. Escalation is simply the ritual by which a call is walked away from the information and toward the authority, as though altitude were the thing that decided well.

What moves up the chain, reliably, is not the decision. It is the liability for the decision. The manager who escalates is not confused about the right answer as often as they are unwilling to own it, and the fastest way to stop owning a call is to hand it to someone whose title makes them the natural owner of anything that arrives. The escalation note is a small masterpiece of this. It presents as deference, I would value your steer on this, while performing a quiet extraction, this is now yours. The problem rises. The accountability rises with it. The context, which cannot be folded into a paragraph without losing exactly the parts that mattered, stays on the floor where it was gathered and is not invited up.

So a second and worse thing happens on the way up, which is that the summary becomes the situation. Nobody above the originating level will ever touch the raw material again. They will decide on the three bullet points and the recommendation, and the three bullet points were written by a person who knew precisely which inconvenient facts to leave in the footnotes. This is not usually dishonest. It is gravitational. Any summary bends toward the conclusion its author already prefers, and once it has traveled one level up it hardens into the only version of events that exists. The decision gets made on a map drawn by the one person who did not want to make the decision, by someone who has never seen the territory.

The incentive underneath all of this is brutally simple and almost never said aloud. Escalating is free and deciding is expensive. The manager who sends a hard call upward pays nothing and looks appropriately humble. The manager who makes the hard call themselves owns every downside and banks none of the cover. A system that never corrects for this teaches its most capable and best informed people the lesson with perfect clarity. Do not decide. Route. The ones closest to the work, whose judgment the organization most needs at the point of contact, learn to convert every real decision into a well written request for someone else's signature, and they are quietly promoted for how cleanly they do it.

The more it matters, the less the decider knows.

Here is the inversion the organization's own logic hides from it. Escalation sorts decisions by stakes. The larger the consequence, the higher it travels, which means the most important calls are routed, by design, to the people with the least direct contact with them. The trivial decision gets made by the person who knows everything about it. The decision that will shape the next two years gets made four levels up, by someone reading a paragraph between two other meetings. The organization believes it is applying its best judgment to its most important problems. It is doing the precise opposite. It is applying its thinnest context to its heaviest calls, and calling the arrangement a chain of command.

Seniority is not proximity. The higher a decision climbs, the further it gets from the only people who could have made it well.

Rebuilding this does not mean abolishing escalation or pretending seniority is useless. Some decisions genuinely belong higher, because they need authority that only exists higher, or a view across silos that only assembles at the top. The discipline is in telling those apart from the far larger pile of decisions that went up only because no one at the bottom wanted the liability. It means a senior leader whose instinct, when a hard call lands from below, is not to decide it but to ask one question. Do you have everything you need to make this, and if you do, why is it on my desk. It means pushing the decision back down to the lowest level that still holds the full context, and sending down with it the one thing the escalator was actually missing, which was never intelligence. It was air cover. Decide this. I will own that you were the right person to.

Which is why the most telling thing to watch in a leader is not how they handle the decisions that reach them. It is what they do in the half second before a decision becomes someone else's. Under real pressure, with the clock live and the stakes climbing, does a leader hold the calls that belong to them and push back the ones that do not, or do they reflexively send everything hard up the building and everything ambiguous down it, keeping only the decisions that were never going to hurt. We built the simulation to surface exactly that reflex. It does not reward the leader who makes the most decisions. It exposes whether a leader decides where the context lives, or whether, the moment the heat arrives, they discover that every difficult call has somehow become a matter for someone else.

Every escalation is a decision. It is the decision to be governed, on the thing that matters most, by whoever happens to know the least about it.

TEST YOUR OWN JUDGMENT

Theory is interesting. Data is better.

Five cascading crises. AI-generated. Your decisions compound. Get your personalized Leadership Architecture Report in under 4 minutes.

Run the Simulation.

WEEKLY INTELLIGENCE

One insight on leadership systems. Every Monday.

No fluff. No spam. Unsubscribe anytime.