In my field, we call this "preserving the tribal knowledge". Documentation is always worth the effort put into it, even though it never really seems so at the time.
As Bill has noted in this thread, the trick is to determine and distill what is "tribal knowledge". Much of the time, the tribal knowledge is really the "what" and the "why", with a sprinkling of "how" that covers weird and corner-case situations.
Sometimes, the most helpful knowledge isn't directly stated. Instead of describing how to do something, instead describe the 100 ways you've found to screw up and ruin the task. It leaves a person keenly aware of
what not to do, but is still open-ended in how to achieve a creative and efficient solution.
Edited 1 time(s). Last edit at 05/09/2021 12:18PM by rainbowroute.