How to ask for help effectively at work
New hires often wait too long to ask for help, then ask in a way that makes the helper do all the work. Here's the version that gets faster answers and builds relationships.
There are two failure modes when asking for help at work. The first is not asking at all: you sit with a problem for two hours, don’t want to seem incompetent, and eventually either figure it out the slow way or produce something that’s subtly wrong because you were missing context. The second failure mode is asking poorly: “can you help me with this?” with no context, no indication of what you’ve tried, and no clear picture of what help would actually look like.
Both failure modes cost you time. The first costs you more.
What asking for help actually signals
There is a belief, especially in the first year, that asking for help signals weakness or incompetence. This is almost entirely backward. The behaviors that signal weakness are: being stuck and not flagging it, delivering wrong work because you assumed instead of asked, and asking the same question twice without learning from the first answer.
Asking for help, when done well, signals the opposite of weakness. It signals that you know the difference between what you know and what you don’t. That distinction is one of the clearest markers of someone operating at or above their level.
Your manager and your colleagues want you to ask. Not because they enjoy answering questions but because the alternative is you producing wrong work and everyone redoing it later.
What the person you’re asking is trying to do
The colleague or manager you’re asking is trying to get through their own day. They have their own list and their own deadlines. Every help request lands as a small tax on their attention.
The version of the request that produces a fast, useful response gives them enough context to answer without asking clarifying questions, demonstrates that you’ve already done some work toward the answer, and makes the ask specific enough that the answer can be short. That combination is respectful of their time and easy to act on.
The version that doesn’t work: “can you help me with this?” attached to a long explanation of everything you’re confused about. They now have to read the background, figure out what you actually need, and essentially do your thinking for you. That tax is large. Busy people unconsciously deprioritize large taxes.
The framework: PARE
Before you ask for help, quickly run through four questions:
P, Problem. Can you state the problem in one sentence? If you can’t state it clearly, you don’t understand it well enough to ask someone else to solve it. Clarifying the problem often reveals that you already have most of the answer.
A, Attempts. What have you tried? Two attempts minimum before asking another person. Not because asking is bad, but because most problems have answers in accessible places, and trying first builds the pattern-recognition that makes you faster over time.
R, Request. What specifically are you asking for? A quick answer, a 10-minute explanation, a sanity check on your approach, a connection to the right person? Know this before you send the message.
E, Easy exit. Give the person an easy out if they’re not the right resource: “Or if there’s a better person to ask, I’ll start there.” This reads as considerate and is often how you end up routed to the right person faster anyway.
The ask structure in practice
In Slack or conversation:
“I’m stuck on [specific thing]. I’ve tried [attempt 1] and [attempt 2] and the part I can’t figure out is [precise question]. Do you have a quick answer, or know who would?”
In an email where you need more space:
State the context (one sentence), what you’ve tried (two bullets), the specific question (one sentence), and what kind of help you need (answer / conversation / sanity check).
That structure works across contexts, across seniority levels, and across levels of urgency. The only variable is how much context the recipient needs to understand the question.
The thank-you that keeps the relationship strong
After someone helps you, close the loop. Two sentences:
“Got it, that makes sense. I’ll [do X]. Thanks.”
Or, if their help led to an outcome worth sharing:
“Quick update: I tried [what they suggested] and it worked. [One-line result]. Appreciate the help.”
This is not ceremonial. It tells the person their time was well spent, and it makes them more likely to help you again. The colleagues who build the strongest help networks in their first years are the ones who close loops consistently. It compounds in a way that’s hard to overstate.
Asking for help well is a professional skill like any other. The version you use in year one will be different from the version you use in year five, but the core structure, clear problem, documented attempts, specific ask, is the same at every level.
Further reading
Filed under: Career Development , Career Development
Cubicle To Corner Office
The 317-page playbook for the transition from student to professional.
Related pieces
Promotion pathways: the 3 levers that matter (even if no one says it)
Most promotion advice tells you to 'do great work.' Here's what actually moves the needle: scope, visibility, and advocacy from people who aren't your direct manager.
Expat first job: the unspoken rules you need to learn fast
In a new country, 'professionalism' may look nothing like what you expected. Here's how to decode the unwritten norms before they decode you.
Office politics for nice people: influence without manipulation
You don't have to become someone you're not to navigate political dynamics at work. You just have to understand what's actually happening.
Join the conversation
Real readers (and Mike) reply in here. The number next to each comment is its upvote score — sign in with just a display name to add your vote or post a reply. No email or password required.