It’s never fun watching a technical documentation, training development, or other writing projects get off to a false start or just downright fail. It can be a real morale blow and expose the writer(s) and their team to criticism from stakeholders. However, failures do happen, and it is best to do what you can to recover from quickly.
Writing projects can fail or stall for a myriad of reasons including poor planning, course changes in the project plan, and other risks that may or not be accounted for in the overall project plan.
Here are five ways to get past a failed or stalled writing project:
One of the most useful – yet potentially embarrassing – features of Microsoft Word is Track Changes. Using the Track Changes feature lets you electronically markup your Word documents with edits, additions, and revisions. Think of it as an electronic red pen so to speak.
The potential embarrassment of the feature comes in when you don’t accept the Track Changes. Comments, edits, and revisions not fit for public consumption can leak out. Even if none of the comments are critical, it is just plain sloppy to have a recipient open up a document that still contains markups.
So much is written about the part-time writer or freelancer being the one who complicates part-time working arrangements – they do this, they do that, part-time freelancing during your off hours is going to melt your brain and turn you into a hermit and so forth. These articles only tell half the story and actually do a disservice to writers and potential clients.
While covering project management and collaboration topics for CNET TechRepublic, I had the opportunity to write about Asana, a social task management platform. I liked it so much I started using to manage the editorial checklists I create for articles, blog posts, and corporate client projects.
When it comes to project teams, Asana is a viable substitute for email. I even recommend Asana to freelancers and independents who need to centralize their project task management.
Even in the day of mobile devices and Enterprise Social Networks (ESNs), organizations can’t escape the need to review business and technical documents for accuracy, completeness, and message. I’ve been a student of technical document reviews, for much of my career. In fact, I was a computer book technical reviewer during the great computer book over-publishing of the nineties.