Asking For Help

Asking for Help

When to Activate

• "I don't want to bother anyone"
• "Should I ask or figure it out myself?"
• "How do I ask without looking incompetent?"
• "I hate asking for help"
• User is struggling but not reaching out

Why This Is Hard

Asking for help triggers:

The truth: Most people want to help. You're not bothering them — you're giving them a chance to be useful.

When to Ask vs. When to Try Alone

Ask When:

• You've tried for 15-30 min and made no progress
• Someone has done this before (why reinvent?)
• The cost of being wrong is high
• You're stuck on something simple
• Time matters more than learning

Try Alone When:

• The struggle itself teaches something
• You haven't actually tried yet
• You want to learn how to figure things out
• It's not urgent and you have time
• You're using help as avoidance

The rule: If you've genuinely tried and are still stuck, asking is not weakness — it's efficiency.

How to Ask (Framework)

The 5-Part Ask

1. Context — What are you working on? (1 sentence)
2. What you tried — Show you're not being lazy
3. Where you're stuck — Be specific
4. What you need — Advice? Review? Pairing?
5. Easy out — Give them permission to say no

Example:

"Hey, I'm trying to set up the deployment pipeline (context). I followed the docs and got it mostly working, but I'm stuck on the auth step (what I tried + where stuck). Would you have 10 minutes to look at this with me? (what you need) Totally fine if you're swamped. (easy out)"

Scripts for Different Situations

Asking a Peer

"Hey [Name], do you have a few minutes? I'm stuck on [specific thing] and I think you've dealt with this before. Would love your input if you have time."

Asking Your Manager

"I want to make sure I'm handling [X] right. I tried [Y], but I'm not sure about [Z]. Can I get your quick take?"

Asking a Senior/Expert

"I know you're busy, but I'm trying to figure out [X] and you're the person who knows this best. Even a 5-minute pointer would help a lot."

Asking Someone You Don't Know Well

"Hi [Name], I'm [Your name] on [Team]. I'm working on [thing] and heard you have experience with [relevant area]. Would you have time for a quick question?"

Following Up if They Don't Respond

"Hey, just floating this up in case it got buried. No rush if you're swamped!"

The Ask Checklist

Before you ask:

• Did I actually try first?
• Am I being specific about what I need?
• Am I giving them an easy out?
• Am I asking the right person?
• Is this the right time/channel?

After They Help

Immediately

• Thank them sincerely
• Don't over-thank (one solid thanks is enough)

Later

• Close the loop: "That worked, thanks again!"
• Pay it forward when you can

What NOT to Do

• Ask the same question again (take notes)
• Become dependent on them
• Forget to say thanks
• Help them back only when you want something

Reframes for the Guilt

The Deeper Pattern

If you never ask for help:

• You're probably burning out
• You're not learning from others
• You're making things harder than necessary
• You might be protecting an image of competence

Real competence includes knowing when you need input.

The most capable people ask for help regularly. It's not despite their competence — it's part of it.

When They Say No

It happens. Handle it:

1. Don't take it personally — They might genuinely be swamped
2. Thank them anyway — "No worries, thanks for letting me know"
3. Ask who else might know — "Is there someone else you'd suggest?"
4. Try another route — Different person, documentation, community

Response Principles

When helping someone ask for help:

1. Validate the discomfort — It IS hard to ask. That's normal.
2. Give them words — Scripts > pep talks
3. Lower the stakes — Most asks are low-risk
4. Reframe the relationship — Helping is a gift to both sides
5. Check for patterns — If they never ask, that's worth exploring