On the ground running: Lessons from experience design
From Adobe Design Center’s Think Tank, May 2007
We live, it seems, in an age in which the long-standing and pleasingly crisp distinctions between what constitutes a “product” and what a “service” are beginning to break down. Even in the early days of this evolutionary shift, we can already see that the implications for both individual designers and the profession of design as a whole are likely to be deep and lasting.
Traditionally, a product was physical and discrete – something obviously demarcated in space but, equally, in time. The designer’s brief rarely extended to much more than the form of an object, at most encompassing the contours of its use immediately after purchase, and that extending only to a narrow range of scenarios and anticipated users. But driven by lightweight and ubiquitous networking, and the open standards it gives rise to, all of this has started to change: no longer can the designer of any product assume that it will stand on its own, autonomous and serenely uninvolved with the wider world, for its entire lifetime of use.
The already-classic example is, of course, the product-service ecology Apple devised for their iPod. Considering the close integration between iPod, the physical device, iTunes, the desktop application, and iTunes Music Store, the online environment, it’s clear that Apple understood relatively early on that the only way their contender would be likely to gain traction in an already crowded field of MP3 players was not to frame it as an MP3 player at all.
Their stroke of genius – and it’s easy to see it as such now, in retrospect, but most commentators missed it at the time – lay in positing the iPod not so much as a stand-alone device, but as the tangible presence in your life of a larger and much more ambitious experience. Apple grasped, before any of their competitors, that evoking a truly pleasurable experience of use transcended questions of the placement of controls or the sequence of menu items, as important as these things are. It required a consistency of conception extending from the moment you opened the iPod’s box for the first time to the way it felt to find new music for it on the iTunes service.
There are two nontrivial insights here, and maybe we’d benefit from unpacking them a little. The first is that the perceived quality of the iPod in use depends to an unusual extent on Apple’s framing what you’re actually buying from them holistically, at the level of the whole undertaking rather than that of its component parts – they get that the product is no longer an isolated entity, but a way of gaining access to content which might ultimately live elsewhere. The second is that getting this “product” right means accounting for your interactions with it across multiple channels, and even more importantly, over time.
In the iPod ecology, then, we have traditional industrial- and interaction-design concerns interwoven with elements which have more usually characterized the architecture of services. When you consider that such interweavings are becoming increasingly common in our day-to-day lives – you can grant an older cellphone entirely features by blowing updated firmware into it, while certain models of Lexus automobiles now come with a subscription to real-time traffic information – the time would appear to be ripe for a new kind of designer to take center stage.
What might we call such a person? Here’s a hint: it’s neither a “graphic” nor a “Web” nor even an “interaction” designer.
Toward the Total Experience
None of the shifts outlined above, mind you, have gone unnoticed by the broader digital design profession, nor has that profession been slow to recognize the potential opportunities involved. Over the past few years, the domain of practice known (if only briefly) as “user experience” has begun to accommodate the new realities on the ground, recasting itself as “experience design.”
Whether the emergence of a self-conscious experience design community reflects a canny land-grab on the part of a few visible and reasonably influential practitioners, an underlying recognition that our technosocial practices have transcended the rather limited model of the “user” ultimately derived from old-school human-computer interaction studies, boredom with a thoroughly mapped landscape, or something else entirely, it’s undeniably been a successful way of framing things.
As far back as 2001, no less authoritative a body than AIGA (“the professional association for design”) had lent its imprimatur to the fledgling field, with an AIGA conference defining experience design as being concerned with a product’s “entire lifecycle with a customer, from before they perceive the need to when they discard it.”
In the years since, the discourse of experience design has steadily gathered authority, offering as it does a way to wrestle and wrangle with the new complexity of the built environment and the objects we encounter in it. (In this, it parallels the emergence of actor-network theory in the academy, a line of thought that accounts for interactions between extended networks of people, ideas, technologies and artifacts. Something’s clearly in the air.)
On its face, this outlook has considerable appeal. There is still no better advice for design students than that offered by the 20th century architect Eliel Saarinen (father of Eero): that things should always be designed with reference to their “next larger context.” Experience design would appear to incorporate this recognition from the beginning, which would certainly better position it to respond to the manifold challenges of design for a networked world than more tactical arts.
But it turns out that there’s a serious flaw in this way of thinking. Ensuring that all phases and aspects of someone’s interaction with a product/service ecology align with the desired vision requires that something little short of total control be asserted over their choices. This, in turn, leaves little room for the self-evident (and lovely) messiness of our lives, not much in the way of flexibility should the scenario of use deviate to any significant degree from that contemplated at design time.
As it happens, another Apple product provides a perfect illustration of the potential pitfalls involved in such overly designed experiences – in this case, the cross-branded Nike+ iPod Sport Kit.
As envisioned, the Nike+ ecology consists of several physical products – a biotelemetric transponder, any of a range of Nike sneakers compatible with it, and an iPod nano – and an online environment where the results of one’s uploaded runs are subjected to a variety of mappings, visualizations and pseudo-statistical analyses. (The desktop iTunes application mediates the flow of data between device and Web site.)
One’s first few runs with Nike+ are smooth and pleasurable, replete with the kind of “thoughtful” touches that generally get lauded as good experience design – Lance Armstrong congratulating you every time your run time exceeds the previous personal best, and so on. But it rapidly becomes apparent that all the smoothness in the Nike+ experience comes at a cost, that it really clicks only if you and everything about the way you use the system conform fairly narrowly to an imaginary ideal.
These insightful comments from Nokia’s Chris Heathcote are spot on:
Designing for one person creates tight end-to-end services. But few companies control the complete end-to-end, and in fact, customers (people!) are wary – it’s normally an excuse to bleed more money out of people more regularly (“we can sell a product and a subscription!”) and to lock people in (how do you get your data our of Nike+?).
He’s absolutely correct, on all counts. In fact, most users will find that their experience is constrained in several ways:
– For quite awhile, the selection of shoes available to prospective Nike+ runners was quite limited: not merely to Beaverton’s own shoes, but to one particular line among their offerings. If you wanted to try Nike+ with, say, a pair of Nike Frees that imitate the biomechanics of running barefoot, you were out of luck.
Although Nike recently announced that all of their shoes would henceforth be fully compatible with the system, it may not matter; as it turns out, hacking Nike+ so it works with non-approved shoes is a simple matter of duct-taping the transponder to whatever trainers you already have lying around the house. That the system works equally fine with its input taped to an old pair of Adidas is an indication that this particular dimension of control was not definitive of the experience. This is a point to which we’ll be returning.
– The sense of needless constraint is, perhaps, equally imposing on the Apple side of the house: of all the available models of iPod, only the nano works with Nike+. Given that other models come equipped with the appropriate connector, there’s no obvious justification for this decision either.
– Nike+ motivates the runner by announcing the achievement of incremental performance goals – you’re reminded of elapsed run time at five-minute intervals, for example, in addition to when you’ve hit the halfway point. Apple has thought things through enough to realize that different people are motivated by different triggers, so they’ve at least provided a choice between male and female voice actors.
But the voiceovers are such an intimate presence that any offness in them registers disproportionately. Since the system affords no way to upload alternative motivators – a coach or drill instructor, a personal hero, a lover – this is likely to remain a sore point.
– What about users, and uses, of the system outside the envelope imagined by its designers? Nike+ feels unnecessarily over-optimized for a single kind of runner, and a single kind of run. (Heathcote nails it: “I can see the persona on the flipchart now,” and anyone who’s worked in the field for more than about ten minutes knows precisely what he’s talking about.)
There’s nothing in the system’s technical capabilities that prevents it being of utility to walkers, for example. They may not necessarily be as sexysweaty as the users featured on the Nike+ site, but would surely appreciate being able to take advantage of its pedometer and calorie-tracking features. Why exclude them, literally by design?
– Perhaps the deepest question facing the Nike+ online experience is that of the t dimension. Manufacturers like Sony and Nike who rely heavily on complicated, Flash-driven experience sites for their products often find the sites hard to maintain or update over anything beyond the short term.
By contrast, of course, for a great many of its adherents, running is a lifelong activity. Where will they turn in three years if Nike decides there’s no longer any percentage in supporting Nike+, or if the latest release of iTunes fails to mediate smoothly between device and site? Will they be forced into an expensive, exhausting cycle of multiple upgrades and compatibility hurdles, or, still worse, find themselves in a technological cul de sac? The more the desired brand experience relies on a concatenation of closed systems from different manufacturers, each of which is subject to revision (to say nothing of a realignment of corporate priorities), the less likely it is to survive intact over time.
As Heathcote suggests, many of these problems could be obviated by opening up the Nike+ platform, allowing people to swap in shoes and other components of their choosing, or even to build custom mashups of their own with the data it generates.
This is, admittedly, not likely to be terribly appealing advice from the point of view of those stakeholders committed to a heavily-branded experience. From this perspective, it’s an offering of Nike and Apple: why on earth should they design it so shoes or music players from other manufacturers work equally well?
But if the choice is between an overcontrol that will predictably result in an eventual breakdown, and a flexibility that admits other players but also affords more satisfying long-term outcomes, which would you rather have your brand associated with? In the final analysis, about all that can be said about end-to-end control of a multi-touchpoint customer interaction is that it results in a perfect experience….except, of course, for when it doesn’t.
Fast train to nowhere
Several years ago – and it was one of the first occasions I personally recall hearing the phrase “experience design,” now that I think about it – design firm IDEO presented their work on the design of Amtrak’s then-new high-speed service, Acela.
At the time, IDEO’s work on Acela could fairly be regarded as exemplary. They surely had the right instincts: originally engaged to design the cabin of a railway coach, they understood that the actual design challenge before them was significantly broader, that the form of the coach was merely a small part of what travelling by train is all about. Still more insightfully, in accordance with Eliel Saarinen’s wise counsel, they had situated that portion of the journey during which a customer was travelling on rails as merely the central segment of a far longer experiential arc.
IDEO divided this arc into ten distinct phases; their conception of an Acela trip began even before passengers had necessarily settled on travelling by train, accounted for the rituals of arriving at the station and purchasing tickets, and followed until they had transferred to another mode of transportation upon arrival at the destination.
The clear intention was to ensure that the customer interaction inscribed in each of these phases was designed to the same high standards as an IDEO mouse or shopping cart. But with the best of intentions, this way of thinking led Acela into error.
The assumptions embedded in the plan are too tightly coupled to one another. They feed from one to the next – remember the word – seamlessly, like brittle airline timetables so tightly scheduled that a delay anywhere in the densely-interwoven mesh of connections cascades through the entire system. When it all succeeds, it’s magnificent, but if any aspect of it fails, the whole thing falls apart.
That the whole thing has, in fact, fallen apart will be readily attested to by anyone who’s taken the Acela lately. Conceived as a competitor to world-class rail services of long standing, like France’s TGV and the Japanese shinkansen, the level of amenity Acela offers its passengers simply doesn’t even come close. From the frankly broken ticketing process, to the tatty waiting areas (it would be stretching credibility to call them “lounges”), to the flickering, dysfunctional arrival/departure screens, to the occasional surliness of onboard personnel, Acela is a system that has failed to uphold the minimal standards seasoned travellers expect from a would-be global contender. Even Korea’s KTX offers a more refined and a more pleasant intercity service.
Notice that these pitfalls have a commonality, that of maintenance. As originally devised, each of the components of the Acela proposition made perfect sense, but they have been allowed to degrade over time. Those that have defaulted drag down the perception of those left behind, until any clever touches there may be in the design of the train cabin or the station signage no longer even register against the net impression of hassle and irritation.
This tends to be a particularly acute issue wherever a designed ecology brings human beings face to face with one another: as things now stand, experience design’s Achilles heel is that contemporary American customer service standards are nowhere near the level of refinement routinely achieved by product and interactive designers. A combination of low wages, disinvestment in training, habitual recourse to offshoring, and deeper cultural factors has left American businesses without a large pool of workers motivated to provide customer service at the level routinely specified by designers. The result is that experiences seamless on paper break down badly the moment a human being enters the loop; the necessary follow-through simply isn’t there.
The suggestion here is not that these crucial interactions be left to chance, to design by committee or to the exigencies of the moment. But there are real limits on what a design organization can reasonably expect to achieve. Designers may well be able to specify the degree to which a seat reclines, the font in which a sign is set, or the sleek lines of a uniform – but not the behavior of the person in that uniform, and ultimately, that’s far more likely to determine the tenor of any experience. Acela’s lesson for experience designers is simple, one that most of us learned in childhood: don’t bite off more than you can chew.
Pumas for Achilles
People, of course, aren’t always the weakest link in a product/service ecology. Puma’s Trainaway line provides us with a perfect illustration of some the pitfalls that await when total experience designs cannot, for one reason or another, be carried through.
Ambitious in conception, Trainaway is positioned as sleek, lightweight running gear for whatever’s left of the jet set, specifically designed to help people maintain their fitness routines while travelling. In addition to the shoes and clothes, the ecology comprises a series of cardkey-sized, plasticized maps to running routes in major cities worldwide, slickly-produced SoundWalk MP3 audio guides, and alliances with suitably aspirational partners, such as the W hotel chain.
One of the most appealing aspects of Trainaway is that it’s clearly been conceived not simply as an integrated system of products but as a coherent experience. The trouble, as we’ve seen, is that such things are delicate, and delivering on them depends vitally on the smooth coordination of heterogeneous and inherently unstable components. In this instance, that smooth coordination is missing in multiple ways.
We’ve already seen how a lack of adequate employee preparation and training can undermine an experience proposition. When Puma’s own retail personnel don’t know how to explain or merchandise the Trainaway components on their own shelves, the augurs are not good, and indeed, it only gets worse when you visit a W hotel in an attempt to extend the Trainaway experience: the desk staff at New York’s W had never heard of the tie-in with Puma, and had absolutely no idea what if anything it required of them.
Such breakdowns in customer service are, by now, sadly predictable. But even at the raw level of product design, the necessary degree of follow-through is missing. The jacket has fittings and pockets for an integral fiber-optic safety lighting system that would admittedly be innovative, if the light source were anywhere to be found. (Despite being called out on the Web site as a product feature, neither customer service contacted via the site’s email form nor, again, the staff at Puma’s retail store were able to explain just how this feature is supposed to work.)
And then there are the blunders that only a self-conscious “experience” designer would make. The Trainaway shoe features an outboard slot for storage of your hotel’s cardkey; anyone who actually runs – even most nonrunners who spend a few minutes contemplating the question – would have a vivid sense for how rapidly and thoroughly this slot is going to be gunked up with the vile muck of street, path and trail. Given every possibility offered by an integrated collection, why on earth choose the bottom of the shoe for storage? This is the kind of too-clever-by-half “solution” that only someone trying to force-fit components into an imagined ecology would have introduced into the product development process.
Finally, the online components of the experience don’t appear to have been thought through with any particular clarity. However lavish, the audio guides are the kind of thing you listen to once, at most. A map of the Tiergarten does me little good should my travels happen to take me to Manila or Buenos Aires. And whatever other mistakes Apple and Nike may have made, the hassle involved in manually entering a long alphanumeric authorization code to download these goodies makes you positively nostalgic for the plug-and-play integration of Nike+.
Is Trainaway a complete disaster? No: at the end of the day, what you get for your money is still a perfectly serviceable array of running shoes and clothes. But it’s unclear, at best, if there’s actually any enhanced value to the consumer as a result of all the experience-design trappings. When so much time and effort are lavished on product, on advertising, on the design of a Web site, on maps and audioguides and other collateral, shouldn’t the ROI on tying these things together be more self-evident?
More fundamentally still, if the entire aim of the product/service is allowing you to maintain your fitness routine while travelling (“[m]ost often, even the best intentions result in gear that’s left idle, never making its way out of the suitcase”), we should ask ourselves whether design is even an appropriate response. This may simply be an issue that’s beyond the ability of an experience designer to affect.
So what might a more approproate ambit for design look like, in the context of complex networked product/service ecologies? How might someone interested in providing people with consistently high-quality experiences address the problems of overly brittle planning suffered, to different degrees, by Nike+, Acela and Trainaway? Some useful hints might be gleaned from domains as close to design as architecture – and as seemingly distant as cybernetics.
Conversations, not control
We’ve seen that highly designed experiences tend to suffer from a consistent range of limitations: physical components that are brittle, unreliable, or not delivered to specification to begin with; difficulties integrating those components with online environments, with desktop or mobile applications, and with human participants; and finally, the inherent unpredictability of any attempt to maintain consistent feel across technosocial systems of heterogeneous type and nature.
Could it be that more headway will ultimately be made when designers conceive of desired experiences as overarching but essentially open narratives, into which individual consumers can insert or demount components at will?
In architecture, the idea of maintaining precise control over the specification of an infrastructural framework, while ceding control over local circumstances to the user, is one with a respectable pedigree, so much so that it has historically appeared in a variety of places, times and guises.
The “kit of parts” approach – in which theoretically endless cities are generated by plugging housing, recreation, and production modules into circulation networks, like the pieces of some gigantic children’s construction set – is most often associated with the delightfully high-flying British collective of the 1960s known as Archigram. Similar tendencies characterized the work of Archigram’s direct Japanese contemporaries, the Metabolists.
Other architects went further still. Constant Nieuwenhuis’ New Babylon, Yona Friedman’s Spatial City and Cedric Price’s Fun Palace all envisioned immense open bays in which finer-grained control of the environment was left to individuals, or small groups. Meanwhile, Reyner Banham and the other prophets of “non-plan” architecture proposed that all but the most vestigial urban planning be done away with, the better to allow a community to find its own most vibrant mode of spatial expression.
There will be a great deal that contemporary experience designers can take from these examples, especially their sense of the continual, shifting, delicate negotiations between the overall perception of an ecology, and how that perception is locally inflected by the input of participants. (Similar ideas can be found in the thought of cybernetician Gordon Pask, who constructed human-computer interactions not as sterile control and feedback loops, but as “conversations” among a shifting retinue of observers and participants both technical and human.) Implicit in many of these visions is a stance that only in a loose and forgiving framework – what we might think of as an “underspecified” one – can the really valuable experiences happen.
There’s a tacit model underneath what is being proposed here, and if it seems familiar, it should: it’s the Internet. Years of working with the Internet and with the World Wide Web built on top of it have accustomed us to a logic of “small pieces, loosely joined,” in which the network is open-ended, effortlessly extensible, and robustly resilient to the failure of individual system components. Finally, this logic has begun to filter out into our experiences of the physical world – and imagine how much better offerings like Nike+ would be if they fully embraced it.
If absolutely top-shelf design organizations like IDEO and Apple are unable to fully encompass the challenges of everyday life in the real world, how much less so their less able peers? How, for example, would the Nike+ experience feel if its various touchpoints had been devised by Microsoft, the same institution that brought you Clippy, the Blue Screen of Death and the DRM-hobbled Zune? Isn’t it better, then, to open these systems up – to provide the APIs and other hooks that would allow people to configure them to their own liking?
This goes beyond William Gibson’s oft-quoted and unimpeachably correct observation that “the street finds its own uses for things,” toward the recognition that designers cannot, even in principle, encompass at design time the full range of uses to which their work will be put. In some respects, too, this is what human-computer interaction guru Don Norman is alluding to, when he argues that the person formerly known to experience design as the “user,” “customer,” or “consumer” needs to be understood as a human being before designers can do their work properly. Any other approach, he reasons, risks treating this person as an instrumental component, not as someone capable of fully participatory co-creation.
Norman is, of course, right, as far as he goes, but he doesn’t go nearly far enough. Truly making room for human prerogatives in the context of heavily-designed product/service hybrids means that, wherever possible, such systems ought to allow people to swap their own desired components in and out at will, to pull data out in a useful format, and to preserve value even where one or more component has broken down.
Does this mean that there is no justified role for the experience designer? No, of course not. Ultimately, though, the best solution may be to plan for people configuring their own experiences – the same distinction reflected in the title of Dan Saffer’s recent book (Designing for Interaction) vis à vis that of Bill Moggridge (Designing Interactions). This may seem like semantic pedantry, mere quibbling, but the difference is crucial: people are already organizers and designers of experience par excellence. Why not let them continue to be?
And this leads us, finally, to the concept not of the seamlessness of designed experience, but of “beautiful seams.”
This term was coined by the late Mark Weiser, a pioneer of ubiquitous computing and the Chief Technologist at what was at the time the Xerox Palo Alto Research Center. Instead of the discourse of smooth, distinction-obliterating, disempowering seamlessness which was then (and is to a significant degree still) dominant in discussions of ubiquitous information processing systems, Weiser wanted to offer users ways to reach into and configure the systems they encountered; ideally, such seams would afford moments of pleasure, revelation and beauty.
Regrettably, Weiser never fully developed this notion, but others have taken it and run with it. And this in turn suggests a valid and a valuable, if relatively minimalist, role for the experience designer: crafting the seams between the distributed components of a product/service, such that they enhance the perception of the whole. This means limiting the ambition of the designer to those aspects of the experience most likely to be definitive, which most require and would best benefit from expert guidance and intervention.
In the long run, providing for high-quality experiences in a deeply networked age means having the humility to know when our efforts are most welcome…and when, as designers, we must let go.
68 responses to “On the ground running: Lessons from experience design”
Trackbacks / Pingbacks
- 25 June 2007 -
- 26 June 2007 -
- 26 June 2007 -
- 27 June 2007 -
- 28 June 2007 -
- 28 June 2007 -
- 28 June 2007 -
- 28 June 2007 -
- 30 June 2007 -
- 30 June 2007 -
- 1 July 2007 -
- 1 July 2007 -
- 2 July 2007 -
- 4 July 2007 -
- 5 July 2007 -
- 5 July 2007 -
- 10 July 2007 -
- 13 July 2007 -
- 22 July 2007 -
- 22 August 2007 -
- 18 September 2007 -
- 5 October 2007 -
- 23 October 2007 -
- 19 November 2007 -
- 26 November 2007 -
- 7 December 2007 -
- 15 April 2008 -
- 12 August 2008 -
- 24 August 2008 -
- 5 February 2009 -
- 28 November 2009 -
- 26 March 2010 -
- 23 April 2010 -
- 22 August 2010 -
- 7 June 2011 -
- 10 September 2011 -
- 10 August 2014 -
- 22 August 2014 -
- 22 August 2014 -
- 13 September 2015 -
- 8 December 2015 -
- 24 December 2015 -
- 14 August 2016 -
- 19 October 2016 -
- 25 October 2016 -
- 11 March 2017 -
I wish I could remember who I read, 5-10 years ago, that said, basically, holistic never ever works. It’s true, and it’s the elephant in the room of experience design, and especially experience design practices who preach end-to-end design. It’s a humble company that accepts this and designs for this.
(and, errr, thanks for the link :) )
Fantastic article! This is definitely something I’m forwarding to my professor/peers. Thanks!
What a stimulating read! It raises many questions that haven’t been publicly aired before, for which it proposes novel answers. But some questions remain, begging to be answered. These revolve around the very nature of experience.
If experience occurs in the mind, as a function of many factors, some external and “designed,” others internal to the “experiencer,” the degrees of freedom involved in designing for an experience are enormous, possibly — in the context of a human’s possibility to parse — infinite.
Nevertheless, people — not necessarily designers per se, just people — do create arrangements of things and meanings that achieve a fairly consistent, reliable level of excitation and even comprehension among experiencers. Notre Dame cathedral is a good case in point: everyone brings something different to it — historical knowledge, reverance of the Catechism, friendship with the organ player — but when the sun slants through the Rose Window, experiences of a aesthetic goodness or holiness or connection with the Godhead are regularly invoked in the beholders, especially if there’s liturgical music playing in the background.
I don’t understand in this case how the designer — a long-ago carpenter or priest — drew the line between what he should do and what he shouldn”t. I have to believe that most organic designs, those designed to invoke spiritual experience for example, are planned to be holistic, even if their designs work other than as intended. The concept of seams as used in this article is based on industrial manufacture of clothing and products. “Seams” seem out of place talking about the more extreme emotions, beyond what one feels when a kid’s toy breaks or the Acela comes lugging up a hill.
This is a very good article, not least because it shows us how much we don’t know about experience design that remains to be discovered and known. Also, we need a lexicon so that we can sensibly discuss and share knowledge about experience design. As things stand, we can allude to experience by describing the factors (at least the external factors) that produce experiences. But that’s not enough as we grapple with the essence of experience, inside as well as out.
Just so long as it’s not “qualia.” ; . )
This is just what I needed! It’s one of the more insightful, practical and applicable articles I’ve read on Experience Design in a while. I’m sharing this with the folks at Critical Mass and I’ll also be doing a write up. I think I may even use some visuals that seem to go well with your written thoughts.
Nicely done—I especially like the thinking about “control” in Experience Design and how this fares in the real world.
Thanks for bringing up such an accurate analysis.
I will try to give the essence of your thoughts in French on my blog.
Great article. i think you’d enjoy ezio manzini’s work very much. He talks about service design and control in terms of multiplying the “points of entry” to a service and a closed path being “disneylisation” of an experience. He’s a very influencial writer on the service design scene.
Wow, he’s like a veritable critical LIVING GOD of systems that have failed to uphold the minimal standards seasoned travellers expect from a would-be global contender!
You know the refrain, Bruce: it’s a dirty job, but someone’s gotta do it.
Adam, thanks for turning me on to “qualia.” It’s a powerful concept, tantalizingly inaccessible.
It’s almost inevitable that anyone studying experience will reinvent qualia as a category of phenomena, whether or not the category’s useful for designing experiences. What’s the alternative? How can we talk about experience so that we get the “Ah-ha!” without resorting to anecdotes that always are particular?
It’s amazing how companies talk about “brand experience” as if it’s the same thing as “experience design”. They make it seem as if we’re now in an age where we are “experiencing brands”, or trying to make the “brand experience” more about the consumer.
The reason I think we really need to differentiate the word “brand” from “experience”, and crowbar them as far away from each other as possible, is because “brand” will always be, no matter how nicely you wrap it up, about the company, and not about the consumer. It’s an impression they want to make to us, and is therefore always from the company to the consumer, from the inside-out.
Experience Design on the other hand, should be about the consumer, about their needs, their desires and expectations. It should be about making what they are trying to achieve as good as possible, the best it can possibly be. It’s about designing things from the consumer’s viewpoint, from the outside-in.
It’s great you highlighted that we need to give the consumers more control, if not total control, rather than force them into an experience we set out for them… Still trying to figure out how to do that exactly and have a company foot the bill for that and explain to them it’s ultimately profitable/desirable? Your article raises as many questions as it tries to answer :-)
Anyways, thanks for the great read, I’ll pass it on to my fellow students at Pratt…
Very interesting article, Adam – you’ve really given me a lot to think about. I think that you’re taking too narrow a view on Nike+iPod, however. It’s a platform, and as a result, it has the potential to change dramatically going forward. In a lot of ways, it’s probably good that Nike designed for limited functionality and a small set of users. I’m written up my thoughts over at Better Than New, if you’re interested in continuing the conversation…
I was just thinking lego sets.
Most of them come with specific instructions to build specific objects – a tightly-designed user experience, while others come with just the pieces – a totally user-controlled experience.
Of course, even those pieces designed for that specific purpose are still user-customizable. No wonder legos remain popular.
Great article. This reminds me of Stuart Brand’s “How Buildings Learn” as a recipe for commodity architectural experience design, it which he proposes two approaches that he has found to work:
1. Open up raw capability on the cheap and let all flowers bloom in the wilderness.
2. Have an array of careful owners working with local craftsmen generation after generation to embed a body of shared knowledge.
and one that he doesn’t:
1. “Magazine” architecture that wins prizes, but is near impossible to configure or maintain.
The same might be true for experience design. There is a role for designing the pieces (similar to industrial design), and there is a role for designing the particular configurations for a single customer (similar to architectural design and interior decorating), but the highly-prized initial configuration might be a much more limited role than initially imagined. Maybe the role of the experience designer is usually to figure out how the design can be changed by experience, and only rarely to change the experience via design.
I havent yet figured out if I agree or disagree with the piece. I fundamentally agree with the principles; I fundamentally disagree with the way in which they’re postured. More:
Well, you can’t please everyone, I suppose.
Beautiful article Adam! It seems to me that the idea of “beautiful seams” comes close to my cludgy thought that we should try to think of interfaces as spaces. In other words, I want to be able to locate, discuss, and inhabit every seam in some way.
This is a lengthy article, almost a thesis. The content is fascinating. I kind of understand the alternative to ‘seamless experience design’ as having some seams, i.e. breaks, within the total experience ‘arc’. The designer’s need to have some humility to know where they’re truly bringing value, and where they are not – and may instead be forcing the user to submit to an over-exalted brand’s will. The point of experience design is to engage, not to design users out of the experience, which is the opposite of the purpose of experience design in the first place.
I’m glad I finally ran across this, Adam. Great job focusing on this issue and articulating it.
I think this balance between designed experience and open architecture has been handled interestingly (and sometimes well, sometimes badly) in the online multiplayer-game realm too. I get into an example of Quake in the late 90s in an article from last year here: http://www.asis.org/Bulletin/Aug-06/hinton.html
I’m a little embarrassed at some of the MMOG hype that crept into the piece now, but I still remember how amazing that gaming community was in 97-99. (I’ve since, um, retired from most of that stuff… )
@Andrew yeah i can see the parallels in gaming. But also in many things that are an experience like gaming.
excellent article, very well written.