Hmm...<<temporary comfort>>...that's gotten me back on a topic that I've
been turning over in my mind for some time now: what is, and how to test
for, emotional response to an interface over *time*...
A group I was working with recently wanted to slow down the login page
to their site with a giant photo of a smiling woman. "We want our
login page to be more friendly," they explained.
I told them that not only was loading speed more important to their
users, but that the photo would lose impact over time...which was what
my gut told me: people would ignore it, or they would begin to see it
differently...and the woman in the photo had an ambiguous corporate
smile -- tightness around the mouth, smile not reflected in the eyes...
This was just an image, but of course I'm even more curious about
emotional response to interactions, and IA, and persistent visuals like
curved corner "chrome" on a web based app...
Anyone else have thoughts they'd want to share about emotional responses
to design over time?
I think we often make interfaces to engage -- that is, entangle -- our
users, and we often test users emotional responses before we launch
things...but do we continue to test that emotional response over time?
Anyone do that and/or have any materials on that?
One problem with literal artifacts is that often they lead to visual
distractions. so while they add temporary comfort, they do make the UI
On 3/7/07, Mark Schraad <mschraad at mac.com> wrote:
> > > On Mar 7, 2007, at 6:44 AM, David Malouf wrote: > > > I would more simply answer your question that a spreadsheet tool > > doesn't need to look like a ledger, a bill pay too doesn't need to > > look like a checkbook, etc. In fact, I would stay clear from literal > > interfaces. They usually break down when you bring them over to the > > virtual. > Literal artifacts are typically embedded into the users schema. In order to
> overcome the comfort and ease that artifact may provide you must deliver
> something in return to provide value. Hopefully, the transition to a new
> medium (in this case digital or remote) provides value to the user, and not
> just the other stake holders. That value can be an easier process, a quicker
> process, better results - or even the fact that they get to keep their job.
> You will need to get rid of that artifact eventually - why not figure that
> out now? > > Mark