Main idea

A document meant for someone selects, simplifies, rephrases and orders the material for one precise need. That is its function, and a deliverable that failed to do it would be a bad one.

But that shaping has an effect nobody ever counts: it leaves outside the sources, the hesitations, the discarded alternatives, the examples left out, the intermediate decisions, the contradictions and the nuances you kept in mind without writing them down. None of that is lost through negligence — it is the deliverable that, by being well made, excludes them.

The document therefore keeps what was concluded, and not what made it possible to conclude.

Why it matters

This forbids treating a deliverable as a memory. You reread it believing you will find the work there; you find only its result, and you reconstruct the rest from memory — so badly, and forgetting that you are reconstructing it.

It also explains why defending a decision six months later is so costly: what would need to be shown was never written anywhere.

Layer added by "A deliverable keeps the conclusion and loses the why" (2026-11-06). An audit engagement shows the scale of it: six weeks of interviews, audience figures, an option ruled out and a tense trade-off with management end up as three lines on page twelve. The report is right to simplify; the problem is that it becomes the only trace of the work.

Nuances and limits

Some formats carry part of the reasoning — a decision write-up, a trade-off note. They remain oriented toward an audience, so partial.

And the loss is only a problem if nothing else keeps the reasoning. The defect isn't in the deliverable, it is in the absence of an elsewhere.

Open questions

• Can a deliverable signal what it left outside without ceasing to be readable?