The Knowledge That Never Gets Written Down
The gap between what procedures describe and what people actually know. Recognising which kind you are missing changes what you do about it.
Knowledge
What gets documented is the part a competent person could work out anyway. The gap is reasons, exceptions and judgement.
7 notes in this section
Why Documentation Projects Fail
The standard response to key-person dependence is a documentation push. Here is what happens to it, reliably, and what to do instead.
Writing the Minimum That Actually Helps
What a useful note contains, how long it should be, and the four things worth writing for any activity.
Where to Keep It So It Is Found
Documentation nobody can find is documentation that does not exist. The arrangement that works at small scale, and the ones that do not.
Keeping It Current Without a Programme
Documentation ages faster than it gets written. Three habits that keep it usable without anybody owning a review cycle.
Recording Decisions, Not Just Procedures
Why a thing is done this way is harder to reconstruct than how, and it is what people most need after somebody leaves.
The Things That Cannot Be Documented
Some knowledge does not transfer in writing. Recognising which parts those are stops you from writing uselessly and points at what does work.
Independent guidance on key-person risk, knowledge transfer and practical continuity for small organisations. External tools are compared as operational support; ownership, rehearsal and human judgement remain essential.