Don't Hand Them the Answer

The Silence You Need to Stop Filling

When someone on your team says "I don't know," you probably say something. You give a suggestion, reframe the problem, offer a direction. It feels like help. It looks like leadership. It is, almost without exception, the exact wrong move.

Here's what's actually happening: the moment you fill that silence, you teach them that silence works. They don't have to develop a point of view because you'll supply one. And over time, they stop trying. You end up with a team that's increasingly dependent on you to do the thinking, and you end up in more and more meetings wondering why no one has any initiative.

That's not a team problem. It's a pattern you trained.

What "I Don't Know" Usually Means

Let's be honest about what "I don't know" actually is. In most cases, it's not an accurate report of cognitive state. It's a stall. Sometimes it's deference, someone who doesn't want to overstep or guess wrong in front of their manager. Sometimes it's fear, being wrong feels worse than saying nothing. Sometimes it's just habit, because previous managers always answered for them so they learned to wait.

Genuinely not knowing the answer is rarer than it sounds. The more common scenario is that they have some idea, maybe a fragile one, maybe an unformed one, but they're not ready to commit to it. And if you let them off the hook, they never will be.

I started noticing this pattern years ago when I was running a fairly large team. Someone would come to me with a problem, I'd ask what they thought, and before they finished saying "I don't know" I was already talking. I thought I was being efficient. I was being efficient. I was also slowly becoming the only person on my team who was paid to think.

The Mechanics of Holding

The move itself is not complicated. When someone says "I don't know," you say something like: "Just give me one idea. Doesn't have to be the right one."

Then you wait.

This is where most managers fold. Silence is uncomfortable, especially when you know the answer and you're watching someone struggle to find it. Ten seconds feels like a minute. Fifteen seconds feels like a job performance issue. But if you can sit in that discomfort, most people will find something within fifteen seconds. Often it's the right answer. Sometimes it's close. Either way, they did the work.

Your job during the silence is to look neutral. Not expectant, not impatient, not encouraging in a cheerleader way. Just present. You're holding space for them to think, and you're signaling with your posture that you're not going anywhere.

If they push back again, "I really don't know, I have no idea," you have one more tool before you step in. Offer a possibility and make them evaluate it. "What if we handled it this way? Would that work?" Now they're still doing the thinking, just with a starting point. You have not given them the answer. You've given them a foothold and asked them to climb.

Why This Is Different From Just Asking Questions

There's a management concept called coaching that gets thrown around a lot and means almost nothing by the time most organizations are done with it. So let me say this plainly: what I'm describing is a specific behavior, not a philosophy. It is a structured refusal to do the cognitive work that someone else can do.

Telling someone the answer is a one-way transfer. It is fast, and it has a half-life of about four hours. When you hand someone a solution, they nod, they might write it down, and they forget it by lunch because it never required them to think.

When they generate part of the answer, something different happens. They own it. By the time you both agree on the next step, they are already bought in because the answer has their fingerprints on it. The implementation goes better. The follow-through goes better. And the next time a similar problem comes up, they have a memory of having solved it, which means they're more likely to try again before bringing it to you.

That's the compounding effect. People who get asked to think start thinking. People who get told stop trying. Over a year, those two trajectories look radically different.

When to Break the Rule

There are situations where you just tell someone what to do. I want to be clear about when those are.

If there's a safety issue, an emergency, or a time-sensitive crisis where deliberation costs something real, tell them. This framework is not for those moments. "I need you to call the client right now and tell them we're delaying the shipment" is not a coaching moment. It's a fire.

Similarly, if someone genuinely hasn't been exposed to a type of problem before, the socratic approach is going to frustrate them and stall you. They can't think their way to knowledge they don't have. You give them the context they're missing, then start asking questions.

And if someone is new to the role or new to the team, calibrate. You're building the relationship and building the trust at the same time. You can introduce this approach gradually rather than sitting in silence across from someone in their second week who thinks they've already disappointed you.

The rule isn't "never answer." The rule is: don't answer when they could.

The Trap of Being the Smartest Person in the Room

There's an ego piece here that's worth naming. If you're good at your job, and most people reading this are, you probably do know the answer. You've seen this problem before. You could solve it faster than they can.

That's exactly what makes this hard. It feels productive to solve it for them. It feels like you're adding value. And you are, in the narrowest possible frame. You solved this one problem. You also made it slightly more likely that they'll bring you the next one instead of handling it themselves.

Being the smartest person in the room is a trap. It feels like success and it stunts everyone around you, including you. Because eventually you are spending your days in one-on-ones solving problems that your team should be solving, and you're not doing whatever you're supposed to be doing at your level.

What to Do Today

Pick one meeting from your calendar this week. A one-on-one, a problem-solving session, anything where someone is likely to ask you what to do or how to handle something. Go in with one commitment: when you ask them what they think and they say "I don't know," wait fifteen seconds before you say anything.

Fifteen seconds. That's it.

You will almost certainly hear something come out of their mouth that surprises you. Maybe it's the answer. Maybe it's wrong and it's useful anyway. Either way, you've just created a small opening where a new habit can start.

Do it enough times and you stop being the answer machine. You become the person who taught them how to think. That's a better job.