> > It's not so much that the "Save Now" button do what users expect. It's that > it do what users need, which, if I'm not mistaken, is to save the stuff now. >
It's possible I'm just overanalyzing your statement, but when I read it initially, it felt a little unsettling. Granted, I've said many times that "it's not necessarily about simplicity, it's about clarity", which is a statement with a similar intent — to point out that one term/phrase is perhaps accurate than the other and encourage people to consider the distinction. Still, something about it just caught my ears wrong. Maybe it's because it sort of ... cancels itself out. As in, the need the user has at a given moment may only exist because you created/encouraged an expectation in the first place, but then you say a good experience isn't about meeting expectations. Hard to articulate, I guess. Just sounded ... off ... somehow. -r- ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
