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.
Subject:RE: Gnaargh! Or, I Am Not Psychic From:Beth Agnew <Beth -dot- Agnew -at- senecac -dot- on -dot- ca> To:techwr-l discussion list <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 13 Sep 2006 10:46:43 -0700
When you do a documentation plan for the documentation you will produce,
ensure you have a Change Control Policy in it, and make sure all the
stakeholders sign off on it. Then you can at least go back and say "here's
the process you agreed to...".
Maybe THEY don't have process, but you can institute processes for
documentation and then encourage people to acknowledge them. It's always an
uphill battle though.
--Beth
-----Original Message-----
> I've just discovered that, shortly after both I and the client went
> through and checked my company's user manual and online help against
the
> product, the development team made some major changes to the UI
without
> telling the doc team.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-