Can you engineer empathy (as part of learning to code)?

images

From Engineering Empathy [Re/code]

Dev Bootcamp, an intensive nine-week coding program in San Francisco’s South of Market district, offers a unique “Engineering Empathy” curriculum. About 30 students stood in pairs and spoke to their partners simultaneously: You don’t respond to email fast enough. Why are you checking Twitter — nothing important happens there. You’re too old to be here. You’re faking it. You don’t know how to develop. You have no career. You’re the worst pair partner. Your accent makes you hard to understand. You’ll never get a programming job.

When the cacophony finally subsided, many of the would-be programmers were in tears. Some were holding hands. One man sat down and put his head in his hands. “My superego runs on a disappointment platform,” he said to the room.

The culture of tech (male-dominated, sexist, entitled and so on) has become even more visible as of late. Even the parodies of Silicon Valley, such as HBO’s Silicon Valley, face criticism for not being inclusive enough.

So I’m a bit stuck on how to parse this particular example. Of course it’s good that people are given the chance to develop empathy! I’ve been teaching designers about presence and mindfulness (and will be doing so again later this year at UX Australia). Perhaps it’s just how the writer took something earnest and presented it out of context, thereby making it look ridiculous (in other words, like a scene from Silicon Valley

online pharmacy periactin for sale with best prices today in the USA

).

I suppose things can be both wonderfully beneficial and hilariously ridiculous at the same time (see rock music or romance, for example). I’ve taught a lot of workshops where you if walked in without context you’d wonder what the hell is going on. I feel trepidation (because I can’t tell how whether this is authentic or just a put-on) but I really want to recognize this as a good thing.

Erik’s War Story: (Don’t) Go Toward The Light

online pharmacy clenbuterol no prescription with best prices today in the USA

Erik Moses is the Director of Research and Insights at Product Development Technologies in Lake Zurich, IL.

Not long ago I was on a project where we were tasked with understanding current practices in BioPharma labs. Overall the program was a huge success and we uncovered critical new insights for our client, which is always rewarding. But that is not what this story is about. This story is about my iPad.

As a researcher, I admit to having a bad memory. I am a dedicated note taker. I love my notes and can’t do much without them. A few months before this, I had begun using the iPad as my main tool for data capture in the field, moving on from my old friend the pen and paper.

For one of our site visits we were in the Midwest at a notable university lab. We were there for the day, courtesy of our client’s long-standing relationship with this lab. That is to say, we were welcome guests. Part of the process we were observing involved a lab technician processing images in a darkroom. At one point during our visit, the PI (Principal Investigator), who was our client’s main point of contact and with whom they had the relationship, invited our group into the darkroom to understand how the process continued in this environment. Of course, I brought my iPad.

Our group piled into a cramped university darkroom to find not only the PI, but also a few other technicians from the lab processing portions of their project. It was dark in the darkroom, so the only thing I could see was the soft red glow of dark room-specific lights.

The PI began the demonstration, while we tried not to impede the movements of everyone else in the darkroom. At some point, our participant said something very interesting that caught my attention. I thought “Hey, this is a must-have insight I need to remember!” and so I opened the cover of my iPad.

Immediately, I hear a technician behind me exclaim “Wha-what? Oh, great!” While I now recall hearing this comment just like it was yesterday, at the time I was so focused on capturing this important piece of information, I did not put it together that the technician was referring to the blunder I had just made.

After noticing a tremendously bright light in this room of black, only then did my mind stitch together the visual information of the bright light with the auditory cue of the mumbled comment. In a matter of seconds I realized what I had done.

While afterwards the PI ignored the incident and the session continued for the rest of the day without another incident, I felt horrible and was flustered for some time. Reflecting on it today, I still feel flustered. I like to imagine that I didn’t mess up that technician’s experiment that much, perhaps only by hours but given what I know about that group and the process, in my heart I know I ruined at least two days’ worth of hard, time- and event-specific work.

Because of this incident I am now very careful in the field, perhaps to the point of being overcautious, often times wrapping my arms around my iPad to physically tell myself to be mindful of my actions. Learn from my experience: remember, don’t (immediately) go toward the light!

This Week @ Portigal

Hope things are as sunny where you are as they are here…

  • I spent the first half of today helping our client with a synthesis session. We made it through two transcripts and they’ve got another 11 to do on their own, so they have some work ahead. But it was really fun, really interesting and quite valuable in pulling out some themes and opportunities. I’ll meet with them next to help with a presentation and run a design workshop afterwards, probably in a few weeks.
  • If you missed last week’s well-received 32 Awesomely Practical UX Tips virtual seminar, you can still get the recordings. Use the code 32UXTIPS for 32% off!
  • I’ve got a great slate of catch-up calls and lunches this week. It’s something I find so helpful and enjoyable and I’m glad to have the chance to do it right now as projects wind down and others are still winding up.
  • Ten years gone: From April 2004 – Academics examine Wal-Mart for clues to our culture, Reuters consent.
  • What we’re consuming: Ferrell’s Donuts, Fargo, a rant about design, Fastball’s The Way, improv as life advice.

Listen to Steve on the UX Discovery Session podcast

DS-LOGO-FB-Final-300px

I was interviewed by Gerard Dolan for the UX Discovery Session podcast. In 30 minutes we spoke about my twisted educational career path, the Interviewing Users book, some products and services I’m struck by and my fantasy of putting on a UX conference devoted to soft skills. You can listen to the interview below, or here (where Gerard has included a nice set of footnote-links).

To download the audio Right-Click and Save As… (Windows) or Ctrl-Click (Mac).

Be a rock star, just like…Spider-Man?

spidey rock star

This designed-by-committee advertainment highlights three benefits, speed, agility, reliability – the third probably not top-of-mind when we think of the web-slinger. And as if this cross-promotion for the USPS Priority Mail and Spider-Man (well, Spider-Man 2) wasn’t ridiculous enough, these qualities will make you a rock star. Just like the US Postal Service. Or Spidey.

What?

That’s it. “Rock star” is officially over. Meaningless. We’ve known this for a while, but this is too far and we must all agree to stop it immediately.

Listen to Steve on Wise Talk

Insights

online pharmacy https://www.archtis.com/wp-content/uploads/1606/80/12.html with best prices today in the USA

I was interviewed by Sue Bethanis for Mariposa Leadership’s Wise Talk show. In an episode titled The Art of Interviewing Users we talked about how to see and notice in a different way, being aware of our own filters and biases, and constantly rediscovering what the problem you are trying to solve really is. You can listen to the interview below, or at Wise Talk.

To download the audio Right-Click and Save As… (Windows) or Ctrl-Click (Mac).

This Week @ Portigal

Greetings to all!

  • We’re onto the final tiny steps to wrap up this long project. Last week’s sessions highlighted some real challenges in moving innovation through the organization and I know that my direct clients have some more work to do. I’ve put together an iteration of our final presentation that hopefully will help everyone understand the path we’ve gone down – the questions we were tasked with and the ways our research addressed those. For now, I’m waiting to hear that this is satisfactory for concluding this phase of work.
  • I’ve got my single transcript in hand will be combing through it this week in preparation for facilitating for a new client next week.
  • We’ve got another new War Story! Check out Seeing Ourselves As Others May See Us. I hope to have more soon (hint hint hint).
  • On Friday I recorded a conversation with Gerard Dolan for his UX Discovery Session podcast and before the weekend was up he had posted it! Check out our 30-minute chat.
  • More to listen to: the recording from last week’s Wise Talk about Interviewing Users is here.
  • This week I’ll be one of several speakers at Rosenfeld Media’s day-long virtual event, 32 Awesomely Practical UX Tips. Use the code STEVE for 20% off!
  • I’m taking time this week to drive down to meet with a design team we worked a lot with about 4 years ago and see if there are opportunities to collaborate again. I’m also having lunch with a few different colleagues around the area to catch up and share ideas and stories.
  • Ten years gone: From April 2004 – Astro Boy currency, Wacky warning labels.
  • What we’re consuming: Philz Coffee (suburban version), Aaron Sorkin’s QSR drama, renovacation, Chinatown Sartorialist, Silicon Valley, focus group horror, dog treats (inadverently!).

War Story: Seeing Ourselves As Others May See Us

Here we break with tradition and present a story anonymously, to mitigate against mortification of those involved.

Twenty something and fresh out of my MA program I obtained a little consulting job which I completed from afar. The company mailed me a video camera and interview guide and sent me out to discover what people think of dinner food. I was to recruit people who would participate in a video recorded dinner we share and an after-dinner interview. I was instructed to send footage back to the company with the camera along with notes and analysis.

My first interview was with a man about my age who ate convenience foods. He was shy and awkward with me as I was with him. When I got there I set up the tripod and attempted to build rapport beyond our obvious discomfort. In an effort to focus only on him as he opened a can of soup and poured it into a casserole dish I spent very little time adjusting the equipment. He prepared soup-in-a-dish dinner and we ate together and then I went through what was left of the interview content. Perfect recruit for “convenience food eater,” and I was off.

Later at home I looked back at the video to make sure my notes are correct and to complete a partial transcript. To my surprise and immense embarrassment I realized that I set the camera up so that the composition includes only one thing in the foreground completely obscuring the participant’s head. It was a close-up view of my right breast – interrupted only occasionally by my arm each time I raised the fork. The entire dinner and interview video contained nothing more than this view. I had never met the employer or the team in person but I reluctantly packaged up the camera and my notes and sent them away without a word. Later they mention that their view of this video inspired quite a few laughs around the office. Oops.

This Week @ Portigal

The weeketh beginneth, all!

Lindsay’s War Story: Sexism in the City

Lindsay Moore is an independent design research and strategy consultant from Colorado.

We were in New York City, on day four of a three-week fieldwork trip. We had had some bumpy interviews the first few days, including a participant who clammed up because her husband was in the room, another who wasn’t comfortable showing us any of the software processes she had been recruited to show us, and a third with whom the conversation was like Mr. Toad’s Wild Ride, with us hanging on for dear life. But I was finally starting to settle in to the interview guide and was feeling positive about what we were learning. Plus we were getting a great apartment tour of Manhattan!

We were accompanied on each interview by a rotating member of the client team so that they could all experience the research firsthand, and this day was our first with a particular team member. Our morning interview had gone fairly well, but I could tell our client partner was having some trouble staying in the background, as she was used to more actively managing her interactions with customers.

We walked in the door for our afternoon interview, and I made some small talk, saying something like “How is your day going so far?” to our participant, who was an older gentleman. He answered that it was going much better now that we three pretty girls were there, but that it would be even better if we didn’t have clothes on. I experienced a shocked moment of “Did he really just said that???” and took a sidelong glance at my client to see her reaction. She had one of those impenetrable customer service masks of politeness on her face. I tried to shake off the comment and proceeded into the interview.

For the first 30 minutes, I found myself utterly unable to manage the flow with the participant, who would physically turn towards the client to answer my questions, and then turn back to me and say “You understand?” The interviews were about financial behavior, and he made it very clear that he thought I wouldn’t be able to follow what he was saying. Meanwhile, in an effort to be polite, engaged and responsive with her customer, my client was unintentionally making it worse. I realized I needed to gain some kind of credibility and after the umpteenth “I don’t know if you would understand” I told him that I do have some financial background and that I was following just fine. After that I was much better able to lead the interview and he engaged directly with me. Still, for another hour and a half he continued to condescend and make inappropriate/sexist comments (The number of times he suggested we “girls” go shopping at Bloomingdales after the interview? Five. What he wanted us to buy? Blouses.)

After leaving the interview I was hopping mad and said to my client and my colleague that I couldn’t believe what we had just experienced. They agreed but felt like we had still been able to uncover great information in the interview. They also thought that sometimes older men are just “like that” and that I shouldn’t let it get to me. I was bothered but decided to let it go. The interview had been uncomfortable but not unsafe, and the client was pleased with what we had learned. As an interviewer, wasn’t I supposed to be able to set my own emotions aside?

When revisiting the transcripts and coding the interview data, it really became clear to me that I was not overreacting to what we experienced. It was blatantly bad. Still, what should we have done? When I’ve related the story to other friends and colleagues, they’ve said that we should have left the home after the initial no-clothes comment. I want to agree on principle, but I also know that if I never allow myself to experience something uncomfortable, I’ll miss out on the richness and depth that is a part of this kind of work. What I do know is that it’s okay to share and talk about our own emotional responses to difficult research situations and that doing so is an important part of self-care for researchers. In the future, I will also make sure to have a plan in place with my fieldwork partners for when — and how — to end an interview, so that it’s not a process we need to invent in the moment.

Series

About Steve