Partizipative Forschungsansätze – auch für uns im Interaction Design relevant

nur kurz, da gerade frisch gehört und für gut befunden: ich habe gerade eine sehr spannende Podcastfolge von Technology Review über partizipative Forschung gehört. Lustigerweise habe ich darüber auch gerade viel Input in dem Modul Community Psychology bekommen. Dazu hoffentlich bald mal mehr. In der angesprochenen Folge geht es um einen Bereich, in dem die hierarchische Kluft zwischen Wissenschaftler*innen und Anwender*innen traditionell besonders hoch ist: der Medizin.

Allerdings ist das Feld der partizipativen Forschung oder des partizipativen Designs auch für den traditionllen Forschungszweig HCI sowie für Praktiker in dem Bereich (UX, Designer*innen, Entwickler*innen etc ) interessant und dreht ja in den einschlägigen Fachjournals schon länger thematisch die Runden. Viele Designentscheidungen beruhen ja (hoffentlich) auf einer Datengrundlage. Also ist auch die Frage wer entscheidet welche Daten überhaupt erhoben werden sehr sehr relevant für uns Praktiker die zB User Research betreiben. Reinhören lohnt sich. :)


Presenting design work

Even if you’ve been doing the job for a long time, design presentations are always a challenge. But presenting and thus communicating conceptual design is a very important aspect of our work.

Listen to this great interview with Donna Spencer on the UX podcast on the value of scenario based presentations.

„[…] pointing out things like real estate doesn’t help the audience get the flow in their head. It doesn’t help them understand what the user’s experience might be. And literally does draw attention to the things you might not want any comment on like, you know, colours and buttons and drop downs.“

I’ll look forward to reading her book.
Podcast episode

Conversations with Machines

Happy 2020 everybody! 🎉 New Year’s starting with the *big* questions and a great (ok, last years) podcast episode: What makes a human a human? What makes a machine a machine?

„Weizenbaum had programmed ELIZA to interact in the style of a psychotherapist and it was pretty convincing. It gave the illusion of empathy even though it was just simple code“

Listen here to „The ELIZA Effect“:

Also if you haven’t seen it already I highly recommend watching „Plug and Pray“
official Trailer:

Image source: Wikipedia

Use storytelling to build empathy for your users


This is a great podcast episode. I’ve once heard that in gym and I was like: yes! This is how to build „empathy“ or a feeling of an „ally“ who must solve a problem and you want to help her to do that.

„[…] Then, when we go in-home and study these users, we have this process, which is pretty fun, where we try and think of the user as a character. We put together something that we call a user profile/character. It’s a prompt where we would learn about the users and then create this character where, kind of like how writers would think of a character for their story, a user wants something, but they can’t get it. There’s something that’s blocking them, whether it’s a technical thing, environmental, or social. Then, now you have a user, which we would call a character, and we’d give them a name. They want something that they can’t get. These studies, we would bring the designers and the engineers with us. Data scientists, QA people, everybody would come and really understand this character. We would run a two-day workshop where the product is actually one where everybody on this team will take that character and map out a story about how we can take this user, apply what Wink has in terms of technical capabilities to get them all the way around to achieving what they want. That’s what we create as a product vision. Usually, we think of“ it as: What can Wink do in the next two years to help this user achieve that problem?

Listen here:

Get everyone aligned with journey mappings

„Can we change the conversation from trying to tweak and improve the existing steps that we have to challenge why we have any of these steps? Can we start again from day zero with this whole journey?“ […] That was the next most interesting conversation. It moved it away from suggests of UI changes to rethinking the experience and the behind the scenes calls that the system makes, and trying to understand why anything was there in the first place. The conversation became immediately incredibly more rich.“

– and : „It’s not a one and done thing“

From: Getting a Clue: Journey Mapping and the Rashomon Effect, a podcast by uie:

GDPR Cookie Consent mit Real Cookie Banner