It’s hard not to be underwhelmed by a product that we already had a good idea of what it would be, especially if you’ve ever used an iPhone. But aside from there being little surprises, and an arguably terrible name (there’s nothing poetic about iPad), what I find more interesting are services the device will enable.

I work for Nokia, so I’m either working on or analyzing new service opportunities created by mobile devices. I’ve been using an iPhone since 2007. At this point, the phone itself is no longer what impresses me. It’s the services that others have built on top of the platform that continue to impress. It’s the same for Nokia devices. Sure, our phones have some pretty solid technology. But it’s the services that mobile devices enable that are really compelling. Nokia Life Tools, which provides agriculture, education, and entertainment services in emerging markets, is a good example. So is a mobile service I worked on last year to help HIV positive youth take their medication.

And While the iPad isn’t marketed to address agricultural issues for farmers or medication adherence for HIV positive youth, I cannot help but wonder what services this new device (and I predict future devices much like it) — somewhere between a mobile phone and laptop — will enable given its size, portability, slick interface, and robust application delivery platform. So while the iPad seems somewhat predictable, the new services it will enable are not. And that, I find exciting.

A small party of Bay Area peeps interested in talking about service design got together this past Friday at Lime in the Castro. The somewhat last-minute event was organized by Aidan Kenny, who was here on business from Kilkenny, Ireland.

The gathering included people from organizations like the American Heart Association, Adaptive Path, Apple, Intuit, Nikon, and, of course, Nokia (me!). The intimate affair gave me a chance to talk to everyone and hear different challenges for service design, from incorporating it more into business development to finding places to practice it. I even got an idea or two for my upcoming service design talk at IxD10.

After coming back from the Service Design Network conference last October, I toyed with the idea of starting up service design drinks here in San Francisco, as it seems to work for the European crowd. I had resolved to kick it off this month, so was happy to find out that Aidan beat me to it. However, since he’s not from these parts, I will try to keep it going. I am looking into some venues and will aim to have a meet-up in February after I get back from IxD10.

Let me know if you’re interested.

“To me, design thinking is the productive combination of analytical thinking and intuitive thinking.” -Roger Martin in response to Peter Merholz’s Why Design Thinking Won’t Save You

While Peter’s original post was in October 2009, the Harvard Business Review called it out in their January/February 2010 print issue. As I tend to think about definitions and terms often in their usefulness in conveying and misinterpreting ideas, design thinking is a term I often ponder and usually loathe. Peter argues design thinking is simply marketing by design firms. And Roger disagrees, saying it’s a real thing.

I agree with both of them. Design firms sell design thinking because design thinking sells (right now). However, combining analytic and intuitive thinking is not something new nor something good designers don’t already do.

As someone who wrote a thesis paper on the thinking behind design, I am no stranger to both analytical and intuitive thinking being necessary for design. Combined, they form the brain behind the process that results in something actually being designed. Without intuition, creative leaps could not happen and new things imagined. Analysis then provides the rigor that ensures the imagined thing will have a useful purpose for people and will be sustainable. That, my friends, is design. There is solid thinking behind it, whether you call it design thinking or not.

I will be speaking at the Interaction 10 conference on Friday, February 5 in Savannah. The title of my talk will be “Service Design: an Interaction Design Perspective.”

What is service design? How is it different from interaction design? Or isn’t it? As an interaction designer with service design education and experience, I will offer my insights into what role interaction designers have in this emerging area of design.

I am super excited to be talking at the premier conference in my field along with others, including Paola Antonelli, Bill Moggridge, Nathan Shedroff, Ezio Manzini, Jon Kolko, and Dan Hill. If you’re attending, make sure you say hello.

Two weeks ago, I was on the island of Madeira, Portugal, for the second annual Service Design Network conference. Like last year, I was part of the planning board. My main role was to review content submissions and help put together the conference program. I also served as a judge for the service design competition sponsored by Volkswagen, ran a workshop on building the SDN community platform, co-facilitated a workshop call “Learning from Failure” with Stefan Holmlid, and I again held the microphone and played the role of master of ceremony.

This was the fourth service design conference I had attended in as many years, and the third that I had helped put together. Overall, I thought it turned out well. But there was a lot of discussion on how to do things differently in the future. With so many great designers in one place, there was bound to be analysis and ideation on how to redesign the conference. After the conference, the planning team mulled over what we heard, what we through went well, what didn’t, and what to do in the coming year. Here are some of my thoughts and reflections.

Location

Madeira will be hard to beat as a conference backdrop. But its remoteness meant fewer attendees and students. The network is hoping to decide on a location for next year’s conference soon. I know Birgit Mager (network co-founder) got a lot of feedback on possible locations. My money is on the UK, though not necessarily London.

We also talked about venturing into the US, perhaps as a second conference next year.

Format

It seemed everyone I talked to was in agreement that the format of the conference felt too traditional and rigid. More breaks, more time for ad hoc conversation, more workshops (more doing), were all things I heard desired. I shared my experience with unconference formats with the planning team and I wouldn’t be surprised if that becomes part of the structure in the future. Personally, I would like to see the conference be more of a facilitator of conversation and action rather than a speaker platform.

Content

While the content was good, it didn’t knock my socks off. I thought it was an improvement over last year. Still, it seemed like a lot of the same territory and ideas were covered (maybe I’ve been to too many of these). I’m hoping that with some format changes and some speakers from outside the community (someone mentioned Richard Branson), things will get shaken up a bit. The best content seemed to exist in the conversations that took place within the conference white space.

Community

“We should do this more often,” seemed to be the sentiment about having conversations and sharing ideas. The problem: the current SDN website does not make this easy. We got a lot of good insights into the needs of the community during the workshop I ran, and now the network is deciding on a course of action. I agreed to advise this activity, so if you have ideas what and how the network communicates with the larger community as well as its role in facilitating conversation and growth, let me know.

The Challenge

There is no shortage of good ideas for next year’s conference and what happens in between. The challenge is making it happen with limited resources and getting input from the service design community. It’s great to see that the momentum the network and conference have gained over the past two years inspired good debate on Twitter and a site to capture ideas for the 2010 conference. During the next year, the network needs to harness this energy and provide leadership while also facilitating grass roots activity.