Experience Map?

The "Experience Map" is something I visualized a couple of months ago in an attempt to illustrate what an "ideal" scenario might look like when planning, architecting and designing an interactive experience.  It's a work in progress—but I'm using it internally to help generate discussion and create dialog between different disciplines.  Feedback welcome.

Comments

[billabel]

This is a nice tool. I had one question. What is 'Shadowing'? Do you mean Observing?

[David Armano]

Shadowing and Observing are similar—but I chose to use the word "Shadowing" specifically because it's more aligned with following people as they go about their business in a natural setting. You can still observe people in a usability test (observe their body language etc.)

But in the end—I would advocate either term. Point is to try to do some of it.

-David

[Sergio Poblete]

David Armano's “Experience Map”, from my anthropological poit of view, is a very usefull mind map to dialogue with clients about their needs in Experience Research and Design. But to me also, like a work in progress, needs to go beyond "artifacts" and "interfases" (maybe I wrong): needs to encompass the most diverse kidns of human experiences and contexts. Maybe one way to do it is to change some words that are too much of information and human interfase design. The words Body, Emotion, Laguague, Interations, Spaces, Storys, Culture, Everyday Life, Practices, Interest, Moods = People in context. I like very much the Map, and I'm thinking how to handel this space in between objects and perceptions that one can call: experience/imperience. Thanks for the inspiration. Sergio

[Mike Johnston]

Nice Job. This is a well developed process. I wish many designers and developers could understand this.

Kudos squared.

[DA]

Thanks Mike.

I'm doing my best to leverage this model in my actual work at Digitas. This kind of process does freak out the occasional Planner (they tend to like to own the insight vs. the team)—but I have been producing effective interactive experiences using this model, so until I'm told otherwise I'm having my teams pick up bits and pieces of this flow.