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.
RE: suggestions needed for teaching a introductory college course in technical writing
Subject:RE: suggestions needed for teaching a introductory college course in technical writing From:"Christensen, Kent" <lkchris -at- sandia -dot- gov> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 24 May 2001 11:16:11 -0600
(two digests today, none yesterday, so a bit late with this response)
Both bryan.westbrook and David Berg disagree with my notion of covering
project management in the introductory course. I'll detail my thoughts.
Both appear to emphasize the "writing" portion of the phrase "technical
writing," while I think my suggestion concentrates on "technical." Of
course most university students have had some prior training (I sincerely
hope) in writing, so more seems like just that, more of the same (but maybe
with emphasis shift away from literature). Most "writing" like that, I
surmise, is an individual thing, and technical writing is certainly not.
Rather, it's a teaming process and teaming processes are something I
perceive taught quite infrequently in public schools and even universities
(I reject high school football as metaphor for life).
For the most part, technical projects at successful firms are managed using
project management techniques and one-person projects are rare, and in these
successful scenarios tech writers are part of the plan. In fact, I'd offer
that all those questioning how to best "interview" subject matter experts
unfortunately find themselves associated with firms not organized for
success--that is, firms where the tech writer is an afterthought and not
part of the team. I should think a good college curriculum would be success
oriented, big picture oriented, and teaming oriented, and that's why I
suggest tech writers learn of project management early and often. A writer
is not a technical writer.
PS: My most recent project? I came on board by myself at the end and had
to "interview" SMEs and do independent research to figure out what was going
on. I produced something (http://www.sandia.gov/elecinvoice/manual.html)
that got very little in-process feedback other than "looking good," and
which I'm still not really certain is any good. I received praise and
awards, but I'm not really happy with what I did because, given the poor
process, I still have no idea if I really did do good.
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Information Mapping, Inc., a professional services firm
specializing in Knowledge Management and e-content solutions. See http://www.infomap.com or 800-463-6627 for more about our solutions.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.