What was not said
The curse of knowing where the line is
Once you know something, you cannot reconstruct not knowing it. This is why experienced people are often the worst at handing work over, and what to do about it.
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.
Where ownership crosses several roles, teams can open the current platform page to make time and recurring bottlenecks visible enough for a useful operational conversation.
For additional reading outside this collection, see material published by Hult International Business School.
The best person to explain how a system works is somebody who learned it recently. The worst is the person who built it. This is not about communication skill and it is not about effort; it is a property of knowing things.
Once a fact is in your head it stops being a fact and becomes part of the furniture. You can still state it if prompted, but you cannot reliably notice that somebody else lacks it, because the gap it would leave in their understanding is not visible from where you stand.
Why experience makes handovers worse
Three effects, all pulling the same way.
The longer somebody has been in an area, the more of their working knowledge was absorbed rather than learned. Absorbed knowledge has no retrieval handle: there is no moment of acquiring it to remember.
The more fluent they are, the more compressed their description becomes. "Just do the usual migration dance" is a complete and accurate instruction to a peer and an empty sentence to anybody else, and it does not feel compressed from the inside.
And the more senior they are, the less feedback they get about it. People who receive a thin brief from somebody senior do not usually say so. They go away and work it out, and the cost is invisible.
The three-week test
A practical way to see the curse operating.
Think of the last thing you explained to somebody who joined recently. Now count how many questions they asked in the first week that you had not anticipated. If the number is more than two or three, the explanation was shaped by your knowledge rather than their ignorance — which is normal, and worth knowing.
Then do the useful half: write those questions down. They are the slots you do not see, and they will be the same slots next time, because the curse is specific to the knower, not the topic.
What actually defeats it
Not effort, and not empathy. Two things work, and both are mechanical.
A fixed list. Four slots, filled in every time, whether or not they feel necessary. The list substitutes for the noticing you cannot do. This is the whole reason the four things on this site are a list rather than advice.
A recent arrival. The best reviewer of any brief is whoever joined most recently. Ask them to read it and mark what they could not act on. It takes them five minutes and they are the only person in the room who can still see the gaps.
Organisations that do the second well tend to do it by accident — a new person writes up what they wished they had been told, and somebody keeps it. The deliberate version is to ask for that document in somebody's first month, while they can still produce it. By month four they have been cursed too.
The inverse problem
There is a failure in the other direction, and it is worth naming so this is not read as a licence to over-explain.
Explaining things the receiver already knows is not free. It takes their time, it reads as a judgement about their competence, and if enough of the brief is obvious they will skim the part that was not.
The four-slot list handles this better than general thoroughness does, because each slot can be one line and a known line costs four seconds to skip. "The deadline is the thirtieth, contractual" is instantly skippable by somebody who knew, and essential to somebody who did not. Prose cannot be skimmed that way; a list can.
Where the curse bites hardest
Not on technical detail, which people are used to explaining, but on three things that do not feel like knowledge at all.
Norms. How much detail a status update should have. Whether it is acceptable to message somebody directly. Whether a disagreement in a review gets resolved in the review or offline. None of these is written anywhere, all are enforced, and nobody can see them as rules.
Vocabulary. The dozen words that mean something particular here. "Done", "spec", "ready", the name of the thing that is not its name. The curse makes these invisible because the speaker has only one meaning for each.
Who to believe. Every organisation has sources that are formally authoritative and sources that are actually right, and the mapping between them is learned by watching. A new person following the documentation faithfully will be wrong in ways nobody can predict.
These are harder than constraints because there is no slot for them. The four-slot list catches facts about the work; it does not catch facts about how the place operates.
The only instrument that finds them is a recent arrival writing down what surprised them, in their first six weeks, before it stops being surprising. That document is worth more than any onboarding material and has a shelf life of about two months from the day they joined.
The sentence worth saying
If you hand work to somebody and you can only manage one self-correcting sentence, make it this one:
I have been in this for two years, so I will have left things out that I cannot see. Ask me anything, including things that seem too small.
It does not fix the curse. What it does is move the cost of the remaining gaps from the receiver's pride to the sender's, which is where it belongs, and it makes the small questions askable — which is where most of the missing context actually comes out.