Why the document does not land
A document states what applies. The person across the table asks something else: why it costs what it costs, how the new thing relates to what was introduced last year, what the next step is if the answer is no. Those answers are in the document somewhere — spread across four pages, none of which is phrased the way the question was asked.
The gap is not knowledge. It is retrieval under pressure, and that is a thing you only get good at by doing it. A PDF in a distribution list cannot deliver it: it can be read, and reading is a different skill from answering.
That holds anywhere business-critical knowledge is produced faster than anyone can turn it into training:
- New products. In wholesale, 140 a quarter is not an outlier, it is the baseline. Budget three weeks of slides per product and the deck is finished once the next 140 are already in the catalogue — built for a revision that no longer exists.
- Onboarding. Every new hire needs the same knowledge, just at a different moment. A classroom date on a quarterly rhythm almost never lands on that moment.
- Methodology. A new sales methodology has been explained once the training is over. It has landed only when it can be recalled in a live conversation. Practice is what sits between the two, and practice is what gets skipped.
So it ends at the brochure. Not out of negligence, but because the arithmetic does not work.
What teams actually do with it
Three patterns show up wherever this gets rolled out, and none of them was the one we designed for first.
- The same-day start. The document goes up when it is ready, not when a training course is ready. The Coach is asking about it that afternoon.
- The change nobody hears about. When a specification, a process or a pricing frame changes, the document changes — and the old answer stops surviving the question. Without anyone rebuilding a deck.
- The quiet refresher. People go back into a topic before a specific meeting. Nobody schedules that, and it is the usage that surprised us most.
