Re: Testing documentation; was, Job listings with demand for salary requirments

[Gene Kim-Eng <techwr -at- genek -dot- com>]

The same way you test product:  by using it as it's intended to be used.
Could be as simple as spending time using the doc with a workstation and
beta build for software.  For hardware, could require assembling a team of
technicians or service people to see if they can actually build, operate or
strip down and rebuild something using the doc.

Gene Kim-Eng


On Tue, Dec 6, 2011 at 8:30 AM, Porrello, Leonard <lporrello -at- illumina -dot- com>wrote:

> Hi Gene,
>
> When you say "test" documentation, I can tell that you are an engineer at
> heart. In the context of reviewing a potential customer's docs, the "test"
> idea intrigues me. What exactly do you mean? Would you tell a prospect that
> you have to "test" their existing docs?
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days.
http://www.doctohelp.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com