Process documentation: It’s important

If one of your employees is out of the office unexpectedly, would someone else be able to take over for them? Do you have documentation for your key processes?

planThere are several reasons why documenting processes are important.

Your employees go on vacation and you need to pick up the pieces for what they do when they’re not around.

Your employees will leave your company and you’ll be left holding their bag and you don’t know what’s in it.



How do we judge good documentation?


As Tracey Halvorsen points out:

Documents can be exciting, inspiring, and creative forms of expression. Documents can be “living” data, intended to be evolving road maps that can empower a client team long after the vendor has left and the project deliverables have been handed over. Documents are often the foundations that survive the longest and inform the next iteration of thinking. They are building blocks that should inform the future, not create problems or bottlenecks for the present.

One thought on “Process documentation: It’s important

  1. You could also see documents as a form of narrating your work, which in itself is a valuable form of reflection for the person doing the documentation / narration. However…it’s also important to acknowledge that any documentation is inevitably incomplete – regardless of how thorough it is, there is always going to be a degree of tacit knowledge that can’t be captured in a document.
    And further, the ‘completeness’ of a document – or the perception of its completeness – depends on the reader / user’s level of prior knowledge of the process, task, context, role, organisation, history.
    Harold Jarche has been doing some posts recently on institutional memory / storytelling / knowledge management with some good insights relating to this (e.g.

Comments are closed.