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 source of 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 and 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 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!
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.
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.
Interviewing Users is now available. Get your copy here!
Hi! If you’ve read the book and found it beneficial, it would mean a lot if you would contribute a brief review on Amazon here.
It’s been eleven months Interviewing Users came out! Below is a roundup of links to various bits connected with the book. I’ll republish this occasionally with accumulated updates.
- Buy from Rosenfeld Media
- Buy from Amazon
- Foreword by Grant McCracken
- Excerpt from chapter 2
- The cover
- Images and diagrams
- Web Designers’ Review of Books
- How To Interview Your Users And Get Useful Feedback by Garrett Moon, Founder of TodayMade
- Reviews on Goodreads
- QRCA (Qualitative Research Consultants Association) Views Magazine (PDF)
- New: Reviews on Amazon
- Why You Should Read ‘Interviewing Users’ by Steve Portigal
- The eLearning Coach
- UX Magazine
- UX Matters
- UIE Book Corner (audio)
- 33 voices (audio) [summary slidedeck]
- UX Booth part 1, part 2
- Business 901 (audio)
- Huffington Post
- Ethnography Matters (and in Spanish)
- Interview with Denise Lee Yohn (audio)
- The User Experience podcast with Gerry Gaffney
- Steve speaks with Jared Spool about field research
- SpoolCast: Steve Portigal’s Interviewing Tips
- IXDA Los Angeles/LA UX Meetup – slides, video, alternate video, tweetstream
- recording of O’Reilly webinar #1
- recording of O’Reilly webinar #2
- New: a 5-minute talk about The Power of Silence
Steve was a guest on Mariposa Leadership’s Wise Talk, discussing Interviewing Users (recording).
Steve presented Building the muscles of innovators at uxWaterloo.
Credit card issuer Capital One isn’t shy about getting into customers’ faces. The company recently sent a contract update to cardholders that makes clear it can drop by any time it pleases. The update specifies that “we may contact you in any manner we choose” and that such contacts can include calls, emails, texts, faxes or a “personal visit.”
Yep, that’s how you get willing research participants – add it to the Terms of Service! Sure, I’m kidding; that’s not really what this article is about (it’s about the credit-card company claiming rights to repossession for non-payment). Still, this ups the creepy ante for visiting customers and makes the trust aspect of recruiting participants just that much harder.
From this article
WIRED: What innovation do you think is changing the most lives in the developing world?
MELINDA GATES: Human-centered design. Meeting people where they are and really taking their needs and feedback into account. When you let people participate in the design process, you find that they often have ingenious ideas about what would really help them. And it’s not a onetime thing; it’s an iterative process.
So great to see this.
Thanks to the folks from Fluxible who posted my 5-minute talk from last fall’s event. I talk about the power of silence in user research – and show just how hard it is to keep quiet when asking questions.