How to ask questions at work (script and examples)

Being new means you’ll have questions. That’s not a character flaw. That’s the job.

The problem is most new hires send the wrong shape of question. You ask “where’s the doc?” or “what should I do?” and you get a vague answer back, which is worse than no answer because now you’re stuck and embarrassed.

Twenty minutes of homework + a tight question = a tight answer. Every time.

Questions aren’t interruptions — surprises are

Most managers don’t get annoyed by questions. They get annoyed by:

• Vague questions (“what should I do?”)
• Late questions asked after you already built the wrong thing
• Drive-by questions that force them to do the thinking you should have done

A good question is a mini status update: here’s the goal, here’s what I tried, here’s what I think, here’s what I need. That structure makes you look competent even when you’re missing context.

The 60-second question script

When in doubt, use this. Works in Slack, email, in person.

1. Frame the goal.

“Quick question — I’m trying to make sure I do this the right way before I go too far.”

If it’s time-sensitive:

“I’m blocked on X. If I can get two minutes of direction, I can keep moving.”

2. Share what you know (one to three sentences).

“Here’s what I understand so far: the deliverable is ___, and the audience is ___.”

3. Show what you tried. Just show you took a swing.

“I checked the docs and old tickets and found ___. I tried ___, but I’m still unclear on ___.”

4. Offer your best guess. This is the part that upgrades you from “junior asking for help” to “teammate making progress.”

“My current plan is to do ___ because ___.”

5. Ask a specific question — yes/no, A/B, or “what’s the standard?”

“Is that the right approach?” / “Should we do A or B? I recommend A. Any objections?”

6. Confirm the next step. Repeat back the decision.

“Got it. I’ll do ___ by ___ and send you an update.”

That’s it.

Five examples (with exact wording)

Unclear deliverable:

“I want to make sure I’m hitting the bar. When you say ‘draft,’ do you mean a rough outline for feedback, or something you’d be comfortable forwarding to stakeholders? I’m planning to do an outline plus three key slides today. If you want something more polished, tell me and I’ll adjust.”

You named the ambiguity and proposed a default.

Asking for context without sounding lazy:

“Is there a previous version of this I can use as a reference so I don’t reinvent the wheel? I found the Q3 deck in Drive — is that the latest, or is there a more recent version you’d recommend?”

You already searched. You’re confirming the best source.

Blocked by access or permissions:

“I’m blocked on finishing ___ because I don’t have access to ___. I requested access in Okta about an hour ago. Is there someone on your side who can approve it, or should I route through IT? If I can get access today, I can still hit Friday.”

Operational, not emotional.

You think the request is wrong:

“I might be missing context, but I want to sanity-check the approach. If we do ___, it’ll take three to four days. If the real goal is ___, I can do Option B in one day. Which outcome matters more?”

You’re offering tradeoffs, not resistance.

You made a mistake and need to recover:

“Quick heads-up: I misunderstood ___ and built it as ___. I see now the correct requirement is ___. I can fix it by ___; new ETA is ___. Anything you want me to do differently before I proceed?”

No drama, just clarity.

When to ask — early beats perfect

A common trap: trying to figure it out alone for too long because you don’t want to bother anyone. That sounds noble. It’s also how you waste ten hours.

A better rule:

• Stuck 20–30 minutes? Ask.
• Work is multi-day? Ask before you start building.
• About to send something external? Ask for a quick review.

Five minutes of discussion prevents days of misplaced work.

Slack vs. meeting vs. email

• Slack: quick decisions, clarifications, A/B choices.
• Meeting or huddle: complex topics where you need back-and-forth.
• Email: formal decisions, longer context, paper trail.

Default to Slack with a clear question, and offer a quick call:

“Happy to hop on a call if that’s easier — five minutes would unblock me.”

The two templates worth memorizing

Yes/no:

“Goal: ___. Context: ___. My plan: ___. Quick check — is this the right approach?”

A/B:

“Two options: (A) ___ or (B) ___. I recommend A because ___. Any objections?”

—

The thing nobody tells you about asking questions: by year three of any job, you’re not asking better questions because you’ve gotten smarter. You’re asking better questions because you’ve been on the receiving end of enough bad ones to know which shape gets answered. The script above is a shortcut to year three.

For the update format that pairs with good questions, steal the Status update template.