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: craft vs. science From:"Dick Margulis " <margulis -at- mail -dot- fiam -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 21 Jun 2002 16:06:27 -0400
Phil Levy <PLevy -at- epion -dot- com> wrote:
>Aren't you talking about tools? Why can't the process stay be the same? Does
>a deadline change a process, or the final format? These things are
>transparent to the reader.
A process is mechanistic. I can conceive of an engineered process that would result in procedural instructions turning out largely the same regardless of who wrote them--because each person would be applying the mechanistic process to do so. I can even conceive of a piece of software that could do a credible job of writing certain types of procedures, given a presentation layer coded in a certain way: "1. Enter Name. 2. Press Tab. 3. Enter Title. ..."
I think technical writing encompasses more than writing field-level help, though. Part of technical writing involves imagining how the audience (a rather fuzzy concept when you get down to it) will best understand what it is you are trying to convey to them. Sometimes this involves deciding whether or not it would be appropriate to offer a homely analogy. Sometimes this involves deciding that a diagram would be most helpful.
Judgment and intuition come into play. Judgment and intuition are bought through experience, broad exposure to the ideas of others and the traditional practices of the craft, and reflection.
The best a process can do is formalize the state of one person's (or a committee's, perhaps) experience, judgment, and intuition at one point in time. Perhaps a process can include a mechanism for improvement based on experience, but it can never be proactively innovative. If you want innovation, you want craft.
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
Check out RoboDemo for tutorials! It makes creating full-motion software
demonstrations and other onscreen support materials easy and intuitive.
Need RoboHelp? Save $100 on RoboHelp Office in May with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
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.