by January 31st, 2013on
Adam Connor shared this brief insightful blog post that really caught my attention:
If you aren’t at least considering people’s emotions, you probably aren’t designing for an experience.
I have written about the need to have empathy with our users before, but Adam has very eloquently and succinctly pointed out why it matters. If we are to design for experience, that has to be a total human experience, emotional as well as intellectual.
But wait, you say, I’m designing tax processing software? Isn’t filing taxes a purely intellectual activity and hardly a positive emotional experience? Study after study shows that even what seem to be purely rational activities require and are greatly influenced by emotions. For example, studies have shown that emotion is essential in decision-making, so much so that people who had suffered a brain injury that impaired their emotional capabilities had significant difficulties making decisions. Emotion in design, also, is not an unfamiliar or recent topic. Books such as Donald Norman’s Emotional Design: Why we love (or hate) everyday things, published in 2004, and more recently, Designing for Emotion by Aarron Walter explore the importance of emotions for successful design.
And yet we still need reminders like Adam’s post to consider emotion in the design process. Read the rest of this post »