Why Your Leadership Team Keeps Coming Back to You

The Ten-Second Answer

A manager knocks, states a problem, and waits. The owner could answer in ten seconds. That ten-second answer is the whole story of why the pattern never changes.

Capable people, real experience between them, and still almost every meaningful decision lands back on the owner's desk: a pricing exception, a hiring call, a vendor dispute, a scheduling conflict. None of these require the owner specifically. All of them arrive anyway. The usual read is that the team is not ready, or not confident, or waiting to be told what to do. That read is rarely accurate. What is actually happening is an escalation loop, and loops are built, not inherited.

What Actually Gets Escalated

Most things that reach an owner's desk are not genuinely hard calls. They sort into three rough categories: routine decisions with low real stakes that simply feel safer to confirm, decisions that feel risky to the person making them but are not actually risky to the business, and a smaller set that are genuinely ambiguous and would reasonably go to anyone with broader context. The first two categories make up most of what arrives. The third is the only one that actually needed the owner.

A hypothetical professional services firm shows the pattern clearly: the owner reviews every client proposal before it goes out, including ones well within a manager's experience to write alone. Years into this habit, managers draft proposals knowing the owner is likely to rewrite sections regardless of how carefully the draft was prepared, so the firm keeps routing low-stakes drafting decisions upward long after the managers were capable of making them alone.

What the Question Is Really Asking For

When a manager asks "what should I do here," the literal question is rarely the real one. More often, the real question is "will you back me if this goes wrong," which is a request for cover, not a gap in competence. Treating every escalation as a knowledge problem and answering it with more information misses what is actually being asked for, and the pattern keeps repeating because the underlying request, reassurance, was never addressed.

How the Owner's Response Teaches the Loop to Repeat

Every time an owner answers fast, decisively, and without complaint, two things happen at once: the immediate problem gets resolved, which feels productive in the moment, and the team learns that asking is fast, painless, and safe. That gets paid back in kind, with more questions and more check-ins.

The lesson lands even harder when a decision made without the owner gets quietly redone or overruled afterward, without being discussed directly. The message absorbed is not really about that one decision. It is that delegated authority is conditional, and checking first is what protects a manager from being wrong in front of the owner later. A team with no reliable way to tell whether a decision made alone will actually stand has little choice but to keep asking, and that is a rational response to the system as built, not a sign the people in it lack confidence.

Breaking the Loop Without Disappearing

Breaking an escalation loop does not start with a speech about empowerment. It starts with a changed response to the next few questions that arrive. Instead of answering immediately, a better first move is often a question back: what would you do, and what is stopping you from doing it. That single habit, repeated consistently, does more to shift behavior than any policy document, because it hands the decision back to the person who should be making it while still giving them a safety net if they are genuinely stuck.

It also requires letting an imperfect call stand without quietly fixing it afterward, and naming out loud, in the moment, when a decision did not need to come to the owner at all rather than just answering it anyway. This is slower than simply solving the problem in the room. But an owner who remains the fastest and safest route to every answer guarantees the loop continues exactly as it was built, no matter how the team's job titles are written.