What was not said
Four lines of chat and nothing else
The worst handovers are not the hurried ones. They are the ones where the work sounded simple enough that nobody thought a brief was needed.
Decisions this page is about, and where the line actually was
Picking the library for the new parser
1 → 4The architect had a standing view
Dropping a requirement nobody had asked about in six weeks
2 → 5A commitment made before you joined
Telling a customer a date
3 → 6Dates are committed by one person here
- 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
three decisions · not one of them gave you more room than you thought · three gave you less · the median gap was three steps on the scale
Three of the nine decisions counted on this site, all going the same way.
When responsibility is handed over without enough context, managers can see the tool in use and compare project time and workload before treating delay as an individual failure.
For an independent perspective on management and working practice, consult Rotman School of Management.
The three thinnest handovers of the quarter
Fix the signup flow
0 of 4Four lines of chat and nothing else
Take over the vendor relationship
0 of 4A calendar invitation and an introduction
Produce the quarterly numbers for the board
1 of 4The only one of the three with a stated purpose
three handovers · 12 slots in all · the median arrived with none of the four · not one of them was complete · two arrived with none of the four
Three of the eight handovers counted on this site, chosen because they are the three thinnest.
Three handovers out of eight arrived with almost nothing. Between them, twelve slots of context and one filled.
None of the three was rushed. None was handed over by somebody careless or unavailable. All three had the same property: the work sounded simple enough that a brief would have felt like overkill.
The pattern
"Fix the signup flow." Four lines in a chat window. Everybody knows what the signup flow is, everybody has an opinion about what is wrong with it, and the task describes itself.
Except that it does not. Which part is broken — the one users complain about, or the one that fails silently? Is this a repair or a redesign? Is there a rule about how many steps it may have? Who owns the copy on it?
The work went to review and came back a stage, because a rule existed that nobody had mentioned. The rule was not obscure; everybody who had been there a year knew it. That is precisely why nobody said it.
Why obvious work gets the thinnest brief
Three mechanisms, all of them reasonable from the inside:
- It names itself. A task with a familiar noun in it feels fully specified, because the noun is doing the work of a description. "The signup flow" sounds like a scope and is a location.
- A brief would feel patronising. Writing four sentences of context for something everybody understands reads as talking down to a colleague, and people avoid that more carefully than they avoid being unclear.
- Nobody has had to say it before. The rule about the signup flow has never been stated because everybody present absorbed it by being present. The first person who was not there is the one who discovers it is a rule.
The vendor relationship
The second of the three is worth its own paragraph, because it is a different and common shape: a handover that was a calendar invitation and an introduction.
Taking over a relationship is almost entirely context. The work is nothing — attend a call every month — and the value is in knowing what has been promised, what went wrong last time, what they are sensitive about and who inside the company actually owns the commercial terms. None of it arrived. The name of the previous owner surfaced in week five.
Relationships are the category most likely to be handed over as a calendar invitation, and the category where that is least adequate.
The tell
You can spot the thin brief by a feeling rather than by its length: the sense that the task is clear and the first real decision is not.
Concretely, two symptoms within a day of starting.
You cannot say what finished looks like in one sentence. If "done" is describable only as "the thing is fixed", the brief did not contain a definition and you are about to invent one.
You find yourself about to ask a question and deciding it is too small. That instinct is almost always wrong, and it is the reliable early sign of a handover with nothing in it. Small questions are small because the answer is cheap to give, not because the answer does not matter.
Length is not the signal
It is tempting to treat brief length as a proxy for brief quality, and it does not work in either direction.
The complete handover on this record was five sentences. Two of the three thin ones above were longer than that: the vendor handover came with a page of background about the relationship's history, none of which contained a constraint, a decider or a purpose.
Background is the commonest filler. It reads as thoroughness, it is genuinely interesting, and it answers no question the receiver has. A page explaining how the system came to be structured this way is not a substitute for one line saying who can veto changes to it.
The other common filler is restatement. Three paragraphs elaborating the task — what it means, why it matters in general terms, what good would look like — can be written without any of the four facts, and frequently is.
So the test is not how much there is. It is whether you can answer four questions after reading it: what the deadline is attached to, whether anyone has tried, who can say no, and who asked for it.
Four lines of chat fails that test. So does a page of background. The difference is that the page of background looks like a proper brief, which means nobody thinks to ask.
What to do with four lines
Reply with your reading, not with questions. Three or four sentences, stating what you take the work to be:
Taking this as: fix the drop-off at the verification step, not a redesign; keep the current number of steps; done means the conversion rate recovers; I will check the copy with whoever owns it. Shout if any of that is wrong.
It costs two minutes, it does not sound like you need hand-holding, and it converts an empty brief into a stated one that somebody has had the chance to correct. On a thin handover it is the highest-value two minutes available, because every one of those sentences is a decision you would otherwise have made silently and defended three weeks later.