Interviewing Users Blog

How to Uncover Compelling Insights

Posts written by Steve Portigal

  • Interviewing Users: Link Roundup

    Posted on

    interviewing-users

    It’s been well over a year since 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. If you haven’t already, get your copy here! And if you have, it would be great if you wrote a brief review on Amazon here.

    The Book

    Reviews

    Interviews

    Presentations

    Other

    Steve on Tuesday #TechHour

    Posted on

    I was on Kitchener’s 570 News technology radio program yesterday, invited by the great folks from Fluxible to speak very briefly about user research. I’m on about 15 minutes in. It starts with a rousing discussion of UX’s role, where companies are doing some unpleasant things in the name of “improving the user experience.”

    [audio: http://pmd.570news.com/podcasts/middayshow/Midday-Show_12-1_2014-08-19.mp3]

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

    Contextual research from a bygone era

    Posted on

    While listening to This American Life I learned about Roger Barker, a psych professor who turned the small Kansas town of Oskaloosa into a laboratory in the late 1940s.

    Barker was one of the most extraordinary — and least known — figures in the history of psychology. Shortly after he became chair of the KU psychology department in the late 1940s, he relocated his family to Oskaloosa to observe and gather data about the residents who lived in the town, population 725.

    At that time, psychological research was primarily done in laboratories. “It was the era of running rats through mazes to understand human behavior,” he said. “Barker said you won’t learn about any real human behavior in a laboratory. If psychologists want to understand human behavior in the real world, they must enter the real world.”

    More from this article

    Among Barker’s more unusual efforts was a 1951 paper he co-wrote under the title “One Boy’s Day.”

    It chronicled 14 hours in the life of a local boy with the pseudonym Raymond Birch . He was 7 when Raymond’s parents allowed the Midwest Psychological Field Station to record his every movement, according to Sabar’s book:

    7:00. Mrs. Birch said with pleasant casualness, ‘Raymond, wake up. …’
    7:01. Raymond picked up a sock and began tugging and pulling it on his left foot. …
    7:07. Raymond turned to his dresser and rummaged around among the things on it until he obtained a candy Easter egg for his dog.

    The notations, archived at KU, track Raymond on his walk to school. He finds a baseball bat in the grass and swings it, accidentally striking a flagpole.

    “This made a wonderful, hollow noise,” researchers wrote, “so he proceeded to hit the flagpole again.”

    Barker eschewed academic prose and wanted his charges to record any telling, prosaic detail.

    Through the 1950s, Oskaloosans grew accustomed to the sight of a child being shadowed by a note-scribbling adult. In published papers, this was the town of “Midwest,” in keeping with the scientific practice of shielding the identity of the subjects being examined.

    Barker’s work differed from other scholarly studies of places such as Muncie, Ind., (Middletown) and Candor, N.Y., (Springdale) in at least two ways.

    First, it focused less on class and politics and more on the relationships that made kids feel comfortable.

    Second, Barker’s family settled into Oskaloosa as a permanent home. Roger and Louise continued to live there until their deaths, Roger’s in 1990 at age 87 and Louise’s in 2009 at 102.

    While Barker used many methods, the part that struck me was his belief that simply documenting in exhaustive detail the ordinary activities throughout the day would somehow provide some additional insight. What would Barker have made of today’s era of personal analytics, data smog, quantified self and beyond?

    David’s War Story: Let it Bleed

    Posted on

    David Hoard is an interaction designer and here he shares his second story.

    Years ago we were re-designing a device to cool a patient’s blood during open heart surgery. This protects the body during the procedure. The client arranged for us to witness a heart operation, and we were pretty excited about that. My only concern was that I would faint from seeing blood.

    Research day came and we headed to a nearby hospital, prepared to be serious, professional researchers. A nurse helped us gown up and get ready. I was expecting the operating room to be a sober technical environment, and I saw that was true. The equipment was stainless steel; the walls and floor were blue-green tile. I anticipated that this would be an orderly collection of findings.

    But as soon as the surgery team started to come in, the vibe changed. The nurses chatted. The anesthesiologist joked. The patient, a man in his late fifties, was casually whisked in on a gurney.

    The nurses chatted with the patient as they put on the anesthesia mask and he drifted off to sleep. They slathered him with a brown antiseptic wash. It made his skin look like a basted turkey, and I thought “He’s just another piece of meat to them.”

    Then things really got started. The surgeon came in and straight away had the nurse hit the music. The sound of the Rolling Stones filled the O.R. The jokes and banter increased. The technician operating the blood cooling machines set to work and we tried to stay focused on that. But it was futile.

    When the patient was sufficiently chilled, they set to work with a powered saw and cut open his sternum. They were ripping a person’s body open, and they did it while talking about sport scores.

    They pried the chest cavity open and prepared for a bypass procedure. They took a vein from the man’s leg that would be used as a new artery for the heart. “How you doing back there?” came the question from the surgeon. “Good!” we replied, and I realized I wasn’t woozy at all. It was all too fascinating.

    It was at that moment that the most surprising thing happened. The surgeon said “How do you like this?” as he put his hand down in the chest and lifted the beating heart up and out. The music thumped, the heart pumped and the surgeon gave us a wicked grin. He knew full well he was holding the patient’s life in his hands. But at the same time, it was all in a days work for him. No big deal.

    After completing the bypass, they finished their work and stapled the man up. The surgeon cleaned up and zoomed off to something else important. Before we knew it our research session was over.

    As for our actual goal of observing blood-cooling machine, we did gather information about that, but the bigger lesson was in understanding the true nature of our users. We expected one-dimensional experts and we saw three-dimensional humans.

    My work on projects like this has taught me that experts are simply regular humans with a specialized job to do. Help them be smarter, help them be more successful. But don’t forget the human underneath that needs ease of learning, ease of use and help preventing errors. Humans don’t want to devote 100% of their brainpower to your product. They need to reserve some for cracking jokes and singing with the music.

    When your research goes in an unexpected direction, go with the flow and let the Stones play. You might learn something more meaningful than your original plan.

    Ari’s War Story: Chicken Run

    Posted on

    Ari Nave is Principal at The King’s Indian.

    My very first field research was in the north of Ghana along the Volta River north of Keta Krachi, trying to unpack the usage rights and other factors that enable the sustainable use of a common pool resource (in defiance of the tragedy of the commons).

    The research was hard. I was isolated, lonely, and physically drained. No one in the village spoke English. They spoke primarily Ewe https://en.wikipedia.org/wiki/Ewe_language and I was communicating through an interpreter. I had a feeling that I was missing a lot of nuance and detail with the interpreter and had several discussions with him about my concern.

    I was also sick as hell of eating fish stew with fufu or gari. For one thing, it was spicy as hell…so spicy that at every meal I had these convulsive hiccups. This hilarity may have endeared me to my host, but the diet was monotonous.

    I had spotted guinea fowl wondering around the village. I asked my host family about it and they just laughed and said they are wild animals.

    So I set my mind to catch one. That evening I watched as the guinea fowl hopped up a tree in the village. They used the same tree each night and seemed to jump up in a predictable pattern.

    The next evening I was prepared. I had a long string for my trap. I tied a slip knot on one end and placed the snare on a protrusion of the trunk that was chest-height, a pivotal step on their journey up the tree.

    The string was about 50 feet long and I ran the length straight to another tree that I hid behind.

    The folks in the village just laughed at me, which they seemed to do with great frequency. But I was determined. Patiently, I waited.

    As dusk fell the fowl made their way up the tree. When the third bird was on the spot I yanked as hard and fast as I could, while running in the opposite direction. And I had the little bastard. He flapped his wings and I reeled in the string, and soon had a plump guinea fowl in my hands. My host and all the other villagers came running at the commotion and now stood with jaw agape as I proudly displayed my bird.

    I asked my host to put the bird in a basket and put a big rock on top to keep him secure. It was too late to cook them so I ate my mind-alteringly hot fish stew but with a content mind, thinking about the fowl I was going to eat for dinner the next night.

    I woke up refreshed and optimistic. I gathered up my notebook, camera and tape recorder and headed out, but first stopped to gloat at my catch. To my dismay, it was gone. I shouted and my host came running over. “He has escaped in the night,” he explained by way of my interpreter. No way, I thought. The boulder was still on top of the basket. Someone stole my bird. When I voiced my opinion to him he shook his head and simply repeated the claim.

    That night, I executed my hunt again, with equal success. This time, a larger group came out to watch my escapades and were equally surprised both by my technique and success. Again, I place the bird in the basket, this time adding another large rock on top.

    The next morning, I woke with foreboding. I jumped out of bed and checked the basket. Stolen! I was pissed off. My host tried to placate me but I was having none of it. Arrogantly, I told him that I was going to complain to the head of the village. My host shook his head. He waved to me to follow him.

    We walked toward the center of the village where the elder lived, ironically where the guinea fowl often congregated. Before we reached his compound, my host swooped down and picked up a guinea fowl with his hands! Of course I had tried this many times when I first got the notion to eat one, but ended up running around like a fool. He lifted the wing of the fowl and I could see a colored ribbon. “Each bird is owned by a family,” he told me. “There are no wild birds here.”

    So I had captured a bird that was someone else’s property. I was confused as he had earlier told me they were wild animals. In the end, it turned out that he never thought I would be able to capture one, nor did he understand why I wanted to capture one. When I explained that, while I loved the fish stew, I wanted to expand my eating horizons, he laughed. “Just buy one from the neighbor and my daughter will cook it for you.”

    So that afternoon I bought a fat guinea fowl and the daughter of my host prepared the most delicious ground-nut stew with him. To this day, I crave that stew. It was unlike anything I had before and better than anything I could have imagined. Although, it was still insanely spicy.

    I felt a bit idiotic about the entire episode and it only reinforced to the folks in my village how odd I was. But it had one positive side-effect. People realized how little I understood about even the basics of their lives, and they began to be much less assumptive about my state of knowledge.

    Note: A similar recipe is here.

    Facing Your Fears: Approaching People For Research

    Posted on

    intercept

    I’ve always found intercepts – where researchers stop people on the street and ask them to participate in a quick study – to be challenging. (I also prefer to have longer interactions with people and even have them prepare for those research conversations, but that is a bit outside the point here). In Facing Your Fears: Approaching People For Research Carolyn Chandler breaks that challenge down into many pieces and addresses each of them. It’s a wonderful article because it gets deeply into the specifics and considers the mindset we bring to the activity and how to reframe that, in many different ways.

    Rejection is people’s number one fear when approaching strangers. Hearing no has always been difficult, whether it’s a polite no or an angry no followed by a rant. Either way, it stings. Your response to that sting, though, is what matters. How do you explain the rejection to yourself, and does your explanation help or hurt you?

    Martin Seligman, one of the originators of positive psychology, conducted a study in the ’70s that gives insight into the types of mindsets that make people feel helpless. Seligman found that those who exhibit long-term “learned helplessness” tend to view negative events as being personal, pervasive and permanent. In other words, if a person is rejected, they might rationalize that the rejection is a result of their own failing, that everyone else is likely to reject them as well, and that they can do nothing to lessen the likelihood of rejection.

    When you prepare to approach someone, consider instead that, if they say no, they aren’t really rejecting you, but rather rejecting your request. It’s not personal. Maybe they’re in the middle of something, or maybe they’re just not in the mood to talk. The rejection is fleeting, and the next person might be perfectly happy to participate.

  • Since Edmunds.com is an auto website we spend a lot of time hearing about how people shop for cars. A couple of years ago we ran a shop-along study where we conducted in-home interviews to both understand car shopping behavior and simultaneously screen people we may want to go with on test drives to dealerships. I always take someone else with me when running interviews – a designer, product manager, exec, etc. – so they get first-hand exposure to real car shoppers.

    This time I had the head of editorial with me. The Edmunds editorial team has a long-term fleet of cars so they can write about car ownership. My colleague tells me that he’ll drive and we’ll take one of the fleet cars. We meet in the lobby and he walks us over to a $100,000 red BMW. Not what I typically show up in to interview somebody who is probably shopping for a Honda.

    The interview is in Hollywood and although it’s only 10 miles from our office this is LA so we drive up Santa Monica Blvd for like an hour. We find the address and it’s not in the best part of Hollywood. There we are with this six-figure car. Eventually we find a parking spot that looks relatively safe and walk to the building.

    We use the callbox and are buzzed into the building. We look for the apartment and realize it’s in the basement. We’re greeted by our interviewee, a middle-aged guy who’s described on the screener as a self-employed writer (like much of the population of Hollywood). The apartment is the tiniest living space. It really looked more like a one-car garage. The air was stuffy, there was a unique odor that was somewhere between musty and dusty, there were no windows open and no A/C, with carpet that had maybe never been cleaned. I started to hope the allergy attack I was sure was coming happened after we were finished. The apartment was overstuffed with piles of papers (screenplays?), VHS tapes, and posters of independent movies (including one with a woman in bondage gear who we later discover is his wife). Although we’d normally want to capture anything descriptive of the scene, to avoid distracting the product team who would watch the video later we had to position the camera to keep the poster out of the shot.

    We’re chatting and after a few minutes our interviewee’s 35-year old wife comes out with a baby. The wife is some kind of Hungarian model (think of a European version of Gisele Bündchen). The guy turned out to be really nice, educated and articulate, but also clearly not at all someone likely to test drive a car at a dealership. Basically he hates cars, rides his bike everywhere, is trying to get off the grid but needs a car now that there’s a baby, and says he’ll buy some used car that’s parked on the street with a sign in the window.

    Was this interview all for naught? From the first moment through the end I wasn’t sure. You always learn something new, so even though this guy did not meet our criteria for people likely to buy a car at a dealership we certainly got exposure to a type of shopper we knew theoretically existed but hadn’t yet encountered (“the eccentric car hater”).

    I’ve seen homes like this (and worse) but after the interview we walked outside and my colleague couldn’t unload fast enough. He’d never seen a living situation like that. In rapid succession he declared (out of concern for our safety) “When we first walked in I though it was a trap – I was looking for a way out” but then (out of concern for the child’s health) repeated several times “They have a baby in there!!” And then he began to express his concern for my safety “Do you go on these interviews alone?…You take a guy with you, right?”

    After this emotional decompression, we jumped back into the ostentatious Beemer and drove down Santa Monica Blvd., away from the unknown of the ethnographer’s life to the predictable comfort of our office…until the next interview.