Escalation Is Not a Confidence Problem
When capable people check with you before acting, they are reading the system accurately. It taught them to.
You can watch it happen over a few months. A decision that used to get made two levels down starts arriving in your inbox instead. Then another one. Nobody announces the change and nobody is doing anything wrong, but the volume of things needing your sign-off keeps climbing while the size of those things keeps shrinking.
The usual explanation is that the team lacks confidence. So you say the encouraging thing. You tell them you trust their judgment, that they do not need to check with you on this, that you want them making these calls. They nod, they mean it, and two weeks later the same class of decision is back on your desk.
That is worth paying attention to, because it means the encouragement was aimed at the wrong problem. People who lack confidence hesitate. People who escalate are not hesitating. They are doing something quite deliberate, and if you look at what they are protecting themselves from, the behavior is not timid at all. It is accurate.
What they are actually asking
Every escalated decision carries two questions the person will almost never say out loud.
The first is whether this call belongs to them. Not in the abstract, and not according to the job description written when the role was created. Whether it belongs to them *this week*, given what leadership has been paying attention to lately and how much scrutiny this area is under. That answer moves, and people track it far more closely than we assume.
The second question is the one that actually drives the behavior. If they make this call and it turns out badly, what happens. Do you back the decision because the reasoning was sound, or does the outcome become the verdict. Nobody asks you that directly, because asking it out loud implies they expect to be hung out to dry. So they route the decision to you instead, which answers the question without anyone having to raise it.
Read that way, escalation stops looking like a confidence gap and starts looking like risk management. The person has correctly worked out that the safest place for a consequential decision is your desk, and they have acted on it. You would do the same in their position, and at some earlier point in your career you probably did.
Where it comes from
Ownership was assumed rather than stated. Most teams have never had the conversation out loud. Everyone has a rough sense of who probably handles what, built from watching what happened last time, and rough senses diverge quietly. Two people can both believe the other owns a call, and the way that surfaces is a decision sitting untouched for four days before someone finally forwards it up.
A previous call got reversed. You may have had good reasons. You may have had information they did not. But a reversal teaches a lesson that outlives the specific decision, and the lesson is that this territory is not really theirs. One reversal changes behavior for months. Three of them permanently relocate a category of decision to you, and nothing you say in a team meeting will move it back.
Judgment got graded on outcome. This is the one leaders do without noticing. Someone makes a reasonable call with the information available, it goes badly through circumstances nobody could have predicted, and the conversation afterward focuses on the result rather than the reasoning. Everyone watching learns the real standard: be right, not thoughtful. The rational response to that standard is to make fewer decisions.
What actually moves it
Name the owner out loud, to the room, not to the person. Telling someone privately that a decision is theirs changes what one person believes. Saying it in front of the people they work with changes what everyone believes, including the peers who would otherwise route around them. The public version is doing different work than the private one, and only the public version survives contact with a hard week.
Say in advance what happens when they get it wrong. This is the part most leaders skip, and it is the part that matters. Tell them explicitly: make the call with what you have, document your reasoning, and if it goes badly we will look at the reasoning rather than the outcome. Then the first time it does go badly, do exactly that, visibly. One of those conversations is worth more than a year of telling people you trust them.
Hand back the decisions that arrive anyway. Not with irritation, and not as a test. When something lands on your desk that belongs two levels down, the useful response is to ask what they think and then let their answer stand, even when yours would have been slightly different. Slightly different is the price. What you are buying is a person who does not need to ask next time, and the gap between your judgment and theirs is almost always smaller than it feels from where you sit.
The uncomfortable part
Some of what returns to your desk is there because it is genuinely comfortable for you.
Being the person decisions run through is not only a burden. It supplies a steady sense of being necessary, and it keeps you close to detail you would otherwise lose track of. When a leader says the team escalates too much and then reflexively answers every escalated question within the hour, the system is working exactly as both parties have arranged it.
That is worth sitting with before you decide the problem lives entirely with them.
Three questions
Name a decision that reached you this month and should not have. Can you say, precisely, what the person would have needed in order to close it themselves? If the answer is only that they should have felt more confident, look again, because that answer is almost never the real one.
When did you last reverse a call someone made? What did the people watching learn from it, as distinct from what you intended them to learn?
If someone on your team made a defensible decision tomorrow that turned out badly, what would the conversation be about? Answer honestly, because they have already worked out the answer, and their behavior this week is built on it.