From: Didar Zowghi (didar@ics.mq.edu.au)
Date: Mon Feb 07 2000 - 00:34:43 EST
---------- Forwarded message ----------
I'm siding with Andrew, on the user interface design issue. What the user
interface looks like and acts like is a requirement from the user -- how you
make it work is the design. The "designer" may be great at creating
interfaces that users really like -- let the designer and users work
together to define the requirements -- almost guarantees success. Do not
confuse this with doing design, it is requirements elicitation.
I'm somewhat appalled by the statement that the "design can go in another
direction" after prototyping and covering the ground with the user. Are you
just trying to make the customer mad? This will do it!
The design part of the user interface is making it work and work
correctly -- to meet the requirements of the customer/user. Obviously this
is not what lots of people think -- ala the WWW. Many of the web pages
take forever to download stuff --- stuff that no one but the creative soul
who built them would care about. They are difficult to use. Many tools
being used on the web require at least four clicks and often many more to
get to anything useful.
In fact, much of what is available on line today is so time-consuming that
you cannot argue that it is in anyway efficient. The only reason that some
of it survives is that the gosh-awful telephone inteface -- if it's today
press 1,etc.etc.ect -- is even worse.
That is probably much more than enough said.
Ivy Hooks
Compliance Automation Inc.
26254 IH 10 West Suite 115
Boerne TX 78006
Office: 210 698-5565
Direct: 830 755-8099
website: www.complianceautomation.com
This archive was generated by hypermail 2.1.6 : Fri Feb 21 2003 - 11:25:09 EST