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: Mayvbe O/T? - Text development vs tech writing
Subject:RE: Mayvbe O/T? - Text development vs tech writing From:"walden miller" <wmiller -at- vidiom -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 7 Jun 2001 13:16:58 -0600
First for Kathy:
A single point failure is used to describe an item that, if failed, would
cause a failure of the system.
Now for Dick:
... what's your point? If there is no process in place, there is no process
in place. Doesn't matter what the process was s'pozed to be...
There is always process. Defined processes are not necessarily better than
undefined processes. However, I see this type of division of labor as
counter-productive, if a well-thought-out process is not in place and that
process must be well-defined. I have worked in many places where the switch
from one system to another was mangled because there was not enough planning
put into processes before the switch occurred.
...How about a more flexible model--the one I suggested--where we take into
account the divers working styles, skill sets, and preferences of
individuals and allocate tasks accordingly, rather than insisting that there
is only one way to get the job done?...
I agree that there are many models to choose from, but usually a flexible
model is not one that companies choose. I would not be interested in a
monolithic editor/publisher model, as I have said. I am also opposed to a
no-style-manual model that allows every writer to style their own manual. I
look at these as the two extremes. Most companies seem to sit in the middle
somewhere: a style manual exists, there may be an editor that acts as a
style enforcer or every writer might be expected to enforce the style
manual.
A model that lets each writer achieve and work at their own level of style,
skill, and preference might work in some corporate cultures. Certainly, at
vidiom, we have experts in certain areas: driver docs, API docs, hardware
docs, exploding graphics, graphic design, etc. BUT, everyone is expected to
know how to do most everything, so as to avoid single point failures if
"experts" quit. We have active mentoring on most all products to spread the
knowledge. This does not pre-suppose your work model, but I am not sure how
one would work in a journalism model of writers and publishing editors with
some but not all writers.
Obviously, Judy will have to find her own way in her company.
*** 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 Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.com
---
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.