Re: Common approach to documentation?
One thing to add to Geoff's excellent suggestions: DON'T solve the problem
yourself.
Along those lines, make sure the company agree that this is a problem worth "solving". It is going to be expensive and take a lot of person-hours (plus potentially travel or international-related expenses). How important is it to your company that all the writers are using the same guidelines? Does it really have an economic or customer impact? If you can make the case that it does, good for you, but otherwise the cost might exceed its value.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
References:
RE: Common approach to documentation?: From: Marguerite Krupp
Previous by Author:
Re: Opinions on www.techwritershome.cjb.net?
Next by Author:
grant writing
Previous by Thread:
RE: Common approach to documentation?
Next by Thread:
A Visio hint
Search our Technical Writing Archives & Magazine
Visit TechWhirl's Other Sites
Sponsored Ads