Your Team Brings You Every Problem Because You Taught Them To

I tied my son's shoes for too long.

Not because he could not learn. Because it was easier than watching him struggle through it. We were always late for something, and the knot was always faster if I did it.

I told that story in a session recently, because a founder was describing his team the same way. He watches the client calls. He catches the problems. He brings the issues to the meeting: every week, every issue, him.

His team is talented. But they had never had to carry it, because carrying it was always faster if he did it.

He heard the shoe story and went quiet. Then he said: "They've had their shoes tied for them too long."

This Is Not a Talent Problem

The founders who describe this to me almost always start by questioning their people. Maybe I hired wrong. Maybe they are not senior enough. Maybe I need a stronger number two.

Sometimes that is true. Usually it is not.

Look at what your team has actually been taught. Somebody brought you a decision and you made it, quickly and well, because you have the most context and the most experience and it took you ninety seconds. Somebody else made a call without checking, and you corrected it, maybe gently, maybe not. Somebody raised an issue in a meeting and you solved it before anyone else spoke.

None of those moments felt like training. Every one of them was.

Smart people read that pattern fast. Asking gets you a good answer with no risk. Deciding gets you a fifty-fifty shot at being wrong in front of the person who signs your check. Nobody has to be timid to land on the obvious strategy.

So they bring you everything. Not because they cannot think, but because they concluded that thinking was not what you wanted from them.

The Tell

There is a specific version of this that shows up in leadership meetings, and it is the clearest signal I know.

The founder brings the issues.

Week after week, the list of what is broken comes from a single person. The team shows up, listens, contributes to the discussion, and goes back to work. It looks like a functioning meeting. It is actually a status report with extra chairs.

If you are the one bringing the problems, your team is not identifying problems. They may be seeing them. They are not owning them.

What to Try This Week

Pick one meeting where you usually bring the issues. Before it starts, tell your team plainly: "I'm not bringing anything today. What's on your list?"

Then sit in the silence. Do not rescue it.

That silence is the whole exercise, and it is genuinely uncomfortable. Ten seconds feels like a minute. Your instincts say the meeting is failing and you should save it, and saving it is the exact thing that created the problem.

Somebody will speak. It is often not who you expect. In my experience it is rarely the most senior person in the room, because they have the most to lose by being wrong. It is usually somebody a level down who has been sitting on something for a while and finally has room to say it.

What they raise first will probably be small. Let it be small. The size of the first issue does not matter at all. What matters is that it came from them.

What Happens in Week Three

The first week is awkward and everyone knows what you are doing.

The second week is quieter than you would like.

Week three is where it usually turns, and it turns in a way founders do not expect. The issues stop being safe ones. Somebody raises something that implicates another person in the room, or a process you built, or occasionally you. That is not the exercise going wrong. That is the exercise working, and it is the moment most founders accidentally end it.

Because the temptation, when the issue is genuinely uncomfortable, is to take it back. To say "let me handle that one." And your team learns, in a single moment, that the invitation had limits.

If you can sit through that one too, you get a different company. Not immediately, and not without some bad meetings. But you get people who bring you problems while they are still small, which is the only time problems are cheap.

Cannot Decide Versus Learned Not To

Not every escalating team is a trained one, and it is worth knowing which you have.

A person who genuinely cannot decide will still not decide once you clearly hand them the authority, the information, and the cover to be wrong. Give it a real runway, be specific about what is theirs, and watch. If they keep coming back, you may have a right person in the wrong seat, and that is a different conversation.

A person who learned not to decide changes fast. Give them room and cover, and within a few weeks they are making calls. What they needed was not skill. It was permission, plus proof that you meant it.

The difference is usually obvious inside a month, which is far less time than most founders spend wondering.

The Cost of Being the Answer

There is a version of this where you decide it is fine. You are good at deciding, your people are good at executing, and the company works.

It does work, up to a point. That point is your calendar.

A company where the meaningful decisions all route through a single person can only move as fast as that person can pay attention, and there is no version of you that scales. It also concentrates enormous risk in one head, which is worth thinking about the first time you take a real vacation, or get sick, or want to sell.

And there is a quieter cost. People who are never trusted to decide eventually stop wanting to. The good ones leave for somewhere they get to think. The ones who stay are the ones who were happy not to.

Common Questions

What if They Make the Wrong Call?

Some of them will. That is the price, and it is lower than it feels. Most decisions at this level are reversible, and the few that are not should be the ones that genuinely come to you. The question worth asking is not whether they will get one wrong. It is whether the cost of that is bigger than the cost of a company that cannot move without your attention.

How Do I Stop Correcting Them Without Lowering the Bar?

Judge the outcome, not the method. If it moved the company toward where you all agreed you are going, it was a good call, even if you would have done it differently. Save the correction for decisions that actually went wrong, and be specific about why. Correcting the approach when the result was fine is how people learn that only your way counts.

My Team Says They Want More Ownership, but Nothing Changes

Wanting it and having somewhere to put it are different things. If nobody owns a defined part of the business, ownership has nothing to attach to and every decision is arguably everyone's, which means it is yours. Getting clear on who owns what usually does more than any conversation about empowerment.

Is This Just Delegation?

Delegation moves tasks. This is about who is allowed to think. You can delegate every task in your company and still be the only person making decisions, and plenty of founders have done exactly that and wondered why they are still the bottleneck.

The Struggle Is the Point

My son can tie his own shoes. He learned it in about a week, once I stopped.

The thing I was protecting him from was the thing that would have made him ready. That is true of most of the founders I work with, and the fix is rarely a new hire or a better system. It is a founder deciding to be less useful for a while.

If everything still runs through you, that is not a life sentence. It is a habit, on both sides, and habits come apart faster than you would think.

Schedule a Free Discovery Call