At 09:47 30/01/2003 -0500, Ulla wrote:
Okay, I see how the term "user experience" can be interpreted in two ways.
But I think there's really only one accepted use of the term in the profession itself.
I'm familiar with usability. I do think that there is a link between usability and competency. Actually, some of my research has shown that if you reach a certain level in one (so, decent usability, or medium level competency), it doesn't matter if the other one is low/bad. You'll make do.
I think the 'make do' phenomenon' is more to do with user needs/system alternatives etc than anything else i.e. if something is sorely needed and there is no alternative source, then users will do anything to get the information from that source or whatever, but that is completely regardless of competency (although there is an assumption that the user can in *some way* access the system).
I'm delighted that we are having this conversation. I bet some people would interpret "user experience" like you did, and some would like I did. So, Thomas needs to make sure he clearly defines it in his book.
My own field is 'user experience', which these days incorporates ideas such as information design, interface design, information architecture, navigation design, visual design, interaction design, content specification, user needs, requirements definition, etc etc. See The Elements of User Experience by Jesse James Garrett for a complete but succinct description of the user experience landscape. Louise Ferguson