Advantages of Context Sensitive Help (to persuade people to have)

["Carrie Baker" <carriebak -at- gmail -dot- com>]

We have 2 sets of products in our company, with different teams of Product
managers.
One of the products has context sensitive help.
The other is newer and does not yet have context sensitive help.
I think Context sensitive help would be a good thing for this software
product, but the product managers really do not see any advantage in this
(this would  be a new "feature" and take programming time, and QA time, both
of which they never have enough of.)
My boss wants me to give them a presentation to persuade them that an
application really should have context sensitive help.
Anyone got any good arguments that I could use?
(As far as they are concerned even documentation is just "nice to have" and
we were not told of major GUI changes).

--
Carrie Baker
carriebak -at- gmail -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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 

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy.  Watch the demo at http://www.DocToHelp.com/TechwrlList

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -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%40infoinfocus.com


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

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