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.
In a message dated 95-09-18 11:43:16 EDT,
Steve_Jong/Lightbridge*LIGHTBRIDGE -at- NOTES -dot- CREDTECH -dot- COM (Steve
>When a technical writer tries to
>document something without having the time, taking the time, or at least
>the effort to learn the subject, the results, as I suggested in my earlier
>posting, can be useless.
This brings up an interesting issue, which is:
How do we resource-load writers who are specialists in only one thing?
I've found that writers sometimes need to manage several projects at once.
This is often the result of having to resource-load writing personnel with
enough work to keep them busy 8 hours each and every day. (With only one
project, what does the writer do when it's out for a 2-week review? Most
managers can't cost-justify this "downtime," even if it is used for
education, training, etc.)
Several projects may involve different subject matters. For example, I worked
for a large bank once. My responsibilities included supporting documentation
for a CD/retirement application, a sales tracking application, the Home
Mortgage Disclosure Act application, a security application, and on and on.
It was not possible for me to become a pseudo-SME about all of these
applications. They're all complicated and vary greatly from each other.