Re: "Good enough"

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

100% of the time.  However, my conception of "good enough"
is based on thoroughness, not on accuracy. Documenting 30
of a product's 50 potential functions or applications because
the product manager has determined that 90% of its intended
customers won't use the other 20 is a "good enough" decision;
leaving out some detail about the functions or features you are
documenting because they are of low importance and/or there
is no information available is a "good enough" decision.  But
there is still no room for inaccurate information or really bad
writing in "good enough."

BTW, how do you know that nobody will read this procedure
if it's included in the system?

Gene Kim-Eng


----- Original Message ----- 
From: "Cardimon, Craig" <ccardimon -at- M-S-G -dot- com>
> My question for you folks is, how do you all cope with "good enough,"
> and how often does it show up?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ComponentOne Doc-To-Help gives you everything you need to author and 
publish quality Help, Web, and print content. Perfect for technical 
authors, developers, and policy writers. Download a FREE trial.
http://www.componentone.com/DocToHelp/

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.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-unsubscribe -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.techwr-l.com/ for more resources and info.