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:
Continue reading 5 ways teams can recover from a failed or stalled writing project
Every job hunt and even unsolicited discussions with recruiters during the past few years brought me more tales of organizations continuing to have issues producing and maintaining technical documentation. It is not isolated in one sector, and I keep hearing the same problems repeatedly. This has been a real disappointment for me over the years I was a contract technical writer and now that I have a staff technical writer job.
Developing technical documentation isn’t fun. Otherwise, it wouldn’t be such an afterthought. Things aren’t made any easier with a technical writing profession that is fragmented on the actual role of the technical writer.
Here are some ways organizations sabotage their technical documentation:
Continue reading 6 ways to sabotage your technical documentation
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.
Continue reading A remote worker’s guide to technical document reviews