It always pains me to see documentation left as an aside or an afterthought for any development project, yet I totally get why it happens because I do it far too often myself! You really have to make it part of your process and not something that maybe you’ll circle back to later if you have time … which you never do.

That said, I really like this methodology that I just read in a blog post by Sara Rosso from Automattic…

Work as though you’re constantly training your replacement: document, explain, and be as public as possible with decisions / discussions – leave a trace! Your colleagues will appreciate it, your team can learn and grow because of it, and you’ll (most likely) still have a job. 😮 😀 😉