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.