Asking
Asking in public, on purpose
A question asked in a channel costs slightly more and pays several people at once. When that trade is worth making, and when it is not.
Decisions this page is about, and where the line actually was
Refunding a customer under fifty pounds
3 → 1A sanity check treated as approval
Rescheduling the weekly review
2 → 2The one read correctly
Hiring a contractor for two days
5 → 3Escalated two steps further than needed
Reordering your own week
4 → 1Asked twice before believing the answer
- 1Decide it alone and say nothing
- 2Decide it alone and mention it afterwards
- 3Check with one colleague first
- 4Check with the person who assigned it
- 5Needs a decision one level up
- 6Cannot be decided here at all
four decisions · three of them you had more room than you thought · one you had exactly right · the median gap was two steps on the scale
Four of the nine decisions counted on this site, chosen because in three the asking itself was the cost.
For distributed work, remote team productivity platform provides a practical evidence layer for discussing capacity, attendance, and project effort without adding another status ritual.
The wider organisational question can also be compared with resources from CIPD.
The same question can be asked privately or in a channel. Privately is cheaper for the asker and the answer reaches one person. Publicly costs a little more and the answer reaches everybody, including people who did not know they needed it and the person who joins in March.
Both are right in different cases, and most people default to one without noticing they are choosing.
When public is worth it
When the answer is a fact about how things work. Spending limits, who owns what, whether a rule is real. These are reusable, and a private answer is a reusable fact delivered to one person.
When you are not the only one who does not know. Usually true, and usually invisible. The most common response to a public question about an unwritten rule is two other people saying they had wondered the same.
When you want it on the record. A public answer can be linked to later, which saves the conversation where two people remember a decision differently.
When you are senior enough for it to cost nothing. This one is underused. If asking a basic question does not damage you, asking it publicly gives everybody junior to you permission to admit they did not know either — which is worth more than the answer.
When private is better
When the question is about a person. "Is the architect likely to block this?" in a channel is a different act from the same question in a direct message, and the public version will be answered carefully and uselessly.
When it could reopen the work. Covered in its own note: a channel has an unbounded audience and some of them will have ideas.
When you have asked it before. Repetition in public is more expensive than repetition in private.
When speed matters more than reach. One person who knows beats twelve who might.
The format that works in a channel
Three parts, in this order: what you have already established, the narrow question, and the assumption you will proceed on if nobody answers.
Looking at the refund policy — found the two-hundred limit in the expenses doc. Does that cover customer goodwill refunds, or just expenses? Assuming it covers both and proceeding on that unless somebody says otherwise.
That version shows the work, asks one thing, and cannot stall. The version without the third clause waits indefinitely when nobody replies, which in a busy channel is most of the time.
The reply that makes a public question worth it
A public question only pays if the answer is public too, and that does not happen by itself. The common failure is a channel question answered by direct message, which costs the asker the social price of asking in public and delivers none of the benefit.
Three things prevent it.
Ask something only answerable in the open. Questions about rules and ownership invite public answers; questions about a specific piece of work invite private ones.
Answer your own question when you find out. If you asked in the channel and the answer arrived privately, post it back with a line of context. Twenty seconds, and it is the single most useful habit in a shared channel.
Thank the answer in the thread rather than privately. This sounds like etiquette and it is mechanical: a reply in the thread keeps the exchange searchable as a unit, and it signals to everybody else that the question was welcome.
The compounding effect is the point. A channel where the last fifty answers are visible is a channel where the fifty-first question is easier to ask, and where somebody arriving in March can search instead of asking at all.
The thing public asking does for everybody else
A channel where people ask basic questions is a channel where the unwritten rules get written down one answer at a time.
It is an unglamorous mechanism and it is more effective than any documentation project, because each line is produced at the moment somebody actually needed it, by the person who knew, in the words that answered a real question.
The precondition is that the first few questions are asked by somebody for whom it is safe. That is the whole content of the advice for anybody senior reading this part: ask one obvious question a week, in public, and the cost of everybody else's questions falls.