Why Are Employees Afraid to Ask for Help at Work?

I once worked with a manager who would walk through the department and ask, “How are you going?”

It was a fair question. I've got no reason to think they didn't mean it. But by the time I'd started to answer, they were already halfway out of the department.

I've also worked with a manager who noticed I didn't seem myself. They stopped what they were doing, pulled me aside and said something like, “Come over here for a second, Dan. I want to ask you something. Is everything okay?”

I was flat out at the time. It wasn't the moment. So they said, “When you get a minute, come to my office or send me a message. I'll make sure I've got time.”

Both managers asked roughly the same question. The words weren't dramatically different.

The difference wasn't the question. It was whether there was actually room to answer it.

That isn't just a lesson about checking in on people. It's the same thing that shapes whether people ask for help. Saying you're available is easy. Creating a real opportunity for someone to tell you they need something is harder.

Most of us would say we're approachable. We say “my door's always open.” We say “ask me anything.” Then we're a bit puzzled when the questions don't come.

Here's how I've come to see it. A question is a small request for help. What you do next teaches that person, and often everyone watching, whether asking the next one is worth it.

Why are employees afraid to ask for help?

Confidence plays a part. Some people are just more comfortable putting their hand up. But it isn't the whole story.

Asking for help can feel risky. You might worry you'll look like you don't know what you're doing. You might remember a response that made you feel small. And you may be weighing up what happened the last time you asked, or the last time someone near you asked.

Over the years I've seen people stay quiet because they:

• were worried they'd done something wrong
• didn't want to look like they didn't know what they were doing
• felt embarrassed because they thought they should already know
• had been burnt before, when the response or the feedback that followed made them less willing to try again
• weren't comfortable saying “I'm not sure”

And sometimes the thing someone feels they should already know was never actually taught.

Research on employee silence points in a similar direction. In one exploratory study of issues people didn't raise with their managers, the reason mentioned most often was fear of being seen negatively and damaging relationships they valued.

Sometimes the question is there, but the perceived risk, embarrassment or sense that nothing will change makes staying quiet feel easier.

Asking for help and looking competent

Some of the people who most need to ask can feel least able to. New starters. Junior staff. People in workplaces with strong hierarchy or a relentless pace.

And experienced people who have just joined a new organisation. That group gets overlooked. Someone can be excellent at their job and still not know who signs off on what, or how things are done here. Professional experience isn't the same as organisational experience.

The irony is that hiding uncertainty to look competent can sometimes create the outcome people were trying to avoid.

A simple question isn't necessarily a sign that someone can't do the job. Often it's a sign they're trying to do it properly.

Why “Any questions?” often gets silence

Most of us have phrases we use without thinking:

• “Any questions?”
• “Everyone happy?”
• “Does that make sense?”
• “Let me know if you need anything.”

None of these are bad sentences. But they can lose their meaning when:

• you're already walking away as you say it
• it's asked in front of the group and nobody wants to go first
• everyone else has gone quiet
• the last question someone asked didn't go well
• there's no real time to answer honestly

That's the “How are you going?” manager again. The invitation was there. The opportunity wasn't.

The skill isn't finding the perfect sentence. It's creating a real chance to respond. A few things can help:

• Stay put long enough for an answer to arrive.
• Ask something more specific, like “What part of this are you least sure about?”
• Offer a quieter route: “If something comes up later, grab me or send me a message.”
• Mean it when they take you up on it.

Silence is a signal, not a diagnosis

Quiet doesn't automatically mean someone is scared, or that your team has a problem.

People go quiet for all sorts of reasons. They might be tired or flat out. They might need time to think before they talk. They might not want to interrupt. They might come from a workplace or culture where you don't question the person in charge. They might have decided nothing will change anyway. Some people are simply quieter, and that's fine.

What you might notice is that something seems different. A pause. A shift in posture. A hesitation. Maybe someone seems less confident than usual.

That doesn't tell you why. It just tells you it might be worth checking in.

So the useful response is curiosity, not diagnosis.

When I notice someone seems uncomfortable, my instinct is to get curious. Sometimes that's as simple as “Is everything okay?” If they still seem uneasy, I try to take the pressure off. Something like: “It's okay, you can tell me. I want to help. It's hard for me to help if I don't know what I'm helping with.”

That isn't a script. It's stopping, making a bit of space, and making it clear that asking is allowed.

What your response teaches people

This is the part that matters most.

Eventually someone will say one of these:

• “I don't know.”
• “I think I made a mistake.”
• “Can you check this?”
• “Can you help me?”

What happens in the next few seconds is a lesson. For them, and for anyone watching.

Be honest about the first reaction you might have. Frustration, because you're busy. “We went over this.” Worry about what the mistake means. A flicker of defensiveness if it touches something you own. Those reactions are normal. Having them doesn't make you a bad leader. The first step is noticing them in yourself.

Because the reaction isn't the response. The response is what you choose to do next. That space in between is where your leadership actually lives.

A few things tend to help:

• Pause before you react. Your face often answers before your words do.
• Get the facts before the judgement. Understand what happened first.
• Acknowledge that they raised it. Where it fits, “I'm glad you told me” costs nothing.
• Help with the immediate problem. Unpack it properly later.
• Be clear about what happens next.

Making it safer to speak up doesn't mean removing accountability. Mistakes still matter. Feedback still needs to happen. Sometimes there are consequences.

High standards and speaking up should sit side by side. The whole point is to hear about problems early enough to deal with them properly. If people learn that raising something gets them hammered, you may not end up with fewer problems. You may just hear about them later.

I'd rather answer a thousand simple questions

In emergency nursing, I've seen what can happen when uncertainty stays quiet. Someone doesn't get a second set of eyes on something because they weren't sure it was worth asking. A small concern has grown by the time anyone knows about it.

Most unasked questions don't lead anywhere bad. That's not the point. The point is that small uncertainty is usually easier to surface and deal with early than after it has grown.

It isn't only healthcare. Think about an educator who isn't sure they've read a child's plan correctly. An apprentice unsure about a step who doesn't want to look slow in front of the crew. A new starter in the office who guesses rather than asks.

Which is why I'd rather answer a thousand simple questions than deal with one bad outcome because a question was never asked.

What happens after they speak up

Listening well is a good start. It isn't the finish.

There are two quite different reasons people might stop asking. One is fear: something bad might happen if I speak. The other is futility: nothing will happen if I speak. Research on employee silence has identified both fear of consequences and the belief that speaking up won't make a difference.

You can respond warmly in the moment and still lose people if the conversation disappears afterwards. They raised it. You nodded. Then nothing.

That teaches something too.

You can't act on every suggestion or solve every problem. Nobody can. But you can acknowledge what was raised, be honest about what can and can't happen, name the next step, and go back to the person. Each of those is within your control, even when the outcome isn't.

In practice it might sound like:

• “Here's what I heard.”
• “Here's what I can do.”
• “Here's what I can't change, and why.”
• “I'm going to check this and come back to you tomorrow.”
• “This needs to go to someone else. I'll help you get it there.”

A clear “no, and here's why” can still show someone their concern was taken seriously. What wears trust down is a concern that seems to vanish.

Small responses become culture

This is why asking for help isn't only a confidence issue for your team to fix. It's a leadership one.

How well you know your own reactions shapes how you respond. How you respond, day after day, is everyday leadership. How you communicate in those moments affects whether someone asks again. And enough of those moments, across a whole team, become the culture. The unwritten rule about what happens here when you say “I'm not sure.”

You don't build that with a poster or a line in a team meeting. You build it one response at a time.

If this is something your team is working on, it's the kind of thing we practise in practical Human Skills workshops: noticing the reaction, slowing the response and making real room for people to ask for help.

Think about the last time someone asked you something they probably felt they should already know. What did your response teach them about asking the next one?

Frequently asked questions