RE: Mayvbe O/T? - Text development vs tech writing

["Dick Margulis" <margulis -at- mail -dot- fiam -dot- net>]

"walden miller" objects:


>
>>>> This is a big if.

No argument there. One of the beauties of English is that it allows us to write conditional sentences.


>>>> This is the real issue.  What process exists to communicate between the
>writer and the publisher (my word for the specialist).  Often what happens
>in these cases is that the publisher starts as the person to combine the
>text and format the text, but ends up demanding/defining the text:  needs to
>be shorter, longer, etc.  Basically an editor/reporter journalism model.  It
>is an old model, but it is getting new life because of the web and online
>content.  Regardless, IMHO the issue is communication between the writer and
>publisher and the processes for editing, submitting drafts, etc.  This can
>be a real headache if a quality system is not in place for handling the
>writing hand-off in both directions.

Yes. You have identified the issue. No matter what "system" you use, if it breaks down, you don't have a system. I can cite examples of departments where everyone was expected to do everything but, as might be expected, most people did only a few things well. That doesn't produce very good results, either.

>
>I work with a company that handled all of its docs in the publisher/writer
>division.  After five years of this system, none of the current writers had
>ever created (in framemaker) a TOC, INDEX, Master page, Reference page. They
>use frame, but they could just as easily use word or notepad.  Now they
>changed the system back to a writer as designer system (due to a buy-out)
>and the writers are having trouble implementing style guides, being in
>control of their own work, etc.  The publisher quit and as the only
>indexer/designer/etc., they found they had a single-point failure in their
>processes.  This is one of the reasons I am working with their company.  I
>am providing a new style manual, lessons on how to implement it, etc.
>
>I understand that not all writers are good designers. That is why style
>guides exist.  They do free the writer to work on writing not on design.
>However, the change from working without a style guide (just the text,
>ma'am) to working with a style guide can be very frustrating for many
>writers.
>

Again, 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.



>I would resist the path to division of labor (what happens when the
>designer/publisher quits and no one understands the way in which the
>convergence of text into document works).  If that is impossible, make sure
>the draft/edit/final delivery process is well understood by publisher and
>writer(s) and that the convergence process is documented.  Also make sure
>management understands the reasons for the documentation of the processes.
>

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?

Dick

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

*** 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.