Guides / Guide

Asking for help in a new job without wasting anyone's time

By Michael Shreeves · 3 October 2026 · HR & People · 3 min read

Background

New starters tend to go wrong on asking for help in one of two ways. Some ask about everything, straight away, and wear out their colleagues. Others ask hardly anything, because they don't want to look like they can't cope, and then turn up on Friday with a problem that's been growing since Tuesday.

The middle path is a habit you can learn. It comes down to knowing how long to try, what to say, and what to write down afterwards.

It's worth saying to the people being asked as well: a good question is a compliment. It shows the person's paying attention, and one that comes with what they've already tried takes thirty seconds to answer.

Setup

The 15-minute rule

Try on your own for about fifteen minutes. Longer if it's a learning exercise, shorter if you're blocking someone else or it's urgent. Then ask. Fifteen minutes of honest effort is worth more than an hour of quiet panic.

The shape of a good question

Four parts, and it fits in a message:

  1. What I'm trying to do. One line.
  2. What I tried. Two or three things, briefly.
  3. What happened. The error, the result, what looked wrong.
  4. What I think might be the answer, if I have a guess.

For example: "I'm trying to get the monthly report out for the clinic leads. I've used last month's template and re-run the export, but the totals for Sheffield are zero. I think it might be the date filter, but I'm not sure. Can you take a look?"

Compare that to "The report's broken." One takes a minute to answer. The other takes a ten-minute conversation just to find out what the problem is.

Pick the right person and the right channel

  • Quick and low risk: a chat message to your buddy or the team channel. Other people may learn from the answer.
  • Needs thought: an email, or a booked ten minutes. Don't corner someone mid-task.
  • Urgent or blocking: call. Say it's urgent and why.
  • About how you're doing, rather than the work: your manager, in your one-to-one.

Keep a "things I've learned" file

When someone answers, write it down, with the date. After a month you'll have a personal guide, and you'll stop asking the same question twice. People do notice that.

Using an AI tool for the "what did they mean" questions

For jargon, a first draft, or how a process might work in general, an AI tool is a quick place to start. Don't put in anything confidential, and don't take its answer as how your organisation does things. It doesn't know.

I've just started as [ROLE] at [TYPE OF ORGANISATION]. My colleague said
"[PHRASE OR INSTRUCTION]". What might they mean? Give me two or three
possibilities and a question I could ask them to find out which.

Edge Cases & BCP

  • The person you ask is always busy. Ask when they're free, not when you are. Say how long it'll take: "Two minutes, whenever suits."
  • You get a different answer from two people. That's normal, and often means there's no agreed way. Tell your manager, because it's worth fixing.
  • You asked and still don't understand. Say "Can I check I've got this?" and repeat it back in your words. It saves a wrong guess later.
  • You feel embarrassed. Most people do in their first month, and the people who've been there longest tend to remember it.
  • If you manage someone new, say out loud that questions are welcome, and answer the first few warmly. That sets the tone for the next six months.

← All guides