TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
>I need to justify hiring a new writer...
>
>Has anyone ever faced this, if so how did you bring them around to your way
>of thinking?
>What is the best way to approach this?
>...a memo...doesn't seem
>strong enough. Any suggestions?
A memo is a start; think of it as your cover letter. Most project managers
eat, drink, and breath gantt charts, so open up Project or TimeLine or what-
ever project management software your company uses and scope out the upcoming
projects. One chart will show you as the lone writer with time lines
stretching
out well into the next century. The other chart or charts will add one writer
at a time or differentiate between the productivity of junior/intermediate/
senior writers until the documentation delivery schedule more closely matches
the company's production goals.
