[Sigia-l] "Standard" interfaces? (was: DHTML Menus and Usability)
David Heller
hippiefunk at hotmail.com
Mon Sep 23 16:41:48 EDT 2002
Risk management:
That there are two types of designers. Risk averse and Risk aware. I
think I'm taking the risk aware approach. Everything in design is about
compromise. I'm actually reacting to what seems to me to be "risk
ignore" design methods. Reality isn't something to ignore, it is
something to negotiate with, but to negotiate with you have to be aware
of the risks.
Ah! Another note on this that is becoming clear.
Ziya was saying that if you have to be that customizable then you aren't
the right app. Ah! What happens when your app is really a platform for
developing tools. So when I use the term customizations I mean tooling
environment. All our apps utilize the services of the same basic server.
Customizations on the server are done for sure, but most end up being
configurations as opposed to real customizations. The UI then has to be
customized to handle these configurations and in some cases the UI then
develops its own proprietary business logic systems.
I tried to explain the whole difference of UI types thing before. Maybe
it just doesn't matter. Either employ UCD or don't, or use what you can
out of it. Personally the differences are the business cases that drive
your designs. Can't have designs w/o business case, right?
-- dave
David Heller
Sr. User Interface Designer
Documentum: The Leader in Enterprise Content Management
925.600.5636
david.heller at documentum.com
http://www.documentum.com/
AIM: bolinhanyc // Yahoo: dave_ux // MSN: hippiefunk at hotmail.com
--"If it isn't useful, it will never be usable."
More information about the Sigia-l
mailing list