How to Ask for Help at Work

You already know you should ask for help. The hard part is the moment right before you do it — when you convince yourself you should be able to figure this out alone, so you stay quiet and lose an hour, or a week. This guide is about closing that gap: how to ask for help at work in a way that gets you unstuck fast and makes you look more capable, not less.
What’s inside
Why asking for help feels risky (and why the fear is usually wrong)
How to know when it’s time to ask
Getting clear on what you actually need
Who to ask, and why it’s rarely your manager first
How to phrase the ask so it’s easy to say yes to
What to do when someone says no or goes quiet
Making help a two-way street
Asking for help on the big stuff, not just the small stuff
Why asking for help feels risky
Most of us carry a quiet belief that needing help is a signal of not being good enough. So we frame the choice as: ask and look incompetent, or struggle and protect our reputation. That framing is almost always backwards.
Think about the last time a colleague asked you a sharp, specific question. You probably didn’t think less of them — you thought they were engaged, and you were glad they came to you before things went sideways. The same is true when it’s your turn. The people who never ask questions at work aren’t seen as the strongest; they’re the ones whose work quietly drifts off course while everyone assumes they’re fine.
The real risk isn’t asking. It’s spending days stuck on something a five-minute conversation would have solved, then having to explain the delay. Naming that fear honestly is the first step to getting past it.
How to know when it’s time to ask
Waiting too long is the classic mistake, but so is asking before you’ve tried anything. The sweet spot is somewhere in between, and you can find it with a simple rule of thumb.
Give yourself a fixed window — say 30 minutes for a small blocker, a day for something larger. In that time, try the obvious paths: search the docs, reread the brief, attempt one or two approaches, write down exactly where you get stuck. If you’re still blocked when the timer runs out, that’s your cue. You’ve earned the ask, and you now have something concrete to show for your effort.
This matters because it changes the shape of the conversation. Instead of “I don’t know how to do this,” you arrive with “I tried X and Y, here’s what happened, here’s where I’m stuck.” That’s not a cry for help — it’s a status update with a clear request attached. It respects the other person’s time and proves you’re not outsourcing your thinking.
Get clear on what you actually need
Vague asks get vague help. “Can you help me with this project?” puts all the work of figuring out what you need onto the other person, and most people, sensing the size of that, will stall.
Before you reach out, spend two minutes sorting your need into one of a few buckets. Do you need a decision (“which of these two directions should I take?”), information (“where does the updated data live?”), a skill (“can you show me how you’d approach this?”), or a second opinion (“does this logic hold up?”)? Each one asks for something different, and naming it changes everything.
The clearer you are, the smaller the favor feels. “Can I get 15 minutes to sanity-check my approach before I build it?” is easy to say yes to. It has edges. The person knows what they’re agreeing to and roughly how long it’ll take. Getting help at work is far less about courage than it is about precision — do the thinking up front, and the ask almost makes itself.
Who to ask, and why it’s rarely your manager first
By default, many people escalate straight to their manager, which is often the slowest and most expensive route. Your manager is usually a level removed from the details and busy with things only they can do. There’s frequently someone closer to the work who can help faster and with less friction.
Map your options before you pick. Is there a peer who solved this exact thing last quarter? A teammate one desk over who owns the system you’re stuck in? Someone junior who happens to be the resident expert on that tool? Spreading your questions across a few people also keeps you from leaning too hard on any one person’s goodwill.
Save your manager for the things that genuinely need them: priorities, tradeoffs, unblocking a dependency, or a decision above your pay grade. And when you do go to a peer, a little context helps — “you mentioned you’d wrestled with this” tells them why you chose them and makes the ask feel personal rather than random. If you’re feeling generally stuck rather than blocked on one task, that’s a different conversation worth having too, and it doesn’t mean your career is stuck.
How to phrase the ask so it’s easy to say yes to
A good ask has three parts, and it’s short. First, the context in a sentence: what you’re working on and why. Second, what you’ve already tried, so they know where to pick up. Third, the specific request, ideally with a scope: “Could you point me in the right direction?” or “Do you have 15 minutes this week?”
Here’s the difference in practice. Weak: “Hey, do you know anything about the billing system? I’m really confused.” Strong: “I’m reconciling the Q3 invoices and I’ve traced the mismatch to the refund logic, but I can’t tell if it’s expected behavior. You built this — could I grab 10 minutes to walk through it?”
The second version tells them exactly what they’re signing up for. It shows respect for their time and competence, and it makes helping you feel quick and satisfying rather than open-ended. Notice you’re not apologizing or padding the message with “so sorry to bother you.” Confident, specific asks land better than anxious ones — and they’re a skill you build by treating learning as the point, not the price.
What to do when someone says no or goes quiet
Sometimes the person you ask is slammed, forgets, or simply says no. This is normal and rarely personal. The trick is to not let a single non-answer send you back into silent struggling.
If someone goes quiet, wait a reasonable beat, then follow up once — briefly and without guilt-tripping. “Just floating this back up in case it got buried” is plenty. If they’re too busy, ask if there’s someone else they’d point you to; people who can’t help often know exactly who can. And if the answer is a flat no, take it at face value and move to the next name on your list rather than reading it as a verdict on you.
The deeper skill here is not tying your sense of worth to any one response. You’re gathering what you need to do good work. Some doors open, some don’t, and you keep knocking. Treating the search as logistics rather than a referendum on whether people like you keeps you moving.
Make help a two-way street
Asking gets dramatically easier when you’re known as someone who gives. The colleague you helped debug something last month is the one who’ll clear their afternoon for you now, without a second thought.
So be generous with your own help, and just as importantly, close the loop when someone helps you. Tell them how it turned out: “That pointer on the refund logic was exactly it — fixed and shipped, thank you.” It costs you thirty seconds and it does real work. It makes people feel their time was well spent, and it makes them glad to be asked again.
Over time this builds something more valuable than any single answer: a web of people who trust each other and trade help freely. That’s what a healthy team actually runs on. Advocating for what you need — including support — is a muscle, and there’s more room for growth in asking than most people use. The people who ask well and give well tend to be at the center of how work actually gets done.
Asking for help on the big stuff
The same skills scale up. It’s one thing to ask how a system works; it’s another to say “I’m in over my head on this project” or “I don’t think I’m growing here and I want your read.” Those asks feel bigger because more of your ego is on the line, but the mechanics are identical: be specific, show your thinking, ask a real question.
Big asks are also where you most need someone outside the immediate situation — a mentor, a peer in another team, someone who isn’t scoring you. They can tell you things your manager can’t, precisely because nothing’s at stake for them. Don’t wait for a crisis to build those relationships; the time to find people you can ask hard questions is before you desperately need them.
And notice which questions keep coming back. If you’re repeatedly stuck on the same thing, that’s not a nuisance — it’s a signal about a skill to build, a process that’s broken, or a conversation you’ve been avoiding.
How Blomma helps you ask better
Most of the difficulty in asking for help isn’t the ask itself — it’s the loop beforehand, where you talk yourself out of it or can’t find the words. That’s exactly the moment Blomma is built for. It’s an always-on career coach you can open at 11pm before a big meeting, or in the ten minutes before you send that Slack message.
You can draft the exact ask and have Blomma pressure-test it: Is it specific? Is it easy to say yes to? Are you asking the right person? You can talk through whether now is the time or whether to try one more thing first. And because it’s private and always available, there’s no risk in thinking out loud — no one’s watching you figure out what you need. Over time, the reps add up, and asking for help stops feeling like a confession and starts feeling like just another thing capable people do.
Practice your next ask with Blomma free →
Related reading
Your career isn’t stuck
There is nothing cooler than learning
Introducing room for growth
