Information architect. Manager. Designer. Graphic artist. Writer. Editor. QA. One person—many hats. Such is the life of a lone writer.
There are many joys in being a lone writer, but also several burdens. One person needs to handle many jobs, and sometimes many projects and/or release dates. This can be daunting for the experienced writer and even crazier for a writer who has never worked in a group.
Experience one person’s lessons learned on her 31-year journey as a technical writer with Sailing Solo: A Lone Writer's Journey Continued, an STC webinar presented by Darice Lang from 1:00-2:00 PM EDT (GMT-4) Wednesday, 21 July [click the link for more information and to register]. Over 60 percent of Darice's journey has been as a lone writer, with nine out of the last ten years as a lone writer at a company.
The lessons learned and processes in place for this writer can help you recognize potential problem areas and address them sooner. These processes can be easily adapted to fit your workflow. Word (2003) templates for all process forms discussed will be provided.
I would love to have attended, being a lone technical writer myself for the last 11 years, but as usual the price is too high. Maybe I can pay to watch a replay if my company ever decides to remove our salary reductions. Oh well.