Why Is Asking for Help at Work So Hard

The day I wasted 3 hours struggling alone

Tuesday afternoon. A weird error popped up in the deployment pipeline. Googled the error message. Found a similar question on Stack Overflow, but the answer was from 2019 and didn't apply. Asked ChatGPT. Got a useless answer.

Three hours of flailing later, I finally asked the senior dev. Solved in 7 minutes. A single environment variable was missing. (Specifically, DATABASE_POOL_SIZE wasn't in .env.production.)

3 hours vs 7 minutes. Why didn't I just ask sooner.

The real reason I don't want to ask

"I'll look stupid" is the honest answer. I'm five years in and I don't want to hear "you don't know this?" But the thing is, nobody has ever actually said that to me. It's a scenario I've manufactured in my own head.

The other reason: "I'd be stealing their time." When you can see a senior is clearly busy, interrupting their flow with your question feels rude. But logically, I know that spending 3 hours flailing alone and pushing back the timeline is a bigger burden on the entire team. I know this. In my head.

Asking well is a skill

One day our team lead said something: "Before you ask, do at minimum this: what you tried, where you got stuck, what happened." Sounds simple but actually doing it organizes the question itself.

"This doesn't work" and "I tried A but got error B, also tried C and got the same error" are completely different experiences for the person receiving the question. With the latter, sometimes the answer comes in 30 seconds: "oh, try D."

And honestly, about half the time, organizing the question like this leads me to the answer on my own. Rubber duck debugging, they call it.

I observed someone who's good at asking

There's a person on the team, only two years of experience, who asks questions really well. I analyzed their pattern. (Secretly.)

First, good timing. Not when someone is deep in focus, but when they're heading to get coffee, or with a Slack message like "do you have a minute?" first.

Second, specific questions. Not "how do I do this" but "for this part, would approach A or B be better? I'm leaning toward A but I'm unsure because of this reason."

Third, always shares the outcome. "Did what you suggested and it worked, thanks" completes the cycle. Seems trivial, but for the helper, it's feedback confirming "I actually helped."

My failure pattern

Me, on the other hand: struggle alone, ask in a panic when truly stuck, get the answer, say "thanks" and dive straight back to work. Almost never shared the outcome. And sometimes I asked the same type of question twice. (That one's genuinely embarrassing.)

Since the start of this year, I've been logging questions and answers in Notion. A personal wiki of sorts. The duplicate question problem has dropped.

It's also a cultural thing

I have to acknowledge that saying "I don't know" isn't easy in Korean workplace culture. There's an unspoken expectation: "at five years, you should know this by now." But technology keeps changing, and nobody can know everything. What you learned three years ago often doesn't apply today.

I recently realized that a team where the lead says "I don't know" first is a good team. Our lead does this well. When they say "I haven't seen this either, let's look at it together," it makes it so much easier for everyone else to admit they don't know something.

I want to be that kind of person for the juniors on my team. Not there yet though. Need to be more honest starting tomorrow.