Often for work I need to put together a detailed document (usually about end user requirements) from the ground up, on the understanding that a development team is going to pick it up and use it as a basis for their work. That document could be anywhere from about 5 pages to 100 pages long, and I've got to bring together information from users and subject matter experts and google and my own analysis and so on. The problem is that when you are using waterfall methodology (where software development is a series of discrete steps rather than an ongoing interactive process) then if you procrastinate, you become the bottleneck and you are likely to hold up several teams of people, twiddling their thumbs and getting anxious.
Recognizing when one is procrastinating and kicking oneself up the butt is often required.
