Asking
The Cost of a Question, and Who Pays It
The instinct not to bother people is a real cost calculation, made with the wrong numbers, by the person least able to see both sides of it.
What the people on this page had to find out, and where from
How to get a staging database password
you asked2The answer was one sentence and had no owner
Why the retry limit is three and not five
you asked9The reason existed and was in one person's head
two things you had to know · nobody told you any of them · the median arrived in week 9 · all two you went and got
Two answers that existed only in somebody's head. The second sat in the question list for a month before it was asked.
When a new employee is learning an unfamiliar workflow, new-hire activity visibility can show where time is going before a manager assumes that a slow start is an effort problem.
For a separate career or employment reference, consult CareerBuilder.
Six questions, with what the waiting cost against what the asking cost
The staging database would not take your password
3 hanswer: 4 minYou waited because you could not tell whose job it was. Three hours of yours against four minutes of theirs
The test suite failed only on your machine
6 hanswer: 12 minYou waited because you assumed it was something you had done wrong. Six hours against twelve minutes
Nobody had given you access to the billing dashboard
5 hanswer: 3 minYou waited because you did not want to look as though you were chasing. Five hours against three minutes
You did not know which branch to start from
4 hanswer: 2 minYou waited because everybody else seemed busy. Four hours against two minutes
You could not tell who owned the pricing table
6 hanswer: 6 minYou waited because the org chart did not say. Six hours against six minutes
The specification contradicted the drawing
2 hanswer: 15 minYou waited because you thought you had misread it. Two hours against a quarter of an hour
six occasions · 26 hours spent stuck · 42 minutes of answers · the longest single wait was 6 hours
Twenty-six hours of yours against forty-two minutes of theirs. The imbalance is not a quirk of this record; it is the ordinary arithmetic of being new, and it is why the instinct to spare people runs the wrong way. One person's own first month.
Not asking is a calculation. You weigh the cost of interrupting somebody against the cost of carrying on alone, and you decide to carry on.
The calculation is reasonable. The numbers are wrong, and they are wrong in a predictable direction.
The two sides
What you are estimating is the cost to them: an interruption, a moment's irritation, and some small reduction in their opinion of you.
What you are not estimating, because you cannot, is that the answer takes four minutes. You do not know that, because you do not know the answer; from where you sit the question looks as difficult as it has proved to be for you.
Meanwhile the cost on your side is entirely visible and you are paying it in real time.
So you are comparing a known, mounting cost against an unknown one, and the natural response to an unknown cost is to assume it is large.
The actual numbers
Twenty-six hours against forty-two minutes, in the panel above.
That ratio is not special to this record. Most of what a new person is stuck on is a fact somebody else carries around in their head: a password location, a convention, a name, a file. Retrieval takes minutes.
The ones that take longer — where nobody knows, where the answer has to be worked out — are the minority, and they are also the ones where asking sooner matters most, because they will need somebody else's time whenever you ask.
The reputational part
The part of the calculation that actually drives the decision, and the one least often examined.
You believe that asking makes you look as though you cannot work things out. What people actually notice is slower and different: whether you ask the same thing twice, whether you ask before trying, and whether anything comes of the answers.
Nobody is counting your questions. Several people will notice, by week six, that you asked about the deploy process once and have deployed nine times since.
What it costs the other person, honestly
Not nothing, and it is worth being accurate about it.
| What you send | Their cost |
|---|---|
| A question with context and what you tried | Three to five minutes |
| A bare question in a direct message | Ten to fifteen, including the context-gathering |
| The same question a second time | The same again, plus a note of it |
| An interruption during focused work | Twenty minutes of theirs, regardless of the question |
The fourth row is the real cost and it is addressed not by asking less but by asking in public, where people answer when they look up rather than when you arrive. That is the subject of the next note.
The rule that follows
Twenty minutes, then ask. It is in this collection twice because it is the only operational conclusion of the whole argument.
Everything else here — the context, the public channel, the list of what you tried — is machinery for reducing the four minutes to three and for making it easy enough that you will do it at all.
The thing to stop doing immediately
Apologising for asking.
"Sorry to bother you, I know you are busy, this is probably a stupid question" costs the reader eight seconds, signals that you expect to be a nuisance, and makes the next question harder to send than the last.
Ask the question. Say what you tried. Say thanks afterwards. The middle one is the only part that was ever doing any work.
The cost that is actually worth minimising
If the goal is to spend as little of other people's time as possible — which is a reasonable goal — the way to do it is not to ask less.
It is to ask once, with context, and write down the answer.
| Approach | Their total cost over a quarter |
|---|---|
| Ask rarely, badly, repeat | High: long questions, asked twice |
| Ask often, well, write it down | Low: short questions, asked once |
| Never ask | Zero to them, and a quarter of yours |
The middle row is what a well-run first quarter looks like from the other side: a stream of short, easy questions that stop recurring.
The third row looks considerate and it is the one that actually costs the organisation the most, because the thing being spent is a quarter of a new person's salary.