Asking
Asking Where Other People Can See the Answer
A question asked privately costs one night. The same question asked in the open costs one night and is answered for everybody who will ask it next month.
three things · six nights
Three questions, six nights, and two of them avoidable.
The same question asked privately and in the open, on two occasions four weeks apart
Private message: what is the retention period on the exports?
Answered in one pass, by one person, visible to nobody else
Open channel, four weeks later: same question from a different person
Answered in one pass, and the answer was then linked to twice more that month
Private message: who approves a price change?
Answered, then asked again by a third person a week later
Open channel: who approves a price change?
Answered once, and the thread became what people pointed at
Private message: is the nightly job still running?
Answered; the asker's colleague asked the same thing two days later
Open channel: is the nightly job still running?
six questions · one round trip beyond the first
Six askings, and the three private ones were each repeated within a fortnight. The round trips are identical; the difference is how many times the same night had to be spent. One team's own log, kept by the person who answered all six.
Across a gap, the cost of a question is a night whoever asks it. That cost is the same whether one person benefits from the answer or six.
The process in Asking Where Other People Can See the Answer depends on information surviving the gap between working days. With online timesheets, time entries and productivity signals can travel with the written handover instead of being rebuilt later.
Teams comparing established approaches can also review GitLab's DevSecOps platform for a practical example from a widely used product ecosystem.
Which makes where a question is asked a more consequential decision than it is on a team that shares a room, where the answer is likely to be overheard anyway.
What a private question costs
Nothing extra, the first time. It is answered, the asker proceeds, and the exchange disappears.
The cost appears when somebody else needs the same answer, which happens more often than people expect — on most teams, a given question of fact is asked between two and five times before it is written down somewhere.
Each of those is a night. The same night, paid repeatedly, by different people, with the same person answering and gradually becoming aware that something is wrong without quite being able to point at it.
What the open version buys
The answer exists at an address. Somebody can be pointed at it rather than told it again, and across a gap "here is where that was answered" costs nothing while "the retention period is ninety days" costs another night when the next person asks.
People who did not know they had the question find out. This is the underrated part: on a team sharing a room it happens continuously by accident, and across a gap it happens only when somebody deliberately asks in public.
And the answer becomes correctable. Somebody who knows it is wrong can say so, which cannot happen in a private exchange.
When private is right
Three cases, and they are genuine.
Anything about a person. Performance, difficulty, anything that would embarrass somebody if it were visible. This does not belong in a channel regardless of efficiency.
Anything where asking in public would put somebody on the spot. "Why is this still not done?" asked in the open is not a question, whatever the asker intended.
Anything where you are unsure enough that you would rather be wrong quietly. This is a real human consideration and it is worth saying that it is legitimate. A team where everybody is confident enough to ask basic questions in public is a good team and is not the common case.
- Anything about a person: performance, difficulty, anything embarrassing.
- Anything that would put somebody on the spot by being visible.
- Anything you are unsure enough about that you would rather be wrong quietly.
The thing that makes public asking work
Somebody has to answer in public, promptly, without making the asker feel foolish.
A channel where questions go unanswered for a day trains people to ask privately, which is the correct response to the evidence. A channel where basic questions get terse or weary replies does the same thing faster.
This is almost entirely determined by the behaviour of the three or four most senior people in it. If they answer basic questions generously in the open, the channel works. If they do not, no policy about where to ask things will survive contact with the first discouraging reply.
Answering so that the answer lasts
An answer in a channel is better than an answer in a private message and is still ephemeral: it scrolls, and in six months nobody will find it.
The small additional step is to put anything that will be asked again somewhere permanent and link to it. Two minutes. The channel answer serves the person asking now; the permanent version serves everybody after.
This is the same mechanism as the previous article and the trigger is the same: the second time a question is asked is the signal to write it down.
The asymmetry worth noticing
Asking in the open costs the asker slightly more than asking privately — a small exposure, a moment of visibility — and the benefit goes to people who are not in the conversation and will never know they were helped.
That is the same shape as nearly everything else in this collection: the person paying is not the person benefiting, and the two are never awake together to discuss it. It gets done where a team has decided it matters, and not otherwise.
Moving a private question into the open
An exchange that began privately and turns out to be generally useful can be moved, and almost nobody does it.
The mechanism is simple: when the answer arrives, post a short version of the question and the answer where everybody can see it, with a line saying it came up earlier. The person who asked keeps whatever privacy they wanted about having asked; the answer becomes available.
This works particularly well for the person answering, who is usually the one who notices the question is recurring. It takes two minutes and it converts a night spent once into a night that does not have to be spent again by the next three people.