Common approach to documentation

Subject: Common approach to documentation
From: "Simpson, Andrew" <ASimpson2 -at- averyberkel -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 27 Mar 2003 10:14:05 -0000


Has anybody got experience of trying to bring 2 separate authoring
departments to a more common approach to documentation.

The company I work for recently merged with a US company. We now have 2
authoring departments; a small team in the US producing books for North
America & Canada, and a larger team in the UK doing the European / rest of
world books & world-wide translations.

An immediate problem has been the amount of documentation re-work involved
when taking the US products here in the UK and vice versa.
The 2 departments produce very different documents (exaggerated by the fact
that one dept uses Framemaker, whilst the other uses Pagemaker).

I have tried to get a discussion going to look at what compromises can be
made and how we can move forward, but have met with stubborn resistance to
any change.

Any ideas?



Andy Simpson
Avery Berkel, Team Leader Technical Author
mailto:asimpson2 -at- averyberkel -dot- com <mailto:asimpson2 -at- averyberkel -dot- com>
Tel: +44 (0) 121 568 1674


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Order RoboHelp X3 and receive a $100 mail-in rebate, plus FREE
RoboScreenCapture, WebHelp Merge Module and iMarkupSoftware, for a total
giveaway value of $473! Order here: http://www.ehelp.com/techwr-l

Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday 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.



Follow-Ups:

Previous by Author: re: Visio question - Line labels
Next by Author: Re: Calling a Bug a Bug
Previous by Thread: Re: BS-ing your way into a Tech Writing job (was: The Tech Writin g World)
Next by Thread: RE: Common approach to documentation


What this post helpful? Share it with friends and colleagues:


Sponsored Ads