Asking
When Nobody Answers
Silence after a question almost never means what a new person thinks it means, and there are four ordinary explanations before any of the worrying ones.
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.
A fair onboarding review can use employee productivity reporting to separate time spent learning from time spent blocked, keeping the discussion grounded in shared evidence.
For additional context beyond this collection, see the material published by FlexJobs.
Four questions that went unanswered, and what actually worked
A question in the team channel, Thursday at 16:00
20 hanswer: 3 minYou waited because you assumed silence meant it was a foolish question. Answered on Friday morning by somebody who had been in meetings
The same question asked again on Monday
1 hanswer: 3 minYou waited because you had learned to repeat rather than wait. Answered in an hour
A direct message to the one person you thought could answer
9 hanswer: 2 minYou waited because you did not want to ask twice. They were on leave and their status did not say so
A question asked in the wrong channel
14 hanswer: 4 minYou waited because you did not know there was a better channel. Moved by somebody kind, and answered immediately there
four occasions · 44 hours spent stuck · 12 minutes of answers · the longest single wait was 20 hours
Forty-four hours across four unanswered questions, and in none of the four was anybody ignoring anything. Three had ordinary mechanical explanations and the fourth was a wrong room. One person's own first quarter.
You ask something in the channel. Nothing happens. An hour goes by, and then an afternoon.
The conclusion that arrives, if you are new, is that the question was foolish. It almost never is, and there are four ordinary explanations to work through first.
The four explanations
Everybody was busy when it arrived. Channel questions are answered by whoever looks up at the right moment. If you asked at four in the afternoon, the people who would have answered were finishing something.
The people who know are elsewhere. On leave, in a workshop, in another time zone. Status indicators are frequently wrong and almost nobody updates them for a day off.
It was the wrong room. The question went to your team's channel and belongs in the channel for the system it concerns. People in your team do not know; people who do know are not reading.
It scrolled past. In an active channel a question is visible for about twenty minutes.
None of these is about the question or about you.
What to do, in order
- Wait until the following morning. Most unanswered questions are answered within a day.
- Repeat it once, in the same channel, briefly. Not a complaint — a bump.
- Ask whether there is a better place for it.
- Go to one named person, with a link to the channel question.
Each step is cheap and the order matters: going straight to step four spends a relationship on something that step two would have fixed.
The repeat
The form that works is short and carries no reproach.
Bumping this in case it scrolled past — still trying to work out which deploy guide is current.
Fifteen words. The phrase "in case it scrolled past" supplies the explanation for everybody, including anybody who did see it and intended to answer.
Repeating once is normal. Repeating three times in a day is not, and it converts a question into pressure.
Asking for the right room
The most under-used of the four steps, and it frequently solves the problem outright.
Is there a better channel for questions about the billing system? I asked in ours and I suspect the people who know are not in it.
That is a question almost anybody can answer, it costs them four seconds, and in the panel above it was what finally worked: the question was moved by somebody kind and answered immediately in the new place.
Going to one person
The last step, and it is worth doing well.
Pick a name from the history of the thing rather than from the chart. Link to the channel question so they can see the context without you retyping it. Make it easy to decline.
I asked this in the team channel on Thursday and I think it may just be the wrong room. Your name is on the last few changes to this — would you know, or know who would?
"Or know who would" is the clause that makes it answerable by somebody who does not know, which is often how it gets resolved.
What silence does not mean
It does not mean the question was stupid. It does not mean you are being excluded. And it does not mean you should stop asking.
The one thing worth watching for is a pattern: if several questions in a row go unanswered in the same place, the place is wrong, not the questions. That is a thing to raise with your manager — not as a complaint about anybody, but as a practical problem with a practical answer.
I am not getting much response in the team channel. Is there a better place for day-to-day questions, or somebody you would point me at?
The channel that is not read
Worth checking early, because it accounts for a surprising share of unanswered questions.
Many organisations have channels that exist and are not read: a general help channel from a reorganisation two years ago, a team channel that moved and left a shell, a support channel whose audience is elsewhere.
There is no way to tell from inside one. The test is to look at the last twenty messages and see whether anybody answered any of them. Four unanswered questions in a row from four different people is a dead channel, and nothing you post there will be read either.
Ask once, somewhere else, where the live one is. The answer takes four seconds and it is the kind of thing nobody thinks to tell a new person, because everybody else simply knows.