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 a product needs docs to comply with government regulations, it
can't ship without them.
Service level agreements are sometimes based on the docs.
A complex product may be useless without the installation guide.
On Sun, Apr 24, 2016 at 5:09 AM, Erika Yanovich <ERIKA_y -at- rad -dot- com> wrote:
> Many of our customers would not accept a new product (be it HW or SW) without the docs.
>
> -----Original Message-----
>
> Gene Kim-Eng said:
>> I have never worked on a HW project where documentation development
>> ended up being the critical path to product release. ...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com