A two-day course in design thinking taught me that a team is more than a group of people and that in our aim to reach our goals, failure can be a positive thing.
During a two-day master class on Design Thinking, under the guidance of Katja Tschimmel, creator of the Mindshake Design Thinking Model Evolution 6², we worked in teams, going through the service design process and creating a service concept that would fit under the title “Studying at Laurea”. As a roadmap, we had the steps of the E6² model.
After a brief introduction, we were thrown head-first in at the deep end. Even though we had just met, in order to succeed we had to work as a team as if we had always done so. But why wouldn’t we be able to pull this off? After all, our instructors seemed to have full confidence in our ability to swim. Or maybe that wasn’t even relevant.
Failure is a part of the process.
“Failure can be a positive thing,” Katja Tschimmel told us at the very start, echoing what she had written on the subject in her research paper Design Thinking as an effective Toolkit for Innovation: “failure is a part of the process”. It is integral to design thinking. Failures early on will save money, as it will push the process onto a better track. Accepting uncertainty and ambiguity is vital for a design thinker. You work with what you’ve got and it’s ok if you can’t swim.
Learning to swim
When one team member runs out of ideas, another one takes over. One idea sparks another and at times it’s like fireworks! This is how teamwork soon started to feel.
As I’m a project manager by profession, I’m very familiar with teamwork and I embrace it. But teamwork has never felt quite like this. It was not just a bunch of individuals forming a group, it was a group effort to which each individual contributed. It was impossible to remember afterwards which part of the path was whose idea. We had the strength of the team. We had each other’s immediate feedback and no one was in it alone. You succeed as a team, you fail as a team.
Teamwork has never felt quite like this!
The process was full of doubt, excitement, frustration, concentration. And occasional panic. The panic being created mostly by the deadline looming on the imminent horizon. But the timeframe was essential, as was the framework given by the Evolution 6² model. Otherwise, we might not have been able to stay focused. We could have easily stayed in the ideation phase forever, just a group of people discussing ideas. Moving on turned us from a group of people into a team.
A starting point, a roadmap and a goal
Design thinking is not just a way of thinking, it’s a toolkit. Within the framework, we had a varied selection of tools at our disposal. As the steps of the Evolution 6² model followed one another in rapid succession, so did the tools: media research, intent statement, mood board, user journey map, brainwriting, insight clustering, visual business model, rapid prototyping, feedback and others, in seemingly random order.
In his book, Change by Design, Tim Brown talks about the convergent and divergent phases of design thinking. They are about creating a sea of possibilities from which to select the most fitting through convergent thinking. We need both of these to reach our goals, “movement from the divergent phase that is the source of our inspiration to the convergent phase that is the roadmap to our solutions”.
Create a sea of possibilities, then make a choice.
This idea of convergent and divergent thinking became most clear to me in the brainwriting phase of the process. In our version of this boosted type of brainstorming each member of the group took a bunch of post-it notes and sat down for a moment to write ideas around the concept we were creating, one on each note. After this, we grouped the ideas and discussed them together. So first there was silent divergence, to maximise the flow of ideas, then convergence in a group. The brainwriting phase of the process came just at the right moment, when we had an idea of the direction, but not an idea of the outcome. Afterwards, we could point to something and say: this is it, this is what we should develop further.
Brainwriting was one of the many tools with which we finally reached the goal. After the two intensive days my mind was full of ideas, creative energy and most importantly, a new way of thinking, design thinking. I had learned to swim. We had done it, as a team!
I felt excatly same that team work has never felt like this. It highlighted that team work is really important in design thinking process and it is important that team has different people and different experts
I agree. Actually I feel that we could use the power of teams a lot more. One can understand many more use cases and perspectives just by talking about a subject at hand. Also a little play with legos or some drawing never hurts anyone, right?
This blog sum up the importance of team work and realization in DT course very well. I am of the same opinion that team work has never felt like this. Every opinion was considered, all ideas were discussed, all possibilities have been analysed before deciding the idea to work as a team. Addition of drawing and using legos in DT makes it more fun to do the tasks. overall well summerised blog.
“An Individual Plays The Game but Team wins the Championship!”. Indeed, it was really a great team work that all of us did who participated in the contact sessions. These contact sessions also revealed the fact that the design is not an individual’s task where one can do in isolation, but instead it is a team work, sharing ideas,thoughts, opinions and discussions
I agree that “Failure is a part of the process.” That is why while designing a new service model, it is important to test your hypotheses, taking frequent and early feedback and act upon it.
I like that many of us felt on the same page about teamwork. Learning to find a team balance feels like one one the hardest parts but also, if achieved, the biggest takeaway. What I like about team dynamics the most is that you may test different roles when working in different teams, and learn so much from yourself and from the others 🙂
I loved the visuals and the style of writing in your post, I would guess you’ve done blogging before! Brainwriting indeed is a good tool and especially doing it first by yourself and then building up on the ideas of others. But do you remember when we even took a step further: after the brainwriting itself we randomly took post-its from different clusters and tried to make up new ideas based on those totally different concepts. That was both fun, hard and insightful, wasn’t it?
Thanks for sharing, really interesting read on your experience with DT!
After having completed the two intensive days of practical design thinking, I could not agree with you more on the collaboration point. The fact that Design Thinking and in this case, brainwriting produces “everyone’s” idea rather than “someone’s” gives a natural buy-in from the entire team and makes it very enjoyable to expand the idea further. The multi-disciplinary team really adds value here and makes the ideas very fluent and flexible.