The four things your team actually wants when they bring you a problem, and the one question that tells you which.
Your teammate has poked their head in your office. "Got a sec? The Smiths are upset about the install date." Before they've even finished speaking, you're already halfway to the solution. "Call the supplier and check in on timeline again, we can get a credit issued, I'll email them myself."
Whoa there. I hope you just bristled reading that. I bristled writing it.
But, it wasn't always that way. I used to think this was good leadership. You might say it is. After all, it's efficient, helpful, and the problem is sorted.
For years, your value was measured by how quickly you solved problems, am I right? Customers came to you with problems and left with answers, and the faster you took care of them, the more trusted you became. That, my friend, earned you the promotion. Unfortunately, on your way to the manager's desk, someone forgot to tell you that doing that very thing, for your team, lands a whole different way. And it doesn't feel good.
I've been doing this work for over twenty years and I still catch myself. If you know me, you know I LOVE problem solving for customers. So it's hard to turn that off. What helped me most was learning that people bring me a problem for one of four reasons, and only one of them is "tell me what to do."
The four requests:
Hear me. They don't need a solution. What they need is 30 seconds to say "That customer was brutal" to someone who understands. If you go into fix mode, you've missed the whole point. What they need from you: listen, name it, and let it go. "That sounds like a rough call. You handled it."
Help me think. They have a few ideas, but lack a bit of confidence in which one might be the best option. They need a sounding board, someone to test their ideas with. If you give them the answer, they will take it, but you haven't helped build their confidence any. Here's your question: "What are you leaning toward? What's making you hesitate?"
Decide for me. Sometimes, they really don't know and they need your expertise. Or they need a little pull that they might not have. A refund outside of regular policy, a call that affects another team. Here, a fast answer is respectful. Make the decision, explain it in one sentence, and tell them what they can decide on their own next time.
Back me up. They know what to do, but don't want to proceed until they know you will stand behind them if they are challenged. What they need: "Go for it. If anyone questions it, I have your back."
The question that tells you which.
You don't need to try to read between the lines or guess here. Just ask:
"What do you need from me on this one? Should I only listen, help you think it through, make the call, or back you up?"
It may feel a bit awkward the first time you ask. Ask it anyway. Within two or three weeks your team will start opening with the answer: "I just need to vent for a sec" or "I've got a plan, do you have a minute to hear it?" That's when you get hours of your week back, because most of those problems were never yours to solve.
Where this shows up most.
In my experience, three places. In the hall, when someone grabs you between meetings and you answer on autopilot. The 4:55 message, when you're tired and fixing it is faster than asking. And the customer escalation, when the stakes feel high enough that you jump straight to "decide for me" without knowing if you should.
When you should just answer.
There are some variables that may apply. Here they are: If a customer is on the line right now, if there's a safety issue, or if your rep is brand new and genuinely doesn't know, answer. But be careful of leaning on these too often, or you're right back in the trap.
If you have been the fixer for months, your team has learned to bring you everything ready for fixing. When you start asking this question, you could expect a week or two of confused looks. Consider owning the learning opportunity. Apologize to the team for getting it wrong for a while in how you have been coaching them and let them know you are going to be trying to shift the way you lead. That you believe in them and their abilities and you will be finding out first what they truly need from you in the future.
Something like: "I've been jumping in with answers when what you needed was for me to listen, or to trust your call. That's on me. From now on I'm going to ask what you need first."
You will likely find them breathe a sigh of relief and say "about time."
You were promoted because you had the answers. Your team gets stronger the day you stop assuming that's what they came for.
Think back to the last problem someone brought to your desk. Which of the four was it really?