Why Does My Team Ask Me Everything?

You open the laptop and there are nineteen messages. Each one is a decision waiting on you. Should we send this to the client. Is this price right. Do we hire him. Which version do we ship. None of them is hard for you. You answer in seconds. That speed is the problem, and it is worth understanding why.

The team is not weak. The team is not lazy. The team comes to you because you are the only one who can read the situation fast and read it right. You map the components, you see how they interrelate, you weigh the consequence, and you give the call. They watch the call land. Then they bring you the next one.

Antano describes exactly this reading move when he works on a business. In order to provide a solution, he first maps how many components are at play, understands how they all interrelate, then sees the mindset causing it to work and the mindset causing it to fail. That mapping is a capability. You run it without noticing. The team does not run it at all, so every situation that needs it arrives back at your desk.

Delegation does not transfer the skill

You already tried the obvious answer. You delegated. You wrote the process. You said make the call yourself next time. And the next time, the question came back anyway. This is the part founders misread. You think you handed over the decision. You handed over the task. The capability that produces the decision stayed with you.

Antano and Harini draw the line between giving someone a thing they already are and completing the thing they are missing. One of the moves that helps a person reach the next level is finding what in their own ecosystem needs to be complemented and added to what they already have. Your team has competence. What they are missing is the unconscious pattern that turns a messy situation into a clean read. You cannot write that into a document. It is not information. It is an installed skill.

If your team escalates every decision and you cannot see how to stop it, you are looking at team dependency, and it has a specific cause. The Team Dependency guide maps exactly which capability your team is missing and why instructions never close the gap.

What the dependency is actually made of

Picture two people watching the same problem. You see the components, the order they matter in, the second-order consequence three moves out. Your team member sees a list of facts and waits for you to tell them what the facts mean. The gap between those two views is the dependency. It is not a gap in effort. It is a gap in installed capability.

This is why capable people still ask. Antano points out that people are often good at many things yet carry an incomplete rarity. They need a couple more things completed for the combination to click. Your team is good. The combination has not clicked, because the one capability that makes their judgment trustworthy to you has never been installed in them. So they protect the business the only way they can. They ask first.

The cost compounds. Every escalation is time compression running in reverse. Decisions that should take the team minutes take you an interruption, and the work you are actually meant to do gets pushed to the edges of the day. The business moves at the speed of your inbox. Worse, the team learns that asking is safer than deciding, so the routing deepens the longer it runs.

Excellence Installation Technology, the work Antano and Harini built, treats this as an installation problem rather than a motivation problem. EIT installs the underlying pattern that produces the judgment, so the capability lives in the person instead of in a checklist. When the reading skill is installed, the team member maps the situation, weighs it, and makes the call you would have made, because they now see what you see. The same move Antano runs on a business, the team starts to run on the work in front of them.

Naming the dependency does not dissolve it. Knowing your team asks too much will not stop them asking. The routing changes when the capability is installed at the level of architecture, and once it is, the next question on the topic does not reach you at all. That mechanism is the subject of How to Stop Being the Bottleneck in Your Own Business.

A further trap waits here. You may decide to delegate harder, give bigger mandates, push the team to own more. That can fail in a way that looks like the team is not ready, when the real issue is that delegation and installation are different acts. The distinction is laid out in Delegation vs Installed Capability: Why Your Team Still Cannot Decide.

Your team asks you everything because you are the only one carrying the read. Make the read theirs, and the questions stop arriving.