In my experience, documentation is the first thing to go when the workload increases. There are always tasks that get labelled as "important, but not urgent" t

In my experience, documentation is the first thing to go when the workload increases. There are always tasks that get labelled as "important, but not urgent" that get pushed out; and documentation that is already known to everyone immediately involved is easy to push out beyond the product release date. Of course, by then other priorities are moved up, and documentation never recovers. The only way I've seen documentation get the priority it needs is if management mandates it as part of the release package on which developers' performance evaluations are based.