Re: future functionality

[Bruce Byfield <bbyfield -at- axionet -dot- com>]

"Field, Kristin" wrote:

> Personally, I think this is a bad practice and don't
> feel that any future plans for the application should be in a user's
> (basically a "How to") manual.  I mean, this manual is a year and a half
> old, as I mentioned, and the future functionality is still future
> functionality.

One reason for mentioning future plans is when an obvious feature is
missing. By mentioning it in the manual, you could reduce the number of
requests for it by customers. In effect, you're saying, "Yes, we know
the product isn't all it could be yet."

-- 
Bruce Byfield 604.421.7177 bbyfield -at- axionet -dot- com

"You know there ain't no kind of dream without some kind of debt
And I don't wanna go to bed, ain't nothin' happened yet."
- The Mollys, "I Don't Wanna Go to Bed"

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

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com

TECH*COMM 2001 Conference, July 15-18 in Washington, DC
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com


---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.