Why Your Team Keeps Bringing Simple Problems to You
If you find yourself answering the same kinds of questions over and over, solving problems that feel like they should not require your involvement, and being pulled into situations that someone else should be handling, the instinct is often to blame the team. They are not thinking critically. They are not taking initiative. They are not capable of operating without you.
That conclusion is usually wrong. The more accurate explanation is that the business has been structured in a way that routes everything through you, and the team is responding rationally to the environment they are operating in.
You Trained Them to Ask
Every time you answered a question that someone could have figured out themselves, you made it slightly more likely they would ask the next one. Every time you stepped in and handled something before giving the team a chance to work through it, you reinforced the message that the right move is to wait for your input rather than act independently.
This is not intentional. It happens because stepping in is faster, feels more reliable, and avoids the discomfort of watching someone struggle through something you could solve in thirty seconds. But the cumulative effect of those choices is a team that has learned, through direct experience, that bringing things to you is the expected behavior.
John Burdett describes the dynamic clearly: when you are the one who has always executed the process, the team does not develop the confidence or the authority to execute it themselves. The owner’s involvement becomes the default, and over time it becomes the only mode the team knows.
There Is No Map for Them to Follow
Teams bring problems to the owner when they do not have a clear way to solve them on their own. That usually comes down to one of three things: they do not know the process, the process does not exist, or the process exists but nobody has been clear about who has the authority to execute it.
Documentation solves the first problem. Building the process in the first place solves the second. But the third one — authority — is the one that gets skipped most often. You can hand someone a perfectly documented process and they will still come to you if they are not sure they are allowed to act on it without checking first.
Clarity about decision-making authority is just as important as clarity about how to do something. The team needs to know not just what the process is but which decisions they can make independently, which ones require input, and which ones genuinely need the owner’s approval. Without that clarity, the default is always to ask.
The Stakes Feel Higher Than They Are
Part of what drives teams to escalate problems upward is an inflated sense of the risk of getting it wrong. If the culture around mistakes is punitive — if errors get handled with frustration, if the owner steps in and corrects things in ways that signal the team cannot be trusted — people stop taking initiative. The cost of being wrong feels higher than the cost of asking, so they ask.
John draws a useful analogy here from aviation and aerospace. Those industries are the most checklist and process driven in the world precisely because the stakes are life and death. But for most businesses, the stakes of any individual decision are not that high. Treating every problem like a high-stakes situation creates a culture of risk aversion that stalls the team’s ability to function independently.
Building a team that can solve problems without you requires creating an environment where reasonable mistakes are treated as learning opportunities rather than failures. That does not mean accepting careless errors. It means being honest about what is actually at risk in a given situation, and calibrating the response accordingly.
They Have Never Seen You Let Them Handle It
For some teams, the reason they keep bringing problems to the owner is simply that the owner has always taken them back. The team may have tried to handle something independently, and the owner stepped in before they had the chance to see it through. Or they handled it and the owner redid it anyway, sending the message that their solution was not acceptable.
This pattern is common in businesses where the owner is highly capable and has high standards. The intention is quality control. The effect is a team that stops trying to own outcomes because experience has taught them that ownership is not really available to them.
Letting the team handle things means actually letting them handle things. Not hovering. Not stepping in before the outcome is clear. Not reworking their output because you would have done it differently. It means tolerating some variation from how you would have done it, as long as the result is within an acceptable range, and treating that variation as normal rather than as something to correct.
The Fix Is Structural, Not Motivational
A common response to a team that will not take initiative is to try to motivate them into it. Better culture, more encouragement, rallying speeches about ownership and accountability. Those things are not worthless, but they do not fix a structural problem.
If the team keeps bringing simple problems to you, the fix is to build the structure that allows them to solve those problems without you. Document the process. Define the authority. Create a clear escalation path that specifies which situations actually require owner involvement and which ones do not. And then hold the line on that path, redirecting questions that fall below the escalation threshold back to the team rather than answering them yourself.
John talks about process as guardrails for growth. It gives the team freedom to do their job without being a robot, while protecting them from veering off course. The guardrails are what make genuine independence possible, because the team knows how far they can go and in which direction without needing to check in.
What Changes When You Stop Being the Answer
When the team stops routing everything through you, something shifts in how the business operates. Decisions get made faster because they do not have to wait for your availability. Problems get solved at the level where they actually exist rather than being escalated past people who could have handled them. The team builds genuine competence because they are actually doing the work rather than describing it to you so you can tell them what to do.
And you get your attention back. The mental load of being the answer to every question in the business is significant, and most owners do not fully appreciate how much it costs them until it stops. Getting that capacity back is not just a relief. It is what makes the owner’s real job — thinking strategically, seeing around corners, making decisions that actually require their level of experience — possible to do well.
If you want to go deeper on how to build the kind of structure that gets your team operating independently, a recent episode of The Fast Slow Motion Podcast: How to Stop Being the Bottleneck in Your Business with John Burdett and Eric Housh covers this directly.
Listen to the full podcast episode here.