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: What Are Writing Skills? From:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 15 Mar 2005 17:17:36 -0800
It is "special" in that the processes are often specific to the
particular industry, technology or product being documented,
just as the marketing, design, manufacturing, quality and
other parts of a company's development processes are.
The common part of "structuring" your writing, product design,
manufacturing, inspection, service, etc. is not to conform
to some sort of universal "magic bullet" process, but to
understand, standardize and document *your own* process,
and to disseminate the knowledge and skills required to make
it work in order to ensure reliable, repeatable, traceable results
within your own operating and/or regulatory environment. This
is the guiding principle behind various process improvement
and quality management systems, such as Six Sigma, the ISO
standards, etc., and it is what makes your deliverable "structured."
You're doing things you've done before using methods consistent
with methods that have an established record or working for you
before, and not reinventing the wheel or sacrificing chickens
every time you launch a new project.
Gene Kim-Eng
----- Original Message -----
From: "Tony Markos" <ajmarkos -at- yahoo -dot- com>
> Oh, I have heard what everyone has, basically in
> unison, been said. I just have a very hard time
> understanding it. In order to create a structured
> deliverable, you have to employ a fairly rigorous
> structured process (specific steps and techniques). No
> mystery here.
>
> Yet what I hear is that structured writing is
> "special": You can do pretty much do whatever floats
> your boat and create a structured deliverable. This
> is a true mystery to me. I was hoping to get an
> explaination.
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
Your Ad Here! Have a product or service you'd like to get some attention for? Use this space to get the word out! Contact lisa -at- techwr-l -dot- com for more details.
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.