I have been attending TED for a couple of years and again this year was amazed by the speakers and their insights. For those of you not familiar with TED I would suggest that you visit the TED website where you will find a treasure chest of the most amazing talks on a broad range of subjects – I guarantee that you will be inspired.
TED 2010 did not disappoint – far from it. Several talks inspired me personally but there was one that stood out for its simple yet profound insight – Daniel Kahneman’s talk on “The Riddle of experience vs. memory”. Widely regarded as the world’s most influential living psychologist, Daniel Kahneman won the Nobel in Economics for his pioneering work in behavioral economics — exploring the irrational ways we make decisions about risk (TED description). I have the deepest respect for people who can take the most complex of subjects and explain them in the most simplest of ways – this is was Daniel was able to do.
Now I will certainly not try to summarize or fully explain Daniel’s talk in this blog – for that I suggest that you visit the TED website to listen to the talk first hand. Let me though try and provide you with the basic premise of his talk. Daniel talks about the “confusion between experience and memory: basically it’s between being happy in your life and being happy about your life or happy with your life”. He provides several examples of the difference between the two. In one example Daniel talks about a person who listens to 20 minutes of glorious symphony music yet at the very end there is a dreadful screeching sound. In reporting this incident the listener said that the screeching sound had “ruined the whole experience”. Yet, as Daniel notes, the experience had not been ruined – ” What it had ruined were the memories of the experience. He had had the experience. He had had 20 minutes of glorious music. That counted for nothing because he was left with a memory; the memory was ruined, and the memory was all that he had gotten to keep.”
“What this is telling us, really, is that we might be thinking of ourselves and of other people in terms of two selves. There is an experiencing self, who lives in the present and knows the present, is capable of re-living the past, but basically it has only the present. It’s the experiencing self that the doctor approaches — you know, when the doctor asks, “Does it hurt now when I touch you here?” And then there is a remembering self, and the remembering self is the one that keeps score, and maintains the story of our life, and it’s the one that the doctor approaches in asking the question, “How have you been feeling lately?” or “How was your trip to Albania?” or something like that. Those are two very different entities, the experiencing self and the remembering self and getting confused between them is part of the mess of the notion of happiness. Now, the remembering self is a storyteller. And that really starts with a basic response of our memories –it starts immediately. We don’t only tell stories when we set out to tell stories. Our memory tells us stories, that is, what we get to keep from our experiences is a story. ” (quoted text is an excerpt from transcript of Daniel Kahneman’s 2010 TED Talk)
Implications for Software Design: Daniel Kahneman’s talk and insights provide important lessons for the technology industry. I think that we in the technology industry – especially the enterprise software industry – have forgotten how important it is for users to be happy when using our software products. Consumers take for granted that the software product will deliver on the basic function that it is designed to achieve - complete a purchase request, format a document or manage a supply chain. However, all to often the software is difficult to use, not intuitive and requires too many steps to complete a simple task.
If you view Daniel’s full TED Talk you will note that in essence what he is saying is that your memory of a particular situation or event matters more than the experience of that event or situation. This insight can have important implications on how we design software to ensure that the memory of the use of the software is positive – even if the experience during the use was painful. Maybe Apple had this figured out a long time ago !
I welcome your thoughts and ideas on this topic.