everyone is asking for "intuitive" HMI, for systems that will "surprise and delight" the user.
but, what do these words really mean to the people that design the system? how can you convert these abstract terms into requirements?
I am not an abstract thinker, I like tangible outcomes, prototypes and examples. So here is a good example:
The BMW voice system it was a "surprise and delight" when I asked a question about the fuel level.
I asked a question, very vague and ill-defined, and the system provided: a) current range, b) distance to my destination as it was entered to the navigation system and c) it informed/assured me that it was within range.
This is what I call "surprise and delight"