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 vs. art From:"Dick Margulis " <margulis -at- mail -dot- fiam -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 24 Jun 2002 10:50:41 -0400
I still believe you are so focused on process that you are losing sight of technique. Yes, a product development organization needs a process. But that process has to stay at a higher level than giving writers stepwise instructions on how to write a document. If you get past, "here's the due date; here's the template; here's who to send it to for review," you are micromanaging; and that can be counterproductive.
A writer is a creative contributor, just as much as a developer or a mechanical engineer. A writer is not a widget assembler.
At the detail level, you have to rely on craft, which is intimately related to technique. Remember the _technical_ part of "technical writer"? You can argue that technical writing is writing about technical subjects. I would argue that technical writing is writing using specific techniques that have been shown over time to work effectively. Nonetheless, the application of those techniques, and the improvement and innovation of those techniques is mediated by the creative efforts of their practitioners--craftworkers--not by reliance on a static process.
Phil Levy <PLevy -at- epion -dot- com> wrote:
>process of creating the document doesn't have to change though, is my point.
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.