I will genuinely spend an hour stuck on something before I message someone who could answer it in two minutes.
Not because I'm too proud to ask. Because asking comes loaded with a whole set of quiet fears that are hard to name out loud.
Maybe this is something I should already know. Maybe the person is in the middle of something. Maybe the question is too small, too obvious, too much. So I keep trying. Keep googling. Keep going in circles, all to avoid the 30-second discomfort of sending a message.
If you've done this, you already know it's not rational. You're trading an hour of your time to avoid a moment of vulnerability. The math doesn't work. But the feeling keeps winning.
Here's what the research actually says about why.
Your brain is running the wrong model
Vanessa Bohns, a researcher at Cornell, has spent years studying the psychology of asking. Her core finding: we dramatically underestimate how willing other people are to help us, by roughly 50%.
That means the mental model your brain is running, "they'll be annoyed," "they're too busy," "this isn't worth their time" — is off by half. The actual yes rate is roughly double what you predicted. The actual warmth people feel when asked is much higher than you assumed.
We're not bad at reading people in general. We're specifically bad at modelling how we come across when we ask for something. We imagine the request landing as an imposition. They experience it as someone trusting them enough to come to them specifically.
That's a meaningful gap.
The helper's high
There's another piece to this that reframes the whole thing.
Helping someone triggers a dopamine response in the person helping. This is well-documented, it's sometimes called the helper's high, and it's a real neurochemical reward for being useful to another person. People feel good when they can genuinely help. It gives them a sense of competence, connection, and purpose.
So when you decide not to ask because you don't want to bother someone, you're not being considerate. You're denying them that feeling. The person you thought you were protecting from the inconvenience of your question? They probably would have enjoyed answering it.
I know that sounds counterintuitive. It kind of wrecked me when I first sat with it.
The "everyone is busy" story
One specific version of this that I notice in myself: I convince myself that senior people, experienced people, are too busy for my question.
But busyness is partly a performance. Everyone is busy. And everyone also checks Teams/Slack while waiting for a build to run, answers a quick question over coffee, responds to a LinkedIn message at 11pm because they happened to see it.
The person you think has no bandwidth for you is probably more available than you think. And more willing than you think. And more flattered than you think.
What actually happens when you don't ask
You lose time. You build the wrong thing. You stay stuck longer than you needed to. You miss a conversation that might have led somewhere interesting. You leave the other person unaware that they could have helped, and that they would have wanted to.
The cost of asking is 30 seconds and a small amount of discomfort.
The cost of not asking compounds quietly in the background.
What helps
Name what's actually stopping you. It's usually one of three things: fear of looking like you don't know something, fear of rejection, or a story about the other person's availability that you made up entirely.
None of those are facts. They're predictions. And the research says your predictions are running about 50% low on how likely people are to say yes.
Send the message. Keep it short. Be specific about what you need.
Your brain is protecting you from a rejection that probably wasn't coming anyway.
This article was originally published by DEV Community and written by Shannon Mettry.
Read original article on DEV Community