Your Team Still Comes to You Instead of Your Manager. How to Stop It
Your team keeps coming to you because your answer still outranks your manager's. It stops when that changes. Move every question, approval and client relationship that still reaches you over to the manager with the decision written down, send people back without answering, and never overturn the manager's call in front of the team.
Picture 7:40 on a Tuesday morning. Your phone lights up with a text from your most senior tech asking whether he can bump tomorrow's install to squeeze in a repeat customer who called last night. Your operations manager is in the office, about thirty feet from where you're standing. The tech knows that. He texted you anyway.
You hired the manager so you could step out of the day-to-day and grow your profits with systems that scale. Owners on our calls describe the hope in plain words: someone who can "answer to a little bit higher level," so they "don't have to keep getting pulled in." When employees bypass the manager and go to the owner, the pulling-in carries on, and the manager's salary sits on top of your time instead of replacing it.
Most advice puts the fix on the team or the manager, telling them to give it time or respect the chain of command. The bigger lever sits with you, because the old route stays open as long as your answer can overrule the new one.
Why does the team skip the manager?
Going to you still gets a better result. Your answer comes faster and nobody above you can reverse it, so anyone who wants a decision that sticks takes the question to the person with the final word.
Your team follows the org chart they've watched in action, which may not match the one you drew. If you've ever adjusted a manager's call after someone complained to you, or answered a question "just this once" because it was quicker, people noticed. They learned that the manager's answer is a first draft and yours is the version that counts.
A few habits keep that route open without anyone meaning to:
- You're still in the group chat, and you reply first because you know the answer.
- Long-serving staff have a direct line to you that predates the manager.
- Key clients still have your cell number, so their problems start with you.
- The manager holds the title without written authority, so even they check with you.
Each of these is a dependency, a kind of question that still has to pass through you before work can move. That makes it a systems problem, and it has a method.
What decisions does the manager need in writing?
Every kind of decision your team still brings to you, written down with a limit and the reason behind it. Written authority makes the manager's answer as final as yours, which removes the reason to shop for a second opinion.
Build the map first. Imagine being out of contact for a full week and list everything that would land on your desk or sit waiting. Stretch it to a month and the list grows, picking up things like month-end billing questions or the quarterly check-in with your biggest account. Every item is a route the team still takes around the manager. In most service businesses, those routes fall into these groups, roughly in order of revenue risk:
- Client relationships and escalations. Accounts that call you directly, and complaints that go straight to the owner.
- Pricing and quote exceptions. Discounts, rush jobs, scope changes and anything off the standard price.
- Scheduling and priority calls. Which job goes first when two can't both happen.
- Spending and purchasing. Parts, subcontractors and equipment above what a crew lead can approve alone.
- People decisions. Time off, overtime, performance conversations and complaints about the manager.
- Quality calls. Whether a job is finished well enough to invoice.
Work from the top. Move one group at a time to the manager with a written rule covering what they decide, up to what limit, and what that limit protects. If you've already sorted your decisions by type, as in the guide to sorting decisions so you stop being the bottleneck, this is where those limits get the manager's name beside them. Keep going until nothing that touches revenue still has to come through you.
The written part does more work than owners expect. A tech who dislikes a verbal answer from the manager has every reason to check with you. A tech who can see the manager applied a rule you both signed has nobody left to appeal to.
What do I say when someone comes to me anyway?
Send them to the manager without giving the answer, even when you know it and it would take ten seconds. Then tell the manager it happened, so they can close the loop and you can see which route is still open.
The tempting middle ground is to answer and redirect at once: "I'd probably do it this way, but run it past the manager." That hint becomes the decision, and the manager is left approving your call. The team learns you're still where the real answer lives.
Agree with the manager ahead of time on the true exceptions, such as safety or a client's money at immediate risk. Everything else goes back, including questions from people you've worked beside for years.
Treat every bypass as information. A question that keeps reaching you marks an item on your map with no written rule yet, or a rule the team doesn't trust. One owner described the change they wanted as "asking more questions to get their recommendations, rather than probably me jumping in as quickly as I have in the past." Sending someone back is that change, made at the moment it matters most.
How do I announce the change so it sticks?
Announce specific decisions as they move across, and say plainly that you'll send people back. A blanket "go to the manager from now on" fails because nobody knows which questions it covers, so the uncertain ones keep coming to you.
An announcement that holds names the decision area, who owns it now, what you're keeping, and what happens if someone brings it to you anyway. Make it with the manager standing beside you, so nobody hears it secondhand. Then announce again each time another group from your map moves, instead of handing over everything in one meeting. Clients get their own version: you introduce the manager as the person who now handles their work, and you step back once they've had good answers from the manager a few times.
The meeting buys you some attention, but the change sticks the first time someone tests it and gets sent back, and your team will watch that moment more closely than anything you said in the room.
How do I back the manager when I'd decide differently?
Let the call stand when it sits inside their written limit, discuss it privately, and change the rule for next time while the decision stays put. Reverse a call only for safety, legal exposure or serious money, and have the manager deliver the reversal.
Most calls you'd make differently still work for the client and the margin. The few that don't show you the written rule was missing something, so rewrite it together. An owner on one of our calls drew the line this way: "I trust… my people to make good decisions. Except when it comes to the big money items." That's a fair line, provided it's drawn in writing beforehand and not after a decision you didn't like.
Overruling the manager where the team can see it sends everyone straight back to your desk, because it proves your answer is still final. A quiet conversation and a better rule cost you one decision made slightly differently, and they keep the new route open.
How do I know the team has switched to the manager?
The only questions that reach you are the ones you chose to keep, like a change to your price list, a senior hire or the direction for next year. On a weekday morning your phone is quiet, and nothing waits for you to get back.
In practice:
- The manager answers questions that used to come to you, and nobody checks with you afterward.
- Your larger clients call the manager first and are happy to.
- The weekly operating meeting runs on the manager's agenda, and it still happens on the days you're out.
- When you test it with a week away, and later a month, the list of things that waited for you is short, and each test makes it shorter.
That's when the manager hire starts paying for itself. Your hours move to the work that grows profit, and the business gets closer to what making your business run without you describes in full, where revenue keeps coming in whether or not you're in the building. If your manager is still learning the work itself, getting a new manager up to speed in their first month covers that side.
If you'd like help mapping which routes still run through you and building the written systems that close them, that's what a Planning Call is for. Bring the list of questions still reaching you, and we'll work out together which routes to move first.
Frequently asked questions
Should I stop answering my team completely?
No. Stop answering the questions that now belong to the manager. You still own direction, major pricing, key hires and anything else you've deliberately kept. Tell the team what those are, so a question that genuinely belongs to you still reaches you, and everything else goes to the manager without anyone having to guess.
What if the team says the manager is getting it wrong?
Listen, then pass the feedback to the manager instead of acting on it yourself. If the complaints point to a pattern, fix the written rule with the manager in private. Settling it directly with the team shows them that complaining to you overturns the manager, and the bypassing gets worse.
What if a long-time employee keeps coming to me?
Expect it, since their route to you is the oldest one in the business. Send them back the same way you would anyone else, and tell them privately why it matters to you. Once the manager has written authority and you hold the line, the habit fades because the route stops working.
How long until my team stops coming to me?
It depends on how many routes are on your map and how consistently you send people back. Each group tends to settle once the team has watched the manager's answer hold a few times without you stepping in. Answering even occasionally resets the clock, so consistency counts for more than speed.
