RE: future functionality

["Swallow, William" <WSwallow -at- courion -dot- com>]

Paul asks:

::  Here's a question: what should you do about future
::  functionality when it already appears in the GUI?
::  (Dummy screens/buttons, etc). Should you
::  (a) mention that those screens will do something
::  at some stage, or (b) just ignore them? (My own
::  opinion was (a), but a lot seem to plump for (b).

How about (c) flog development until they take non-functional elements out
of the GUI?

Non-functional elements in the GUI are dangerous. They can lead to any
number of user confusions/frustrations, resulting in a wide variety of
support calls. If it doesn't work, take it out. You gain nothing by putting
the non-functional elements in the UI... except PO'd users and a heavy
support cost.

***************** 
BILL SWALLOW 
Technical Writer 
C O U R I O N   C O R P O R A T I O N 
1881 Worcester Road 
Framingham, Mass.  01701 
T E L * 508-879-8400 x316 
F A X * 508-879-8500 
www.courion.com 
***************** 

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

*** 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.