Bringing user studies in form of a game
Wohoooo! First exam successfully finished, a lot of preparation, hours of user study evangelism and a lot of insights into importance of user studies into design and innovation. I understand more and more that role of designer is becoming more than just creating a beautiful wrap. It is also something about discovering a user need, smartly involving them in creation process and giving a soul to the concept that could be fulfilled.
I would like to share my ideas of how I imagine user studies brought into the team that is not familiar with such. Most of the insights came from our Participatory innovation project with Dimaps, but is not limited to it.
I have used this synopsis in exam presentation, and of course – this is not a complete scientific paper, just a guide for myself. The basic idea is to make studying users as a game (3rd poster) and building knowledge about them from the methods applied that would be made in attractive form.
In quick glance – it is important to challenge teams’ assumptions about users that at least I have met quite often. In my opinion these assumptions lower the motivation of conducting user studies. Of course, there always can be good guesses, but studying users I think is actually a safer way of making innovation that would be accepted on the market.
- assumption - innovation comes from a lone genius instead out of a team-work. What some people want is an approval of their own assumptions and ideas about what the user needs. And some persons whose assumptions about users are strong, could consider other conflicting ideas as a threat for them.
- assumption - users know what they want, and instead of extensive user studies, it is better just to ask them – interpret material 1:1.
- assumption – functionality of product is more important than user studies and users are going to adapt proposed functionality if it will be “good”.
- assumption - industry standards and specifications are more important than user studies.
More about challenging these assumptions in a synopsis. That’s at least from my own experience 
design, Innovation, user research, user studies, users
It’s time to write about our last study project together with Innovation&Business students. Writing is such a good way how to save an experience for a reference with a high level of details The course we are taking now is called Participatory innovation - one of major user-driven innovation approaches. And this project was a complementary part to lectures and discussions. We had to 1) find a real company, 2) get an innovation project and 3) fulfill it with methods that we were taught of. Project was meant to be 8 weeks long.
To sum up we worked together with company Dimaps on their route planning software. We made reasonable ideas and scenarios which were based on our user studies. However, there were some problems with inner motivation, communication (different mind-sets) and in our case – presentation of results. There is one of the scenarios above that we have extracted from user studies and co-ideation events.
In this project I have learned:
- There is need for one leader in a team, who helps to make teams’ decisions in a way that everyone is satisfied. That person needs to be charismatic, knowledgeable, a fast-thinker (to evaluate everyones’ ideas) and has to have a big picture in a head. Such person must not lose composure. By having many people who are willing to be only the one leader, makes decision making hard. Having bad or no leader in team, results in low motivation and incoherent group-work,
- Team of 7 was too big in our case, just 4 people were working,
- Presentation is how others perceive your work, good presentation means for most that group had a good work together (and it is mostly true),
- It is important to be quick in capturing and interpretating data. Aim could be having 1-2 user-study videos per day, that would help to better and faster co-ideate in a group leading to richer ideas,
- There is little value in having a shallow look at user-study materials (videos) and interpreting them 1:1. Question why they are doing that is important in order to create good user-centered products and services.
- I have got a good insight in participatory innovation,
- Consensus based group-work is slower, especially if members have different mind-sets, that requires to discuss each decision.
I am going into more details below.
Read the rest of this entry
geographic information systems, gis, Participatory innovation, route planning system, scenarios, software, Teamwork, users
