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.
> Around here, we're currently working <schmoozing?> with both
> the Development
> and Support managers to get them to authorize time for their
> people to a)
> answer questions in a timely manner and b) review docs (also
> in a timely
> manner).
Around here, our Support people are very helpful in catching
problems with the documents, making suggestions, etc. However,
it's not a matter of their budgeting time for reviews. When the
call comes in from the customer, they take it. Everything else
comes second, and that's the way it's supposed to be.
However, a product release schedule can't afford to depend upon
customers to wait until after document-review time to call in
with their problems.
So, we take what we can get.
One approach that works well with anything except a brand-new
product is to schedule their review AFTER the product is released.
That means, they have to trust me and the Product Verification
group to a certain extent. However, since it'll only be weeks
or months before the next release of a product goes out, the
Support people can review my docs at some leisure and ensure
that their comments and requirements are incorporated in that
upcoming release.
If they catch something urgent, then either they or I publish
a note that gets inserted with any new deliveries between now
and the next release, and which is also pushed out to existing
customers.
So far, so good.
Now, if I could just train everybody that an index is not the
same thing as a concordance... and is not a matter of pushing
a button...
/kevin
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Purchase RoboHelp X3 in April and receive a $100 mail-in
rebate, plus FREE RoboScreenCapture and WebHelp Merge Module.
Order here: http://www.ehelp.com/products/robohelp/
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.
