Re: Term "tech writing"

["Susan W. Gallagher" <sgallagher -at- STARBASECORP -dot- COM>]

David Dubin writes...

> When one asks me what I do for a living, I tell them I am a writer. When
> asked what I write, I reply, "I write books that no one ever reads."  S/he
> who has asked smiles and then says, "Oh you must be a technical writer."

I've been known to use the "books that no one ever reads" approach
myself -- but I usually begin by saying that I bore people for a
living. ;-)

> Actually, I tell people that I am an information systems designer. In
> addition to my responsibilities as the department's technical writer, I am
> also the tech editor, graphic artist, tech illustrator, copy writer,
> presentation designer and training support specialist.

[snip]
I agree, David. I've found that there is a perception problem
with the term "tech writer" as far as job responsibilities are
concerned, and I, too, wear many hats (those you mentioned above
and usability tester/interface designer...). It's often difficult
to break into the communications "loop" for a project when you're
viewed as "just a tech writer". But still, I tech writer I be.

I've actually been leaning towards "technical communicator" as
a handle... Mostly because I don't just write anymore -- I
design toolbars and icons and "author" help files and online
tutorials. AND - with the title "technical communicator" I
can more easily convince people that communication begins
with the UI, so that's where I belong. ;-)

Sue Gallagher
StarBase Corp, Irvine CA
sgallagher -at- starbasecorp -dot- com