I’ve always believed in project documentation as a source of team/project memory, but more than just documenting the ‘what’ of what was decided, I like to document the ‘why’ it was decided. Jennifer Whitt’s article Dress for the Crash, Not for the Ride presents a similar perspective on the value of project documentation… but presents it using a different metaphore. Am I every glad I got into the habit long ago. More PMs need to understand the value of documentation of decisions, actions taken, and related explanations/justifications… Too many PMs believe that a task list is all that needs to be recorded and managed.