Archive for March, 2012

Service design faces an important obstacle when it comes to education. Every design problem is a negotiation between a designer, their client and the intended audience but for service designers that interaction is the medium. It’s the object of design. Service design embodies the literal interaction between all three parties much moreso than for first- and second-order design disciplines. That makes it almost impossible to tinker around the edges of a service without buy-in from an actual client, which defeats the point of tinkering in the first place.

My background is in graphic design and it’s hard to overstate the benefit of simply playing around with color and typography and other elements of the medium for the fun of it. Logos, posters, books, t-shirts and packaging offer a hypothetical vehicle for designer to experiment without the need for an actual client. To initiate what Donald Schön called “design games” with a situation in order to learn. There’s obviously a gulf between speculative design and the constraints of an actual project but tinkering on your own is what gets you across that gulf.

Web design is the same way. I’ve been exploring the boundaries between design and code for almost as long as I’ve been a designer. The barriers to entry are so incredibly low that anyone with a computer and a text editor can dive in and start making things. You don’t even need an internet connection, strictly speaking. Anyone with the proper hardware can tinker around with the medium. An entire generation of web designers have bootstrapped themselves into the profession without the need for an actual client or project, or anyone else’s involvement or permission. That experimentation is how we learn.

But for a service designer, not only is such an arrangement less than ideal; it’s completely unworkable. Clients and the interactions they embody are the medium of a service. Designing without a client is like cooking without food. I’ve made this mistake myself and the results help to illuminate the nature of service design. You simply can’t credibly explore beyond the line of visibility without access; or prototype without the cooperation of the people and systems involved. Speculative service design requires buy-in from the client (or at least acquiescence) on a scale that dwarfs the first-order disciplines.

Cobbling together that access is one of the core responsibilities of design schools. Many of the best service design programs are working to provide students with first-hand exposure to hotels and banks and other touchstones of the service industry as sponsors for actual project work. It’s essentially a subsidized platform for tinkering that provides access for students and minimizes risk for the client.

But outside of returning to school, how do you find ways to tinker? Chris Downs of live|work spoke about this challenge at the second Emergence conference five years ago. Short of launching your own service, as they did, one of the best ways to gain experience with the medium is to work in the service industry yourself. Think of it as participatory research.

I worked at a bank for several summers during college and the experience was integral to my understanding of both the front stage and back stage of a service operation. And although my 18-year-old self had no aspirations to service design at the time, and certainly no authority to implement change, I had access to plenty of what I now recognize as service design problems.

But that’s a pretty daunting way to tinker because it requires a commitment out of proportion to the simple curiosity that draws designers to other disciplines. Most people aren’t willing to quit their job to go work at Starbucks as an undercover anthropologist. Graphic designers can pick up a copy of Illustrator and a subscription to Print but until service designers find a better way to tinker we’ll have problems growing the discipline.

A New Landscape

Only 1,368 unread posts to sort though in my RSS reader. I’m a little rusty, but I supposed that’s to be expected. At first glance there are a dozen or more defunct weblogs in my list. Even the sidebar at Design for Service is out of date. A couple weblogs seem to have migrated to Twitter, two others are quickly becoming dormant and one Australian blog was evidently hacked in the past year and never repaired.

David mentioned some new service design activity in the comments earlier today. Any other interesting voices from the past year who should be on my radar?

Sabbatical

This morning I woke to the end of a year-long sabbatical from Design for Service. Five years after starting this weblog, the service design landscape has barely changed here in the United States. Interest has waxed and waned among several academic institutions and Continuum is making good progress but service design is still largely an afterthought.

Looking back, I was able to hold that reality at bay until the SDN conference in Berlin two year ago. Faced with so much fantastic work it was hard not to wonder about the lack of enthusiasm on this side of the pond. The trip was inspiring but, in retrospect, a little demoralizing. The followup last fall here in San Francisco made it even more obvious that service design isn’t on the local radar. I couldn’t even be bothered to blog about it.

In the face of apparent apathy, it’s easy to retreat into what you know. For the past year I’ve been immersed in the life of an interaction designer. That head space is full of engaging problems and complex systems but interaction design is still widely assumed to be digital and that’s simply too limiting. Service design keeps calling me back.

I’m not exactly sure where to go from here, but today is the first day in reviving Design for Service.