You're heads down, preparing for an upcoming leadership meeting, when your team member pings you with the sixth question about an assignment you gave them yesterday. Not about the deadline, nor confirming the budget. It's about what font to use in a document that maybe three people will ever see. You feel the instinct to respond"Figure it out yourself!!" build in your chest.

Or maybe you thought about going to Reddit and asking: "What do I do about a team member who asks too many questions?!" 

Before you do either, watch this week's video, which shows what happens when a manager tells their team member they ask too many questions - but from the other seat. I play HR, coaching a team member through what to actually do after hearing that feedback from their own manager.

Watch the video here. And if you're the manager who said it - or the one who's been thinking it - this post's for you.

What "Too Many Questions" Feedback Actually Means

Even when you feel fed up, it's rarely about the actual number of questions. It's a proxy for one of three things:

- You're overwhelmed, and the next question - literally any question - feels like one more thing landing on a pile that's already towering on your desk.

- You haven't drawn the lines. Nobody told this person what's theirs to decide versus what needs your sign-off, so they're asking about everything because they don't know which bucket anything falls into.

- You haven't seen them decide well yet, so every question feels like proof they can't be trusted with more.

Only one of those three is actually about them. The other two are about you.

Why It's Bad Feedback - Even When You have a Good Point

You might be completely right that this person needs to ask fewer questions. But if that's all you say, that's not going to help them.

Feedback without a specific example doesn't change behavior. It just makes someone anxious and unsure what to do differently, which - if you've ever gotten vague feedback yourself - usually produces a lot more hesitation, not less. It means they still have the questions... now they're just afraid to ask them.

A quick gut check before you say it:

- Am I frustrated with them, or with everything else currently on my plate?

- Have I actually told them what they can decide without me - out loud, not just in my head?

- Would I honestly rather they guess and risk getting it wrong than ask and get it right?

If any of those rings true, the answer isn't telling them to ask less. It's telling them what to ask about.

The Fix: Set the Guardrails Before They Have to Ask

The best time to prevent "too many questions" is before the questions start - at the moment you hand off the work. Proactively give your team member three things, every time:

1. What I need to know from you. The non-negotiables - the deadline, the budget, the thing the client actually asked for.

2. What's completely yours to decide. Format, structure, how they get there - their call, no check-in required.

3. What to flag me on - and how. The one or two things that, if they come up, you genuinely want to hear about before they're solved. And also how to do that - what they should reach out to you about immediately, and what can wait until your next 1:1.

Here's what that sounds like in practice:

"Before you get started, let's do a quick two minutes. Here's what I actually need from you on this: the client wants X and Y by Friday. I'll give you examples of how we've done it previously, but there are things you can decide: format, structure, how you organize the research - those are your call. If something's getting in the way, or the client asks for something new, let me know ASAP. Everything else, run with it."

That's it. Two minutes up front can buy you a project's worth of fewer "is this okay? What about this?" pings - and it's the same framework I'm coaching the employee in this week's video to bring to their manager, from the other side.

If You've Already Said It, Here's What to Say Now

If "you ask too many questions" already left your mouth without the context behind it, you don't need to pretend it didn't happen (which is what many people would do - but not you!). You need to have a follow-up conversation:

"Hey, I want to follow up on something I said last week. I told you that you ask too many questions, and I didn't give you anything to actually do with that - that's on me. What I actually meant is I want us to get better at me telling you upfront what's yours to decide versus what needs my input. I want you to ask questions, but I don't want you to feel like you have to ask so many questions. Let's talk specifically about how we can try that on the next project."

When you have this conversation, it does more for trust than the original comment did damage. When you don't, it just sits there as a thing they're now quietly afraid of doing again - which, ironically, tends to produce more hesitation and double-checking questions, not less.

Want every manager in your org communicating this clearly - without you having to coach each one individually? Manager Method's leadership platform helps you do that - much more easily than you think. If you're in HR or L&D, set up a call for a custom demo.

Building this skill for yourself first? Manager 201 covers the strategic leadership side - including how to delegate with the kind of clarity that prevents this exact feedback loop.