So what is service design? I first heard the term service design at the 2007 Design Research Conference in Chicago. Shelley Evenson was the presenter and I remember clearly being fully engaged in what she was saying. Since then, I’ve been hearing more about this evolving area and I’ve been reading a lot to understand what service design is so that I can articulate it in my own words. The funny thing is I believe I have my own definition of service design. Perhaps it’s because I don’t see myself as a professional service design practitioner (uh um, yet) that I feel the need to anchor my beliefs on someone else’s expertise. The thing is that I, too, have expert hands-on knowledge as a user of service systems. You see, I have only worked in service organizations. My ten years of professional experience are in the financial services industry. I worked in the marketing department helping to market and sell investment “products”, a misnomer for investment management services.
Working within a global division of a large French bank gave me an up close view of the complexity of service organizations especially those that operate on a global basis. From my experience, there are a few things you need to consider about service design. the internal ‘clients’–employees who work within service organizations, the external clients (or users) themselves, and the different touchpoints in which one must go through to deliver the service for both the user and the provider. These touchpoints maybe interactions with different people within the same or across different department or the tools and resources people rely on. This is the nucleus. Around that nucleus there are contextual elements to consider such as social, cultural and environmental factors. A lot of what I’ve read thus far definitely focuses on service between the end user and the provider. There is a dearth of coverage on the design of services behind the scenes of a service organization. This too plays a significant role in how a service organization delivers a service. I know this all too well because I worked behind the scenes in the trenches.
When an RFP came in, depending on its type, there were multiple ways to handle that RFP. There was a qualification process which required notification of the right people. There was a legal process to confirm if there were any legal constraints precluding us from responding, there was the response process undertaken by the RFP writer and that process usually entailed collaborating with people in different departments. And then there is the production process..the time to print, package and mail out. The steps go on and on, but you get the point. Getting the information out of the door does not happen in a linear fashion. Each of these processes entails a dynamic level of engagement and interaction with people and technology technology.
So I’ve been trying to sketch this out. These are my first prototypes. More iterations to come.