Asking
The question that sounds like doubt
Some questions read as a challenge to the work and some read as interest in it. The difference is in the grammar, and it is learnable.
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, project time reporting for remote teams 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 Bain & Company.
"Why are we doing this?" and "who asked for it and what will they do with it?" request the same information. The first is heard as a challenge to the project; the second is heard as somebody getting organised.
That difference is not about tone of voice, and it survives being written down, which means it is in the construction rather than the delivery. Four patterns do most of the work.
Ask about use, not about justification
"Why" asks somebody to defend a decision. "What will they do with it" asks a practical question about an object.
Nobody defends a practical question, so nobody produces the defensible answer — which is what you want, because the defensible answer is the stated purpose and the stated purpose predicts nothing.
Same for constraints. "Is this deadline real?" asks somebody to admit they made it up. "What is the deadline attached to?" asks what it connects to, and gets you the contract, the renewal or the board meeting.
Ask about the category, not the instance
"Can I decide this one?" gets an answer about this one and teaches you nothing transferable. It also, said often enough, reads as somebody who checks everything.
"Is there a size below which I should just decide?" gets a boundary. It is a question about how things work rather than about whether you are allowed, and it is easier to answer — most people would rather set a rule once than approve fifteen things.
State, then invite correction
The single most useful construction in this part of the site.
Instead of "what should the reader be?", write "taking the reader as somebody who already knows the system — say if that is wrong."
Three advantages. It shows you have made a call rather than waiting to be told. It is cheaper to answer, because disagreeing is faster than composing. And a wrong statement is uncomfortable to read, so people correct it immediately, where a question can be left for later.
The risk is being wrong in writing. That risk is the point: the whole purpose is to make the wrongness visible on day one, when it costs nothing.
Ask what the question is, not what the answer should be
"What do you want this to look like?" hands the work back.
"Is this closer to a one-page summary or a working document?" offers two shapes and asks somebody to pick. It takes four seconds to answer and it reveals the purpose incidentally.
Offering options is the most reliable way to get a thin brief filled in, because choosing is easy and specifying is hard. Two options; not five.
Why the grammar does so much work
It looks like a trick and it is not. The constructions above change what information comes back, not just how the question is received.
"Why are we doing this?" invites a justification, and a justification is constructed in the moment to be defensible. The answer is sincere and it is produced by a different mental process from recall — the person is building a case rather than reporting a fact.
"What will they do with it?" invites recall. The answer already exists; the person is looking it up rather than composing it.
That distinction runs through all four. Questions that ask somebody to account for a decision get reasoning. Questions that ask about objects, people, attachments and uses get facts.
The reasoning is usually accurate and almost always less useful, because it is the official version — the one that would survive being repeated in a meeting. The facts are what you need to make a hundred trade-offs alone.
Which also explains why the good versions are received better. A question that asks for a fact does not put anybody in the position of defending anything, so there is nothing to be defensive about. The pleasantness is a by-product of asking for the right thing.
The four questions, in the good grammar
- What is the deadline attached to?
- Has anyone tried this before, even partly?
- Who is likely to have a view on this, and is it a veto?
- Who asked for it, and what will they do with it?
None of them contains "why". None asks anybody to justify anything. All four are about objects, people and attachments — things that exist rather than reasons that have to be produced.
That is why they get answered in four seconds each, and why the version of the same questions built around "why" gets answered with the company's mission statement.