Asking
Putting a Question So One Answer Finishes It
A question that can be answered in one pass names the thing, states what is already known, and says what the asker will do with the answer.
three things · six nights
Three questions, six nights, and two of them avoidable.
The same six questions, asked first as they occurred and then rewritten before sending
Is the report wrong?
No version, no figure, no statement of what wrong would mean
The March revenue figure on the finance report reads 412,000 and the ledger says 418,000. Which is authoritative?
Can I change the schema?
Asked of somebody who had to find out who owned the table
I want to add a nullable column to the orders table. You own it. Any objection, or shall I go ahead Thursday?
What should I do about the client?
Two clarifications before anybody established which client and what had happened
The client asked for the deadline to move to the 14th. I can do it by dropping the export work. Shall I, or shall I tell them no?
six questions · six round trips beyond the first
Six questions, three pairs, and every rewritten version was answered in one pass. The rewrites took about forty seconds each and saved seven nights between them. One team's own log, kept by the person who did the rewriting.
A question that needs two crossings was usually answerable in one. The missing part is small, it is known to the asker, and leaving it out took no effort at all.
When the working day is split across locations, managers need a consistent baseline rather than a stream of check-ins. time tracking reports can supply that baseline for the scenario explored in Putting a Question So One Answer Finishes It.
A useful external reference is Basecamp's project workspace, which provides another official view of how teams organise shared work.
The fix is a rewrite that takes under a minute, and the hard part is doing it rather than knowing how.
The three parts
A question that finishes in one pass has three components, and omitting any one of them produces a predictable kind of second crossing.
The thing, named specifically. Which report, which table, which client, which call, which version. Names are cheap and the lack of one makes an answer impossible rather than merely harder.
What you already know. The figures you have seen, what you have already checked, what you have already ruled out. Without this the recipient's first move is to tell you something you know, and their second move is to ask what you have tried.
What you will do with the answer. This is the part most often left out and it does the most work, because it tells the recipient what kind of answer is wanted. "Shall I go ahead on Thursday?" tells them a yes is sufficient. "What do you think?" invites a paragraph, and the paragraph will not contain a decision.
- The thing, named. Which report, which table, which client, which call.
- What you already know. What you have checked and ruled out.
- What you will do with the answer. This tells the reader what kind of answer is wanted.
Stating the default
The strongest single technique in this article: say what you will do if nobody replies.
"I am going to add the column on Thursday unless somebody objects" converts a question into a notification with an opt-out. The night passes either way, and in the common case where nobody objects, the work proceeds without a second crossing at all.
It also makes the stakes visible. If the default is wrong, the recipient now knows they have to say so, which is a much stronger prompt than an open question that could be answered any time.
The limit is that it only works where proceeding is reversible and where you genuinely have the standing to proceed. Used where either is false it is not a question technique; it is presenting somebody with a fait accompli, and it is noticed.
Offering the options
Where the answer is a choice rather than a fact, naming the options removes a crossing almost every time.
"Shall I do A or B?" with one line on what each costs is answerable in a word. "What should we do?" is answerable only by somebody willing to reconstruct the situation, and across a gap they will usually ask for more context first.
Two options is the useful number. Three is acceptable. More than that is a sign that the question is not ready and that what is needed is a narrowing conversation rather than an answer.
The recipient's side
The same principle runs the other way and is worth naming, because half the second crossings in a week belong to answers rather than questions.
An answer that finishes in one pass addresses the question as asked, says what it is conditional on, and — if the answer is no — says what would make it yes.
"No" costs a night and produces another question. "No, because the export job reads that column; if you make it nullable with a default it is fine" costs the same night and ends the exchange.
When one pass is not possible
Some questions genuinely require a conversation, and it is worth recognising them rather than trying harder to phrase them.
The reliable sign is that you cannot write down what a sufficient answer would look like. If you cannot describe the shape of the reply that would finish it, no amount of rewriting will produce one, and sending it anyway buys two or three nights of correspondence that arrives where it started.
Those belong somewhere else: a scheduled hour, a decision delegated to whoever is awake, or a narrowing of the question until a piece of it can be answered.
The habit
Write the question. Then read it as the recipient, waking up, with no memory of your day.
Almost everybody who does this finds the missing noun. The technique is not difficult and it is not consistently applied by anybody, including people who know it, which suggests the useful intervention is a reminder in the place where questions get written rather than more explanation.
Rewriting as a habit rather than an exception
Everything above describes a rewrite, and a rewrite only happens if there is a moment in which it can.
The practical version is to write questions into a draft during the day and send them at the end, rather than sending each one as it occurs. That produces a natural pause in which the question is read again, which is when the missing noun gets noticed.
It also batches them, which is worth a night on its own. The two benefits arrive from the same habit, which is unusual and makes this the one procedural change in this section worth adopting deliberately.