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.
Subject:RE: Tech Comm Portfolio From:"Dan Roberts" <droberts63 -at- earthlink -dot- net> To:"'Shelley Hoose'" <shoose -at- mail -dot- metro -dot- net>, "'TECHWR-L'" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sun, 7 Nov 1999 10:16:52 -0500
fwiw, "information designer" doesn't quite sit right - makes me feel like
I'm twiddling fonts and nudging kerns more than bashing out concepts,
procedures, and all that stuff.
This subject was discussed a little while ago. Most folks seemed to like to
stick with 'technical writer' although some wanted to go with 'information
developer'. Both are good - ya gotta get the words first, no matter which
format they finally get delivered in, so TW works. But a lot of what we
churn out is more than (oh dear, this could get me in trouble) just
technical - we write white papers, and policies and procedures, and god
knows what else - but it's information and we develop it from raw
materials - specs, sample code, interviews, beta applications, etc. And,
'writer' might conjure up too many associations with quill pens and
parchment. And 'technical communicator' is just too much of a mouthful for
me to get out easily - it just doesn't roll trippingly off the tongue <g>.
as for 'instructional designer ' - or developer - got me there. I think some
skills definately overlap, but they can be two completely different areas.
and speaking of fonts, anyone out there using that MS Comic Sans Serif? I
kinda like it, makes the doc look less stodgy and intimidating. But then
again, my typical response to finding bugs in the software i'm doc'ing is
"Broke, no good" (long story).
Dan Roberts
droberts63 -at- earthlink -dot- net
Delores Delago for President
> -----Original Message-----
> My generic resume says that I'm a "writer, editor, designer *
> print and
> web." My tech comm resume inserts the word technical before "writer."
>
> But is the word "design" appropriate for the tech field? I
> have not seen
> it often used. Or would "information design" be better?
> Actually now that I
> think about it, why don't technical communicators refer to
> themselves more
> often as information designers -- I think it is a more
> descriptive term.
> Does it sound too high-falutin? Not able to be understood by
> an average
> reader? Because "technical communicator" also does not tell
> the story.
>
> In any case, for those of us (and I gather it's most of us)
> designing our
> docs as well as writing them, is there a common descriptive term?
>
> And, another question: is an instructional designer a
> sub-category of an
> information designer?
