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.
>If the software is poorly designed you may end up with a manual that looks
>a bit weird. (ie. 5 procedures for doing the same thing; 5 different
>places to access information about doing the same thing; unwieldy
>procedures with 27 steps, and so on). In a good situation, people will
>review your document and say "wow this looks confusing" and you can say
>"that's how the software works" and then maybe someone will change the
Nope. ;) Changes are made the next time around in an _average_ situation.
In a _good_ situation, you would be on the product planning team and
the problem never would have occurred in the first place.