What was not said
Written briefs and the ones nobody writes
Remote work is supposed to force things into writing. In practice it forces the task into writing and leaves the context in the places it always was.
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 autonomy has no visible boundary, a team can review the service overview and use project patterns to identify where clearer authority would remove rework.
The wider organisational question can also be compared with resources from ProjectManagement.com.
The standard claim about distributed work is that it makes everything explicit. If you cannot lean over and ask, things have to be written down, so remote teams end up better documented than co-located ones.
The claim is half right, and the half it gets wrong is the half this site is about. Remote work reliably forces the task into writing. It does nothing at all to the context, which stays exactly where it was — in the heads of people who were present when it was formed.
What gets written and what does not
Written, because the work cannot start otherwise:
- What to do
- Roughly when
- Who is doing it
Not written, because none of it is required to start:
- What must not change, and why
- What was tried before and why it stopped
- Who holds a standing view
- Who asked, and what they will do with it
The asymmetry is not about discipline. It is about what the medium forces. A chat message has to contain enough to act on, and four lines is enough to act on. The context is not needed to begin; it is needed to begin correctly, and the difference does not show up for weeks.
Why co-located teams get away with it
They do not have better briefs. They have cheaper repair.
In a room, the missing constraint surfaces in the first forty-eight hours, because somebody glances at a screen and says "that'll need downtime, won't it". The missing precedent surfaces because somebody overhears a noun. The missing decider surfaces because the person with the standing view walks past.
None of that is documentation. It is ambient correction, and it is almost entirely absent remotely. The same thin brief that costs two days in an office costs three weeks distributed, and the brief is not the variable — the repair mechanism is.
This is why "we were fine before" is both true and useless as an argument against writing things down.
The documents that do not help
Most organisations respond to this with artefacts, and the usual ones miss.
A project template with twenty fields gets filled in by somebody copying from the last one. The fields that matter are the four, and they are not easier to see because a form asks for them in a heading called "background".
A wiki of standards collects the knowledge that was already explicit. The invisible knowledge stays invisible — nobody writes down a standing view they do not know they hold.
A long kickoff document is written once, at the point of maximum ignorance, and is never updated when the context arrives late.
What works is smaller and less satisfying: four sentences in the message that assigns the work, written each time, by whoever assigns it.
Where the context actually lives remotely
Three places, and knowing them is most of the archaeology skill:
The revert. Standing views leave traces in what was undone.
The thread nobody linked. Decisions get made in a channel and never summarised anywhere. The search is unpleasant and it is where the purpose usually is.
The calendar. Who met whom, and when, tells you which decisions were made live and therefore are not written anywhere.
None of that is a substitute for being told. It is what the receiving end can do unilaterally, which is the theme of this whole part: half the fixes here belong to the person handing over, and the other half work even if that person never changes anything.
What writing does that talking does not
There is one genuine advantage the remote case has, and it is worth claiming accurately rather than overstating.
A written constraint can be checked later. When somebody says in week six that the deadline was always the fifteenth, a message from week one settles it in four seconds. The same exchange about a verbal conversation takes twenty minutes and damages something.
A written assumption gets corrected by people who were not asked. Post "proceeding on the assumption that this is for the review group" in a channel and somebody who was never part of the conversation can correct it. Said aloud in a call, the same sentence reaches two people.
And a written answer outlives the asker. The reply to "who owns the pricing table" sits in a channel and is found by search eight months later by somebody who did not know to ask.
None of that happens automatically. It happens when the four facts are written in the place the work lives rather than said in a call, which is a choice somebody makes each time.
So the honest version of the standard claim is narrower and more useful: distributed work does not produce documentation, but it makes written context more valuable than it is in an office, because written context is the only kind that survives, spreads and can be checked.
The claim, restated honestly
Distributed work does not make things explicit. It makes the absence of explicit things expensive, which is a different claim and a more useful one, because it tells you where to spend the effort: not on documenting what everybody already writes down, but on the four things nobody does.