Service Design Workshop with Marc Stickdorn @UNSW

I feel very fortunate about attending a 3 day workshop with Marc Stickdorn co-author of  This is Service Design Thinking over the last few days. It was organised by UNSW and consisted of a really interesting mix of people from diverse backgrounds including students, academics, professionals and UX/Service Design practitioners.

 

A note to the Service Design Community
Marc thinks that we need to share more in Australia! He thinks we should collaborate more and support each other. He said that instead of guarding our own slice of pie – if we share and collaborate more – we will grow the pie. With this in mind I decided to write an extensive post sharing my learnings from the seminar. Please share and leave me feedback if you like :)


1. Why You Should Care About Service Design

Some supporting literature

a. Experience Economy by Pine & Gilmore 1999

b. Service Dominant Logic  - Vargo, S. and R. Lusch (2004), “Evolving to a new dominant logic in Marketing,” /Journal of Marketing, /68, 1-17

c. The rise of Social Media:

This schema below was adapted from one by Adaptive Paths Brandon Schauer

2. The Workshop Format

Marc made us work but it was fun so it didn’t feel like work! We broke into groups and over three days used various service design tools to design a new service or solve a business problem. It was really great to learn new methods by doing. His process is really experiential and I do not believe that you can really learn it without doing it. It was great to do the activities and then reflect on them afterwards on a meta-level in order for us to experience the process as well as understand on how to facilitate these methods.

 

3. The Process & Learnings

 3.1 Do! Don’t talk.

Marc gave us a really short amount of time to do things so we could not talk about it but had to jump straight in and do it. We created lots of “shitty first drafts” which we could then refine. This proto-typing method enabled the free flow of ideas – both shitty and not shitty. We started the day off creating a very shitty first draft of a new service in 5 minutes – so we got failure or the fear of it out of the way early on in the day.

3.2 What workshops are really about…

Workshops are about getting people who usually don’t talk to talk. They are about creating empathy with the customer within cross-disciplinary teams and about seeing things from multiple perspectives. Services are complex and co-created by many different actors over time. These workshops enable an understanding of this complexity, and it’s associated relationships, dependencies, value chains and power structures.

3.3 Activities

Some of the exercises that we did in our groups included:

  • the mapping of value networks (example below) – who are the actors involved and what are their relationships and what values are exchanged?

  • quick ad-hot personas (although these should have been data-driven!)
  • Customer journey maps

  • Service Blue-prints

3.4 Story-telling and prototyping
Marc organised a Skype chat with the guys from Work Play Experience (also the guys behind  Global Service Jam) who use theatrical/role-playing methods (which they call “investigative research”) as a toolset for modelling interactions within service design workshops. This is a form of experience prototyping whereby the group can act out the existing situation and understand the actors involved and their emotional experiences. Everyone can relate to a story and everyone can relate to a scene being acted out. With this format there is no layer of abstraction which needs to be understood to understand or represent a service concept. “Investigative rehearsal” is a really good way to identify the real problems within a situation and explore alternative possibilities. Interestingly this method was inspired by Forum Theatre which was utilised in South America to understand the plight of oppressed villagers to understand and help improve their circumstances.

PROTOTYPING HAS VALUE and a LOW cost! Especially this type.
3.5 The Service Tweet or the Service Poster

Being able to explain your service in 140 characters or representing the key concept of your service within a poster is an important tool for you to keep focus. It is so important for everyone involved in your project to have a shared vision of what you are working on. (I have blogged about the need for all products/projects to have experience principles elsewhere.)

3.5 The steak and the Sizzle
We need steak and we need sizzle.
Service design and the methods we learnt can help with both.

3.6 One common language 
There is one common language and that is the customer!
These methods enable a human centered perspective which everyone can understand.

These tools are powerful ways to break down internal silos and create delightful experiences for your customers, customer advocacy and service differentiation! These methods can provide language and frameworks for conversation and service improvement and innovation.

THANKS to Mark Stickdorn, UNSW, Selena Griffith who organised this and to everyone who co-created this experience. Great to meet you all.
It was fun! I am hoping to be able to use my learnings in my practice really soon.

Human Centred Design, Co-design and Government

Below you will find a talk I gave at a recent conference/bar camp at http://govcampnsw.info

It explains what co-design and human centred design is and shows some examples of how it has been used to shape public services in the UK.

SDN Conference Paris Notes 2011

I was fortunate to attend the Service Design Network conference  in Paris last month.
You can view the talks at this URL: http://www.service-design-network.org/content/media-1

Whilst many of the talks were excellent, below are a few brief notes about my three favourites which you should check out.

  1. I would highly recommend the talk by Craig La Rosa from Contiunuum. Craig shared a case-study he was involved with for Holiday Inn. It was an impressive project where they created a prototype hotel reception in a ware-house out of 25 cases of foam which they used for acting out scenarios with the staff. Better to iterate in foam than bricks! They are big fans of prototyping. They showed too an artefact that looked very much like a ‘design pattern library’ (used in interaction design) which they supplied to their franchisees to help them fit out their establishment with different modules e.g. breakfast area etc. His most salient point was for this Holiday Inn project which lasted 1.5 years was that 25% of it was design work and 75% of it selling in design concepts. Video was a format used a lot on this project to help create buy in.
  2. I also really enjoyed the talk by Julia Schaeper from the UK NHS where she shared some case-studies of co-design projects being done in a hospital whereby staff and patients collaboratively improved that patient and staff experience. Julia has the task of spreading design thinking across the NHS. She showed a lot of video footage of this work in action which was good to see. She stressed the importance of using terminology that makes sense to the participants and at the NHS they have developed toolkits (www.institute.nhs) to empower their staff to create change and improvements from the ground up. Staff are encouraged to think in a different way…the playing field is leveled and staff can ask “how can we do this better” and then act! To facilitate this it is vital that this approach is built into the organisational phiolosophy.
  3. I also really enjoyed the opening talk by Birgit Maher who talked us through the homelessness project in Cologne Germany, Gulliver: A survival station for the homeless. Using this case study she articulated 10 service design basics. I have seen this project mentioned in academic literature a lot and it was really great to see photos of it in process and learn about the details. It’s a really great project which consists of a drop in center for homeless people i.e. people who are not so comfortable with the idea of a home.

Some learning from other practitioners

I have translated my notes from this 2 day conference and have provided a summary of related insights I gleaned from discussions as well as some of my own reflections.

  1. Good service design bridges business and design. As designers we need to be focus on business benefits and be able to show value in terms of both financials and business efficiencies. The next frontier for service design is  being able to communicate it’s monetary value.
  2. The design thinker and the business thinker working together = power! Service design never works alone. Whilst facilitation is a core competency of the service designer, we are more than facilitators. We are experts in visualisation and design process which lead to outside of the box thinking.
  3. Service design bridges user research and strategic business interests. There is a risk that as designers we do too much research. Getting to know when to stop the research component for maximum ROI takes practice.
  4. Service design is concerned with both front and back-office interactions and processes simultaneously.  Staff need to be aware of the whole picture. It is important for middle management to be able to experience from the customer perspective as this is where the problems usually get solved. Senior managers do not interface with customers or solve front line issues.
  5. Include the staff in your research! What motivates them? How is accomplishment measured by, themselves, their peers and the organisation? The buy-in you will get from this from the people that deliver the service can not be under-estimated.
  6. Service design involves “sell-in” to your staff. Participative techniques can help with this and can assist with change management as well. There is a need for the design to be sold in differently to different levels of staff addressing the why should we change?
  7. Empower your middle managers to manage change. Provision of tools and infrastructure to enable change within the organisation is vital.
  8. Your customers’ experiences are largely a result of your staff. Often a service design project involves the change of the service attitude of employees and it is so important to hire staff with attitudes that compliment the organisation. Happy staff make happier customers. Staff KPI’s should include metrics for customer satisfaction e.g. customer retention over sales. Good customer service should be rewarded. Make sure you map your stakeholders as well and try and get the people closest to the top involved.
  9. Staff need to be empowered and not stifled by processes where they can not can not think outside the box and graciously handle exceptions. The way that exceptions are handled makes all of the difference. Staff need to be empowered to handle circumstances that fall out of the usual process.
  10. Understand your clients motivations for hiring you. At the outset of the project explore not only what the organisational aims are but what are the personal motivations of the client side representatives. Understand too their expectations from you and agree on some KPI’s for the project and associated metrics. Further, have regular meetings with your client in order to ensure they are getting what they need from you to manage things on their end.
  11. Speak the language of your client. It is really important to be able to have a shared discourse for your service design work. This is why frameworks are so important. Customer journey maps/service clue-prints become a language whereby everyone in the company uses them and thinks in these terms. It is so important to ensure that these frameworks make sense and are relevant and embraced by the people in the organisation.
  12. Visualisation is key to making services more concrete as a formalisation of the concept. A lot of service design is about communication and sell-in. Good visualisations of non-tangeible services is crucial for getting everyone involved on the same page.
  13. The importance of execution. How you execute an idea is just as important as your high level strategy in the beginning.
  14. User research should be fun! The experience of the research should be part of the reward. People who take $50 for research are often boring. Research is about building relationships so don’t treat your participants as idiots if you want good insights. Extreme users are usually very willing participants if you provide them with fun activities and create good relationships with them. Extreme users often provide the most meaty insights.

Data as a bridge

About Co-design

Expanding upon my last post about the initiative by EU governments to encourage design driven innovation within the EU, I found some videos explaining what co-design is from UK service design agencies Think Public and Engine. This last post had many examples of this drive within UK and both these videos discuss Service Design work they have done for the UK government.

This first one from Think Public :

Interestingly, within this video after talking about Think Public’s work with the NHS someone describes the rise of ‘co-design’ in the video as the “collaboration movement”.

(NOTE: Having not lived in the UK myself….I can only quote by  English friends reaction…”It’s great that the UK government is trying to find new ways to improve their public services ‘cos they definitely need a re-think!”)

This 2nd case-study for Kent County Council by Engine looks at how co-design was used to design local government policy.

Engine helped the Kent local government find new ways to personalise services and help understand the people that they serve.

The people from Kent County Council think that design provides a structured approach for generating ideas and mentioned the value Engine provided by making things tangible, and their ability at identifying and communicating patterns between what a  broad spectrum of customers need.

I recently wrote a post with a collection of quotes about design which seem relevant here:

Herbert Simon – “changing existing situations to preferred ones”

Donald Schon – “a dynamic knowing process”

Buchanan, Richard – “the subject matter of design is potentially universal in scope”

Check out the videos:

Another video about the Kent County Council and Engine collaboration.