T-minus 6 months: As part of an overly ambitious post-tenure career plan, agree to take on major project for outside organization: I am to Revise the Thing, a process that involves a new format, new content, new mechanism for dissemination -- and, like most academic projects, no budget or staff (though other organization members have been generous in making sure I have whatever materials and guidance they can provide).
T-minus 4 - 2 months: Figure out content for the Thing. Worry that I don't have enough, or that it potentially sucks. For the first time in the history of academia, receive promised contributions from outside contributors well ahead of schedule. [?!?] Lapse into false sense of security.
T-minus 2 months: Realize that I need to figure out a design for the Thing. Find software to make it work. Figure out software. Sink back into sloth.
T-minus 2 weeks: Realize that deadline is approaching and, in a burst of activity, get the Thing three-quarters done, then procrastinate for several weeks, letting the guilt build up to critical mass, until...
Liftoff!: Finally finish the Thing (about a month behind schedule) and make it available to organization people.
2 hrs later: Read and respond to two notices (out of 400 recipients) reporting the same minor technical glitch that appears to have occurred in the dissemination phase.** Deduce from the evidence that the problem is likely technology-related, user's end (since the issue appears to have only affected a few individuals rather than everyone), and provide a one-click solution.
24 hrs later: Receive terse one-line e-mail from one of the two correspondents (the other had no problem viewing the Thing once I resolved the issue) explaining that since s/he still can't view the Thing, s/he will be forced to cancel hir organization membership.
**to be fair to myself, this was balanced out by half a dozen e-mails received in the first 24 hours, congratulating me on what a good job I'd done with The Thing.