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.
". . . technical writing isn't literature. It doesn't require any thought about
characters, dialogue or imagery . . . ."
I am of a different opinion. I believe imagery can be woven into technical
writing. Of course, like all things, it must be done well to be effective.
Also, I believe that characters and dialog have a place in certain types
of technical writing. I am thinking particularly of training materials and
video scripting, where plots, characters, and motivations can be used
with great effectiveness.
As a personal example . . . I've been working on training materials for a
hospital to explain a computerized patient care system. We created
several patients, each with different health problems, and take the
trainee through their admission, surgery, subsequent care, and
discharge. The patients become "real." They talk about their concerns
and pain, their relatives visit them, they improve and get well (although
we gave them an outrageous number of ailments, in order to exercise all
parts of the patient care system, we cured all of them!). I believe these
"plots" work well in involving the trainees in the lessons and sustaining
their interest.
Ellen Fenwick
ellefenw -at- mailstn -dot- sarmc -dot- org
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-