Tag Archive | service design

Design Thinking – the bridge between the problem and solution

I had a chance to attend a two-day intensive course called `Unlocking the Secrets of Service Design´ offered by CityDrivers. The trainers were Dr. Niels Billou and Adil Mansouri who are experts on Design Thinking and innovation. Both trainers created very energetic and enthusiastic environment that helped us, participants, to get excited about the two-day intensive course.

Trainers: Dr. Niels Billou and Adil Mansouri

During these two days Niels and Adil introduced the principles, practices and the process of Design Thinking and methodology of Service Design. I have some experience about Service Design and Design Thinking from my Service Innovation and Design studies in Laurea. By taking the two-day course, my goal was to learn new tools and methods that I haven’t used before and to know how I can apply these to my future projects. Here are my key take-aways from the days.

Day 1 – Introduction and understanding the customer

The first day gave an overview of Service Design and Design Thinking. After an interactive lecture all the participants rolled their sleeves and started working with the case assignment and exploring the first parts of the Design Thinking process – understanding the customer, collecting and analysing the interview data.

What is Design Thinking?

“Design thinking is a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.”
— Tim Brown, CEO of IDEO

 

DT

Billou introduced few different definitions for Design Thinking. In my opinion the most descriptive definition for Design Thinking is from Tim Brown. According to Brown´s quotation Design Thinking helps to make decisions based on what customers want. And when using tools from designer´s toolkit, like applying experimentation and empathy that helps to create innovative solutions to problems.

Trainers introduced a Stanford D. School Design Thinking model that consists of five stages: Understand, Observe, Define Point of View, Ideate, Prototype and Test.

DT processStanford D. School Design Thinking model

During my studies I have noticed the stages of different Design Thinking process models are actually quite the same – only the titles and amount of stages vary. Earlier I have been using only the Double Diamond Design Thinking process, since I know the stages and it is familiar to me. So now I was excited to get to know a new process I haven´t used before.

Power of Empathy

Empathy is all about understanding the people. First phase of the Design Thinking process is to understand the customer. Adil talked about the power of empathy and how important it is to step into customer´s shoes. In this part of the process the data reveals underlying needs of the customer. The trainers introduced few effective tools for this data gathering part:

  • In-depth interviews – help researchers to learn more about a person’s experiences, processes, attitude, problems, needs, pains and ideas.
  • Empathy map – represents a customer’s actions and a mind-set. Interview guide can be adjusted into an empathy map and cover what the customer “Think”, “Feel”, “Say” and “Do”.

 

After an interactive lecture the participants were divided in multidisciplinary teams. Trainers pointed out the importance of cross functional teams – it is vital to have people from different backgrounds who co-create innovative solutions together. My group got a design challenge to redesign the workday lunch experience and encourage people into sustainable eating habits.

Our first step was to go out and interview people regarding their lunch experience. We made an interview guide for the interview – one was interviewing and the other took notes. I have been interviewing people before but I haven´t been using empathy map template. I noticed it helped to sum up the findings and catch a deeper insights from the interviewees such as what the user was saying, doing, thinking and feeling. In my opinion this tool works especially well in mini-interviews when having only 30-60 minutes to do the interviews.

Data visualization leads to insights

Our next step was to analyse and interpret our data to find insights from interviews. Niels introduced us a storytelling tool. Each of us had a chance to be a storyteller and describe what we heard and observed from the interviews. The listeners draw visual images about important details on post-its – finally we had a wall full of post-its. The empathy map template used in interviews was very helpful in this exercise.

Storytelling: Capturing data & clustering insights

The last step of the first day was to cluster the post-its and find common patterns between the notes. This storytelling and the visual data capturing were new tools for me. I was surprised how easy it was to see the overall findings when the post-its were full of pictures, and not just text. I could use this in workshops at work when we have limited time to capture customer data.

Day 2 – From Insights and Ideas to Innovation

The last day started with a summary what we had done so far and what was ahead of us: ideating, developing a prototype and testing it with customers.

Finding a focus

We started the day by creating a persona. Adil explained personas are fictional customers created to represent different user types. The persona helped us to step into the customer´s shoes and it guided us to make useful design decisions later during the day.

personaCreating a persona

At this point of the Design Thinking process we were on the “Define a point of view”-stage. According to Niels the Point of view sentence help us to build a line between the initial problem and future solution – it narrows the focus and makes the problem specific. It was surprisingly hard to summarize our thoughts into one sentence.

Next the trainers encouraged us to generate plenty of wild ideas by using how might we… –method. How might we questions launched many crazy ideas and we put those on the post-its. After that it was time to vote for the best idea. Adil introduced a Prioritization Matrix that helped us to identify the most important and valuable ideas, prioritize them and vote for the best idea.

prio matrix.pngPrioritization Matrix

Presenting a Prioritization Matrix on the lecture was a great reminder for me. Once I have been using that during my studies but since there are so many tools it is easy to forget. Since the time was limited during these two days the impact / effort axis on the Prioritization Matrix helped us to point out the best ideas fast. I put this tool into my toolbox and definitely will use this in the future projects.

Fail early, to succeed sooner

In the afternoon we started to build a prototype that eventually helped to solve the problem. According to Niels the prototype is a draft version of a product or a service. It should present our idea and when showing it to the users the aim is to get feedback for iteration.

This was the best part of the day and we were really excited about this step. The team made a prototype out of Legos. This was a first time for me to do this part with Legos. Lego characters were the actors on the stage and the bricks worked very well when presenting the idea and the experience around it. We were very pleased to our prototype.

Building a Lego prototype

The last step of the Design Thinking process was testing the prototype with users. The team went out and we presented the prototype for few users.

“If prototypes aren´t failing you are not pushing far enough. Failure is part of understanding and improving”
– Dr. Niels Billou

final proto.png
Final prototype

Niels’ quote went straight to the point. We got plenty of feedback and enhancement ideas for the prototype and some users crushed the prototype by saying “That won´t work in real life”. We presented the prototype and the feedback for the whole lecture group. Our team proved Niels´ quote true – the failure is truly part of understanding and improving.

To sum up these two days, this intensive course taught me new tools and methods of Design Thinking and reminded me of tools I already knew. Since there are so many tools to use, the hardest part is to choose the most relevant ones for every project. I´m excited to learn more – practice makes perfect, doesn´t it?

 

If you want to discover more different Design Thinking tools and methods, I recommend This is Service Design Doing Method Library. Library consists of 54 hands-on Service Design methods. This is a useful site when choosing the right methods.
https://www.thisisservicedesigndoing.com/methods

tiss

 

Written by: Marianne Kuokkanen

 

 

 

 

 

The key take-aways from POLISHOPA Design Thinking 2019 conference

POLISHOPA is the biggest Design Thinking conference in Poland, two days of interesting lectures and two days of workshops, 16 experts from different fields and 4 speakers from abroad. It was the sixth edition. You can find more details on this page: https://polishopa.pl/

I recommend signing up for the newsletter to get information about the next edition in advance.

20190604_160226

It was the fourth time I attended this conference and this time I had a chance to participate in the lecture days, so-called Revolution & Innovation Days. I will share my key take-aways with you.

Year by year I see an increase in the quality of this conference showing that the knowledge and interest about Design Thinking is growing. However, as one of the presenters (Dymitr Romanowski) showed, although the popularity of Design Thinking grows, web searches for the term “Service Design” decrease. It seems there is still a lot to do regarding educating people on what service design is in Poland.

This year the healthcare and financial sector was highly present. There were representatives of Santander Bank and mBank as speakers. Piotr Sałata from Symetria spoke about how they created a more user friendly vindication platform by Kruk. Adrian Chernoff from Johnson & Johnson spoke about how they solved the challenge of helping patients with diabetes improve adherence and outcomes thanks to patient-led innovation and user centricity. They developed the first diabetes app in the US – OneTouch reveal app.

The participants also had a chance to listen to the story of creating a restaurant in Krakow – Handelek by Socjomania. Silke Bochat told us about implementing and scaling design and design thinking in FMCG companies. Piotr Chojnacki from Allegro (“Polish eBay”) told us how to scale the UX in a large organization without losing the consistency of user experience. Radosław Ratajczak from SHOPA explained how they designed the user experience of Olivia Garden – 8270m2 in one of the skyscraper offices in Gdynia. Tey Bannerman from McKinsey & Company shared a story of disruption at Pizza Hut. Olga Bońka from Motorola Solutions Systems told a virtual lesson of empathy for a dog.

Among all of the mentioned lectures, my key learnings are described below.

If you want to introduce Design Thinking to a company, don’t ask for permission, ask for forgiveness. In Santander Bank, Andrzej Pyra and Jakub Tyczyński simply started organizing Design Thinking workshops. The more people took part in it, the more they wanted to work using Design Thinking methods. What is more, product owners started to ask for their help in managing the whole process in the end.

Empathy is key for making a change. Empathy also makes the transformation last after the Design Thinking project finishes.

Design Thinking is just one type of method used for innovation, it is good to be familiar with other methods such as business model innovation (more in the picture below) as well and juggle with tools and methods depending on the project and its phase, company, and situation.

Innovation methods graphs

Once introducing Design Thinking, there is usually a phase of skepticism which takes up to 2-3 days, it is good to simply overcome it. We also need to understand the cognitive biases and “stamp them out for innovation’s sake” as Mike Pinder from Board of Innovation advised.

skepticism

Mike Pinder also had an interesting definition of MVP: “ MVPs are a way of asking questions about critical assumptions within the features of your concept and business models”.

Piotr Chojnacki from Allegro (a company with 20 million users and 100 million offers and over 150 processes) listed three key points to successful scaling in such a large organization:

  • Diffused structures of teams who work in agile way
  • Local innovation within the global structure
  • Consistent user experience

Silke Bochat presented John Maeda’s list of the top 8 skills that designers need to understand in business as well as the top 10 emerging trends that have the biggest impact on design published in Design in Tech Report.

The Top 8 skills that designers need to understand are the following:

  1. Product Roadmap Strategy
  2. Company strategy
  3. Retention/ Engagement metrics
  4. Conversion Metrics
  5. Funnel Acquisition Metrics
  6. Revenue Model
  7. Financial Metrics (i.e. Revenue margin etc.)
  8. Resource Allocation

In terms of the top 10 emerging trends with the biggest impact on design, here is the list:

  1. AI and machine learning
  2. Augmented Reality
  3. Virtual Reality
  4. Behavior tracking and modelling
  5. 3D printing
  6. Distributed teams and virtual workplace
  7. Democratization of design
  8. Algorithmic design
  9. Crowdsourcing and open source
  10. Facial and voice recognition

For those who are interested in the newest Design in Tech Report, here is the summary of it: https://www.youtube.com/watch?v=Czq2j4p924s

She advised to start implementing Design Thinking with a small project with a limited budget and low risk. Deliver value from it as early as possible. Then promote it if it becomes a success. This gives more chances that it will persuade the decision makers to scale it.

She also recommended to try this canvas in practice: https://www.xplane.com/designops

Zrzut ekranu 2019-06-29 o 23.43.40

Arian Chernoff from Johnson & Johnson recommended answering what, when, where, how and why questions once solving the challenge. In terms of their diabetes app, the answers look as below:

We…

why

…make diabetes easier to manage…

when

…to improve patient adherence and outcomes..

what

…placing the patient at the center…

how

…on a connective cloud ecosystem…

where

…by personalizing experiences.

Dymitr Romanowski explained the role of empathy in health care and shared the results of the projects Human Behind Every Number:: https://humanbehindeverynumber.com/

This is how the project is explained on the website: “Human Behind Every Number is a non-governmental organization that provides research, insight and education on the first-hand experiences of patients involved in clinical trials. In today’s active research industry, our results deliver clear information to industry professionals that will help shape the development of clinical trials around the globe.”

This website gathered patients’ stories throughout their patient journeys which might be helpful for designers working in the Health Care sector.

Zrzut ekranu 2019-06-29 o 22.39.47

From the story of creating Handelek, a restaurant in Poland, I walked away with a feedback tool –  a physical one in the form of a board in the restaurant as well as a virtual one on Instagram. They called it  the card of transparency with Your opinion, Status and What we changed. It obviously helps to deliver real value to customers.

Here is the POLISHOPA summary by professional illustrator, Agata Jakuszko.

Polishopa summary

I would recommend this conference to any DT enthusiast. See you in 2020 in Bydgoszcz, Poland :).

Author: Cecylia Kundera

What I stole from Marc Stickdorn

Event: The 12 Commandments of Service Design by Service Design Network Finland & Service Design as a Tool of a Consultant by myself

Time: 1.2.2019, 18-20 & 15.2.2016, 16-17

Place: Gofore Oyj, Urho Kekkosen katu 7B & Fraktio, Antinkatu 1

Fraktio does many wonderful things and one of those is Perjantaipresis, an event open for anybody to listen to presentations by talented people from various fields. I got the honour to speak about service design there, and since I didn’t want to copy all the service design presentation I’ve seen during this past year, I decided to talk about something I know, i.e. what does it require to utilize service design as a consultant.

I had my presentation pretty much planned and ready, when, two weeks before my presentation, I got the chance to meet my service design guru, Marc Stickdorn, at an event organized by SDN Finland and Gofore. I listened to him sharing his thoughts about service design and the 12 Commandments, and after the presentation all I could think about was “he actually said exactly the same things I’ve been thinking about”. So, on I went with adding some #StickInHel quotes to my presentation.

 

I started from bottom with “It’s all services”. You can’t access a product without touching the services around it, and you can’t offer a great customer experience without aligning the layers around your core offering.

Capture2

12. It’s all services.

The next commandment that suited my presentation was “Zoom in & zoom out”. As a service designer you need to both focus on the tiniest details and understand the big picture.

Capture3

11. Zoom in & zoom out.

I wanted to emphasize that service design is more about the right mindset than the processes and tools. As Marc said, we are not designing in order to create beautiful journey maps. So, the next commandment that I wanted to include in my presentation was “It’s not about the tools, it’s about changing the reality”.

Capture4

9. It’s not about the tools, it’s about changing reality. (And that’s not a walnut but the brain.)

I skipped a few commandments until I found the next one prefectly suiting my needs. Service design is probably 80% about figuring out the problem and 20% about solving it, since the more you know about the problem, the less options you have for the solution. So, “find the right problem before solving it right”. However, as a consultant you need to solve the problem your customer pays you to solve – or convince them that it might not be the problem the actual users would need to get solved.

Capture5.PNG

6. Find the right problem before solving it right.

As a consultant doing service design you need to accept the fact that the resources – money, time, people – are limited. But even as a service designer you can’t iterate to infinity being all “yes, and”. At some point you need to start doing some “yes, butting” and let go of some ideas. “Yes, and” takes you to new places and should be used before “yes, but”, but the latter is important as well if used wisely.

Capture6

5. Yes, but… & Yes, and… For a consultant, it is important to decide which cup to fill first and make sure the customer understands what it means to the end result.

Finally, I pondered the role of service designer and who can and should do service design. I came to the same solution as Marc that in the end, as a service designer “you are a facilitator” who knows a bit of everything but more importantly brings together the people who really know about something.

Capture7.PNG

3. You are a facilitator.

To me, service design is common sense that everyone can utilize, but if you want to succeed there should always be a purpose for it.

You can listen to my full presentation (in Finnish) through this link: https://fraktio.fi/perjantaipresikset/palvelumuotoilu-konsultin-tyokaluna/

I hope you enjoy it!

More information and ideas:

http://www.marcstickdorn.info/

https://www.service-design-network.org/chapters/finland

https://gofore.com/en/home/

Can big organizations be agile?

For big companies, change is hard and slow. No news here. However, corporations that are successful, keep up with the change. How is it done? A few quite interesting points were raised at an event on how to engage your customers in developing digital services organized by Helsinki Region Chamber of Commerce. The event was held on December 10th, 2018 and we heard keynotes from Harri M. Nieminen from Kesko and Mirette Kangas from Yle. In both organizations, service design or design thinking methods were adapted in order to drive change and develop value for the customers. I was keen to hear how change is driven in big organizations, like Kesko and Yle.

Kesko’s Lead Service Designer Harri M. Nieminen shed a bit of light to the way Kesko has started to utilize Service Design methods. As digitalization keeps accelerating, the role and power of the customer grows ever more – and in order to stay in the game, corporations, both big and small have to understand the customer. Understanding the customer is the key to provide excellent customer experience, always and everywhere. This is what Kesko is also aiming for. With his designer team, Nieminen is supporting the organization in building up winning customer experience and a seamless connection between the brick and mortar business and digital services.  

Founder of Agile Company Culture Accelerator Mirette Kangas talked about how YLE has transformed their company culture. At YLE, developing company culture is tangible and practical everyday work. Not a program or a project.  It’s all about learning together and curiously utilizing different models and methods. Part of their mindset is also to share the tools used for others to try as well.

Keep the processes light

To me it seemed that at Kesko, they cherish agility throughout their design processes.  To start with, they emphasize the importance of framing the problem in every project. The key question always is: What are we trying to solve and are we actually looking at the right problem? After the framing and solutions and ideas, they proceed quickly to prototyping. Instead of making it a huge and time-consuming project, the testing phase would, ideally, come in the third day of a three-day sprint. Experience at Kesko show that people are surprisingly willing to give their time and participate in developing new services. So, instead of waiting for the investment decision for a prototype, the insights can be gained through light means as well. The idea is to get things rolling quickly.

At YLE the agile company culture is built on experimentation too. And as Kangas emphasized, it’s not just building it, the culture is also changed through experimentation. However, it has to be systematic, not just experimenting for the sake of it. The point behind all these activities is to ensure YLE’s competitiveness in digitalization. The focus is in the future and innovative methods are implemented in everyday work.

How to succeed?

Design methods, experimentation and keeping your eyes in the future. What else is there to keep in mind, when transforming a large corporation? Both Nieminen and Kangas had some useful tips to share. Here’s my summary of their most valuable points.

  • Ensure things get done. When starting a project, make sure there’s ownership in the organization. Otherwise things might just hang loose in the air.  
  • Keep the customer in mind, always. When developing a new service, keep asking how the customer has been involved and what’s the feedback.
  • Base the change of an organization on voluntariness. It’s the basis for growth and mutual learning.
  • Leadership matters. The leader must reflect every day whether s/he is a preventer or promoter.

By the way, if you want to read more about the event, there’s another blog post about it here.

Engaging customers in developing digital services

Event: Kuinka osallistat asiakkaat digipalveluidesi kehittämiseen? (How to engage your customers in developing your digital services?)

Time: 10.12.2018, 8.30 – 11.30

Place: Helsinki Region Chamber of Commerce

IMG_6789

Helsinki Region Chamber of Commerce has organized a series of events related to digitalisation, out of which this was the 6th one. I haven’t participated the previous events but will definitely keep my eyes open for the next ones now that I got to enjoy this free event where we were served with inspiring presentations as well as both breakfast and brunch. Perfect!

Introduction

The event was opened by Maarit Heikkilä from Digital Discovery. She gave us insights about why service design has become so popular lately and shared her experiences in the industry.

According to Maarit, we live in a time where the customer has finally been brought in the centre of all processes. This has happened mainly due to three reasons:

  1. Unlimited supply of products and services from all over the world
  2. Recommendations and transparency through social media
  3. Customer experience as a relevant competitive factor

Maarit also went through the service design process and the importance of its steps. Some key points from her were that if we don’t define the problem, we won’t get proper solutions, and that we should bravely put even the wildest ideas to test with customers as soon as possible in order to receive feedback and fix things based on that.

Service design at Kesko

The first keynote presentation was held by Kesko’s Lead Service Designer, Harri M. Nieminen. Even though the event focused on digital services, Harri wanted to point out that digitality is not a value in itself but rather a means of doing things. We should take advantage of the digital possibilities but not let digitality restrict us. It is also important to align the experiences in digital and physical channels as the customer won’t separate those two but will choose the channel that serves their current needs in the best possible way.

A project often starts with a request for an application. However, according to Harri, you should first create brilliant content and only then decide a suitable channel for it. A reponsive webpage can actually be a lot better option than an app – you don’t need to download anything or make room for another app in your already full phone. Especially when some content is needed only for a certain time period, you can do like Slush did and go for a webpage instead of an application.

The key factor in service design is a customer-centric way of thinking. The world is full of tools and methods but it doesn’t make sense to utilize them unless you sincerely want to make things better for the customer. If you are able to put yourself in the shoes of the customer you’ll also design the services more objectively. Often it also requires reading between the lines: if the customer requests a fix for a symptom X, it might actually be better to solve Y that is causing the symptom. Harri also presented us with the holy trinity of creating successful services: business for viability, technology for feasibility and design for desirability. If one of these viewpoints is missing, it will be difficult to succeed.

Like Maarit, also Harri brought up that solving problems is hard (and often takes a lot of money and resources), so you’d better be sure that you’re solving the right problem. It is important to empathize before defining anything, and you shouldn’t be scared of half-baked assignments – the assignment can and maybe even should change during the process. It is sometimes hard to prove the value of discovery to a non-designer, and it can be more difficult to get a 50k budget for investigating if something is worth investing into than the actual investment of 500k or more.

According to Harri, trying things out even just out of curiousity is always worth it. You will always learn something during the process.

Transformation at Yle

Mirette Kangas from Yle talked about their transformation towards a customer-centric, agile culture. Three key insights from her presentation were as follows:

  1. It is not enough to learn methods, tools and customs but you need to change yourself
  2. It is not enough for a leader to enable change but they need to promote it and lead from the front
  3. Culture of experimentation is not about senseless experiments but systematic doing

 

All in all the event was inspiring, and especially Harri’s presentation was a good overview of current trends and considerations in service design. I was also happy to notice that there wasn’t really anything totally new to me but I could feel myself as an equal expert in the audience, listening to a colleague.

More information and ideas:

https://digitaldiscovery.io/

Kesko’s customer community Kylä: https://k-kyla.fi/

Yle Lean Culture Toolkit: https://drive.google.com/file/d/1NkGRe-YACIcxextpkZLD-HTydZ1ifPyY/view

Dash 2018 Takeaways – How to Approach a Hackathon?

by Miikka Paakkinen

 

Last weekend I participated in the Dash 2018 design hackathon. During the event our team was challenged to design a new service business concept in less than 48 hours. The experience was wonderful, so I thought I’d share some key points on how to approach this type of a challenge.

IMG_5434

Point #1 – Keep the Pitch in Mind

 

  • To present a project, you’ll have to pitch it to your audience.

 

  • Having in mind what’s needed for a good pitch helps you define the key questions you need to answer during the project.

 

  • This helps you in choosing the way you work, the design tools you want to use, etc.

 

  • You might want to follow a design thinking model if a free-flowing way of working doesn’t feel natural to your group.

 

  • Here’s an example of a pitch structure that was suggested at Dash:

 

  1. Tag Line – The reason you exist for. Catch the interest of the judges.
  2. Problem – What is the problem you’re solving and who’s experiencing it?
  3. Solution – How are you solving the problem?
  4. Value – Why would someone give you money?
  5. Business Model – Who pays, how much, how often?
  6. Competitive Landscape – Map of competition + how are you different?
  7. Team – What’s your unfair advantage, why are you working on this problem?
  8. Traction – Why will it generate money, how much money per time unit?
  9. The Ask – What do you want from your audience?
  10. (Design Process) – This is specific to a design hackathon: you’ll need to be able to explain briefly how and why you got to your solution.

 

  • Points 2-5 are especially useful to keep in mind during the process. If you’re not solving a real problem that people face at a price they’re willing to pay while also generating profit, your project does not have real-world potential.

 

  • When it comes to the actual pitch, every second counts. If you’re lucky, you’ll have up to five minutes – use your time to deliver the essentials.

 

 

IMG_5446

Point #2 – Have Something Tangible to Show

 

  • It’s easier for your audience to understand your concept if you have something that in a very concrete way illustrates exactly how it works.

 

  • This could be, for example:
  •  
    1. Raw version of an app or software
    2. Interactive demo
    3. Animation of how your solution works
    4. Website
    5. Any sort of rapid prototype
    6. Video

 

  • This separates you from teams that have just a good concept or idea.

 

 

IMG_5451

Point #3 – Enjoy the Ride

 

  • Learn as much as you can from others.

 

  • Be open to new ideas and ways of working.

 

  • Don’t stress too much – you don’t have the time to achieve everything you want.

 

  • And most importantly: have fun with your new friends!

 

A big thank you to Aaltoes, the Dash crew and the challenge partners – see you again next year!

 

 

The author Miikka Paakkinen is an MBA student in Service Innovation and Design with a background in business management and information technology.

 


 

 

Practise, practise, practise.

Michihito Mizutani from Siili Solutions held a short introduction to service design as a part of Design Track in School of Startups. Instead of inclusive theory lesson, he kept the workshop more hands on. His work history is strongly related to user experience and service design. Currently he is facilitating co-creation design workshops in different subfields such as Internet of Things, augmented reality, service design processes.

I enjoyed about having the opportunity to get hands on experience on different kinds of tools. I believe that practise is important in order to learn design process methods and facilitating workshops related in the matter. I also felt more confident after the workshop. Mizutani used a climbing metaphor to explain design process. You have a starting point and a goal where you want to go. The process happens in between and there is the work.

 

IMG_3733.JPG

The content of the workshop was well presented. After forming groups it was time to find a problem, create outcome (tomorrow headline) and between we used tools to solve the problem and figured out ways to illustrate and test the ideas. The problem ideating was well thought: first we all thought by ourselves general problems in everyday life and wrote them down to post it notes. After that we collected problems, clustered them and used three votes each to determine the ones that would proceed in the process. Common problems that got most votes were chosen to be worked with in teams. The reason I think problem ideating was well implemented was the level of work. Having common grounds helps the team to work with the solution. General identification is important because the team needs to be on the same page. In that sense problem finding was a good excerise.

 

Using tomorrow headlines, SAP scenes and Marvel POP for prototyping was good practise because you need to know the tools you use. It migh have been good to have a little bit more introduction to the tools, since some of us were using them for the first time. In order to use tools efficiently in short period time would require a short introduction to principles so that working would be more smooth.

 

 

For me the workshop gave opportunity to also reflect my skills as a facilitator and a member of a team. For example, I noticed that my team members had a little difficulty in defining the tomorrow headline in unison and what kind of prototype we would create. I tried to focus staying neutral and help teammates to collaborate. Some people have hard time to give up their initial idea when collaborating and co-creating. Making sure everyone gets heard isn’t easy, and I wanted to practise that also. It might have been good if the facilitator would have time to see each groups working process more. There were eight teams of three people going through the design process, which is a lot to juggle alone.

That juggling leads me to my key learnings when facilitating service design process. This workshop reminded me of my other course, where I’m currently planning and later executing a workshop. Some of these thing scame from this workshop and others are ideas that originated later. Firstly: timing. Timing is crucial factor for me when facilitating a design workshop. Having adequate time for all the steps in process ensures good results. Plannig tables according to aquired team sizes ready before the workshop, helps people to set up in the right places right away, so suffling tables around would’t be nececcary. In the beginning the whole group also might need support when narrowing down the options. For example  clustering might be done by facilitator to make things smooth. Clear instructions on diffecent phases are important, and I believe it is handy to leave them on display when working starts. People tend to forget easily.

For me it makes sense, that when organizing a design workshop, it might be a good idea to have two persons present. Then you have two sets of eyes and hands to help teams to work efficiently. Some teams need help from the facilitator in order to move forward. Having two people facilitating gives opportunity to keep everything in order: clear instructions, support for the teams, timing, handing out supplies etc. Nothing is more frustrating than running out of time just before it is time to present your results to the other participants. That would leave the workshop incomplete.

More info and ideas:

https://www.siili.com

http://www.servicedesigntools.org/tools/14

https://experience.sap.com/designservices/approach/scenes

https://marvelapp.com/pop/

 

The author Siru Sirén is MBA student in Futures Studies and Customer-Oriented Services in Laurea UAS// Licenced social service professional