Why Your Team Keeps Bringing You Every Problem (And How You Trained Them To)
You know the drill. Someone leans into your doorway, or a Teams message pops up, or your phone buzzes with a "quick question."
"Do you have a minute? I'm not sure what to do about this."
And here's the thing: you do know what to do. You could probably tell them faster than they could even finish explaining the problem.
So you do. Problem solved. You're a hero for about four minutes.
Except tomorrow they're back. Thursday, someone else is standing in your doorway with a different version of the same question. Somewhere around week three, you notice you're spending half your day being everyone's answer key.
Now you feel like you’re crushing it as a contestant on Jeopardy. Answering fast and furious.
Here's the uncomfortable part: the problem isn't that you're too helpful or too knowledgeable. It's what your helpfulness has been quietly teaching your team.
Why You Became the Answer Machine
Give yourself some credit first. There are real reasons you do this.
You were probably promoted partly because you were good at solving problems. So now you know the answer, and you can get there faster than they can. You don't want to watch someone make an expensive mistake. And honestly, some days you just don't have twenty minutes for a coaching conversation; you've got a meeting in six.
Fair enough. Solving it yourself is almost always faster today.
It's next month where it costs you.
The Pattern You're Training Without Meaning To
Every time the loop runs the same way, a problem comes to you, you hand back an answer, you're teaching something, whether you mean to or not: when I'm not sure, I go ask.
Do that enough times, and people stop working through problems before they land on your desk. Their judgment never gets the reps it needs to get stronger. Every decision, even the small ones, starts drifting upward to you. You become the bottleneck. And then, this is the part that stings a little, you get frustrated that nobody on your team "takes ownership."
“Sometimes the manager complaining that nobody takes ownership is the same manager who keeps taking ownership back.”
Coaching vs. Rescuing — And Why It's Not That Simple
There's a name for the fix, and you've probably heard it before: coach, don't rescue.
Rescuing sounds like, "Here's what you should do." Coaching sounds like, "What do you think you should do?"
But don't turn this into a bit. If someone runs in and says the building's on fire, you don't respond with "Interesting, what do YOU think we should do?" That's not coaching. That's just annoying.
The goal was never to answer every question with a question. It's knowing when someone needs your answer, and when they need the room to find their own.
The One Question to Ask Yourself First
Before you jump in, run it through one filter: does this person need my answer, or do they need to think this through?
If it's on fire, urgent, risky, above their pay grade, genuinely outside what they know, give them the answer. That's not a coaching moment; that's just being their manager. Of course, you could circle back after and treat that time as a development opportunity.
If they've got what they need to work through it, the information, the judgment, the standing, that's your moment to coach instead.
And if you're not sure which one it is? Coach first. You can always add the guidance after. Does that make sense?
What to Say Instead of the Answer
A few lines that buy your team room to think instead of just handing them yours.
"What have you tried so far?" tells you whether they've actually wrestled with it or just walked straight to your door.
"What do you think is going on?" gets them interpreting the problem instead of just reporting it to you.
"What would you do if I weren't around?" is the single best question for breaking the habit of checking with you first.
And the one that changes the whole relationship: "What's your recommendation?"
That question moves the culture from bring me your problems to bring me your thinking. Say it enough times and people stop showing up empty-handed.
Don't Swing Too Far the Other Way
Now, don't take this and go full "I refuse to answer anything" on your team next week. That's not empowering anyone. That's just being unhelpful with extra steps.
Sometimes people genuinely need information only you have. Or context. Or a real decision. Or just permission to move forward. Good managers aren't withholding the answer to prove a point. They're just intentional about when they hand it over.
The Payoff
Coaching costs you more time up front. No getting around that.
But do it long enough, and the conversations start sounding different. Instead of "I don't know what to do," you start hearing, "Here's the situation, here's what I considered, here's what I'd recommend."
That's the whole shift. You stop carrying their problem and start sharpening their thinking. And that frees you up to actually do the parts of your job that need you — not the parts your team could've handled if you'd just given them the chance.
Your Turn
Reflect: Think back on the last three problems someone brought you. How fast did you land on the answer?
Assess: Where might your helpfulness be building dependence instead of confidence?
Engage: Next time someone brings you something they could reasonably work through themselves, don't answer right away. Ask one question first: "What do you think?"
Your job was never to be the person with all the answers. It's to build a team that doesn't need you to have them.
If this sounds familiar, it's exactly the kind of pattern we untangle in coaching.Book a discovery call and let's talk about what's actually happening on your team.
