This site contains archived material that may be obsolete. For more information about AIGA please visit us at

Bradley B. Foust, Logisoft Interactive, Rochester, NY, 07-Apr-03
I am always looking back at where things started and where things are going especially as it plays to the Internet and eCommerce. Since that is my focus I design and manage a variety of eCommerce and Internet Sites that all started out in my hands. Over...

Challis Hodge, Chicago Illinois USA, 22-Feb-03
Larry, I don't think anyone on the panel would disagree with your notion that experiences cannot be designed—they can only be designed for. Certainly, if we could design them it would make the job of archiving them somewhat easier. The fact that...

Larry Irons, I.C. Technologies, St. Louis, MO USA, 15-Jan-03

Some of the comments in response to this question as well as the others I've read don't take an explicit position on whether experience design involves “designing experience” or “designing for experience.” The two don't seem equivalent to me. The former implies that the designer controls the meaning that uderlies user experience with a product. The latter aligns with the position articulated best by Paul Dourish in Where the Action Is (2001). His basic point seems to be that “users, not designers, control meaning.”

So, when I think of archiving experience I think of archiving user interaction since that provides the meaning for it. Indeed, that seems to be Peter Morville's point when he talks about making artifacts themselves available for use, i.e. 1994 html, NCSA Mosaic and a 2400 baud modem. I also don't think this view of interaction and experience applies only to computationally capable artifacts, although it is probably easier to spot it in their use. Archiving experience design projects won't do much other than facilitate project managment of experience design projects (a laudable goal but certainly not the expressed one).

LOOP June 2003 Number 7