For those of you following along, I’ve been conducting interviews to understand the life of a product manager.
I’ll be blogging about both how I conduct the research and the trends and patterns that come out of it.
One of the biggest challenges with qualitative research is capturing the overwhelming volume of data you collect throughout the process.
To Record or Not
I have often recommended that people not record their interviews.
It’s rare that an industry research team has the time (or the money) to do full transcriptions and recordings are rarely listened to. So it felt unnecessary.
It also often led to lazy habits when it came to sharing the research with the rest of the team. Too often, I see teams share links to the raw videos rather than synthesizing key learnings.
While these limitations and risks are still true, I’ve recently changed my mind. I now always record my interviews and recommend that others do the same.
When I don’t record, I try to take verbatim notes. I want to capture exactly what the participant said as it’s my only record.
But the challenge (as we’ll see in a later section), is that we can’t synthesize while taking verbatim notes. If I can’t synthesize, I can’t ask good follow-up questions.
So I started recording sessions as a way of easing the burden of verbatim note-taking and of increasing my ability to stay present with the participant.
Record your interview sessions to ease the burden of taking verbatim notes. – Tweet This
Audio vs. Video Recordings
I only record the audio of my interviews. I find that video cameras are intrusive. They interfere with the comfort of the participant. When the participant isn’t comfortable, they don’t share as much.
Audio recorders are less intrusive and are quickly forgotten. However, I never hide the fact that I’m recording the audio from the participant. This is unethical.
In some states, the law requires that you tell a participant that the session is being recorded. But don’t limit yourself to the law—do the right thing and always tell your participants if you are recording.
Video recorders can be intrusive during interviews, whereas audio recorders are quickly forgotten. – Tweet This
For in-person interviews, I use this flash-drive recorder. It’s good enough to pick up a conversation in a conference room or at someone’s house. I like that it’s small and easily forgotten. It also has a long battery life and large storage capacity, so I don’t have to worry about running out of either.
For virtual interviews, I use Call Recorder for Skype. It does mean that I run the risk of having connection issues, but it’s far easier to record a Skype session than to record a phone call, so I deal with the connection issues.
Handwritten vs. Typed Notes
Even though I record the session, I still take notes during the interview.
Before I started recording sessions, I always took notes on my computer. It was the only way that I could capture verbatim notes.
But this introduced a new problem. It’s hard to build rapport with a participant when you are hiding behind a laptop. The participant will often pause to give you time to type, which means they are thinking about you instead of thinking about what they have to say.
Now that I record my sessions, I don’t take verbatim notes and I’ve switched to taking notes with pen and paper.
Even with pen and paper, you have to work to maintain frequent eye contact. I find this to be much easier in person than on virtual calls, but I work to maintain frequent eye contact regardless of the medium.
Regardless of how you take notes, maintain frequent eye contact with your participant. – Tweet This
I like these large sketch books and use whichever pen I can get my hands on.
I find that writing gives me freedom that typing does not. I can use space to set topics apart, use arrows to connect related topics, and can star pivotal moments.
Handwriting Notes Might Help You Synthesize More than Typing
Pam Mueller, a recent PhD student in social psychology at Princeton, and Daniel Oppenheimer, psychology faculty at Princeton, compared the impact of taking notes with pen and paper vs. typing on a computer.
They found that students who handwrite their notes did better on conceptual questions—meaning they were better able to process the information.
Mueller and Oppenheimer speculated, however, that this result was not necessarily due to the medium itself, but due to the fact that students who typed their notes tended to capture verbatim notes. While they captured more content, they did less work to capture it during the note-taking process, and thus processed less of it.
Because handwriting is slower, you have to decide what to capture, and this forces you to process the information. – Tweet This
In a follow-up study, they tried to instruct computer-using students to not take verbatim notes, as a way of teasing apart the impact of the medium vs. the note-taking style, but unfortunately the participants did not heed this instruction.
If you want to learn more about Mueller and Oppenheimer’s work, check out this Freakonomics episode.
I’m skeptical that the difference in comprehension is due to typing vs. handwriting and suspect that it is more tied to verbatim vs. synthesis. Regardless, there are enough benefits to handwriting for me that in interviews, I’ll continue to handwrite.
Since I’m not capturing verbatim notes, let’s turn to what I am capturing.
Capture Enough to Ask Good Questions
I need to write to think. If you’ve ever had a conversation with me in a room with a whiteboard, odds are I started scribbling all over it. Seeing helps me synthesize.
During an interview, I try to capture the structure of what’s being said. My goal is to look for gaps or inconsistencies, as these are areas I want to follow up on.
For example, just last week, I was talking to a product manager who said he was one of five product managers. He then walked me through how the product team was organized—who worked on which products. But he only described four product areas.
Since I had captured that he was one of five product managers and because I was drawing the structure of his org chart as he was describing it to me, I could ask him what the fifth product manager did.
I would have never caught this if I hadn’t been writing notes.
Capture the structure of what is being said. Look for gaps and inconsistencies. – Tweet This
By the way, I do this during phone conversations, too. I need to see to synthesize. My brain wants to outline. I want to see the structure to understand. And I find it immensely useful.
Capture Enough to Reflect Back What You Heard
A key tenet of active listening is to reflect back to the person what you heard. This does two things. First, it shows that you are listening, and second, it allows the participant to clarify any misunderstandings.
I don’t have a good short-term memory. My brain likes to jump around. I’m constantly trying to connect the dots and that means that sometimes I get jumbled up between what I just heard and my own thoughts.
Capturing the structure of what I hear helps me to stay focused on your part of the conversation. It also gives me a handy outline to refer back to when reflecting back what I heard.
With a glance at my notes, I can quickly summarize at any point in the conversation, before jumping into the next topic. This might look something like, “You’ve told me about your current role, how you got there, and what you like about product management. Tell me what you aspire to. Do you have any career goals?” Of course, if I’m doing this in an interview, I’ll include some specific details, so that the participant knows that I’m listening.
I don’t do this just when I’m switching topics, but also when I need clarification on something. I’ll start with what I heard, what I expect that to mean, and then ask about the part that I’m confused about.
For example, I might say, “You mentioned earlier that you do a lot reading at home, almost every day, but several times since you’ve mentioned that you don’t have time for other activities. What’s different about reading?”
Again, this shows that I’m listening and it allows the participant to clarify what they mean, and it helps me to ensure that I’m not misinterpreting what they said.
Reflect back what you heard. It shows that you are listening and allows the participant to clarify. – Tweet This
Capture What Needs Follow Up
I also capture what I want to come back to later so that I don’t have to interrupt.
For example, I ask every product manager to tell me about how an idea goes from concept to launch. Suppose someone says, “Ideas can come from anywhere. We capture them all in a Google Spreadsheet and prioritize them. For the top ideas we start to do research…”
I already have a series of questions.
- What are some examples of where ideas come from?
- How do you prioritize them?
- Who prioritizes them?
- What do you mean by research?
But I don’t want to interrupt the participant. He or she is on a roll and I don’t want to interrupt their thought process.
Thankfully, I’m sketching this process as they describe it, so it’s easy for me to return to the places where I need more information.
For something that isn’t as linear, I might just jot down a note in the margins to remind myself to come back to it when there’s an appropriate time in the interview.
Don’t interrupt your participant. Capture your thoughts and come back to them later. – Tweet This
Highlight Key Moments (And Other Notations)
With time, I’ve developed my own style of notations.
I put notable phrases in quotations. If the participant mentions an aside, I usually put it in parentheses.
Some of this is just good punctuation, but it’s easy to get sloppy in note-taking, and it’s important to know what your own punctuation means.
Oftentimes, in the midst of an interview something jumps out at me. Maybe it’s particularly salient, or maybe it’s unique.
I don’t want to just capture that moment. I want to highlight it so that it doesn’t get lost in the shuffle.
I usually draw a star next to a key moment. Again, something that is easier to do with pen and paper than with computer.
I also make note of the time so that it’s easier for me to find it on the audio recording later.
I also note when something was said in response to a specific prompt.
For example, if I ask you about the people on your team and you say, “We have five developers and one QA person,” and then I respond with, “What about UX?”, I’m going to capture that like this to indicate that I had to prompt for UX.:
– 5 developers
– 1 QA
– UX? Oh yeah, 1 UX
It tells me that you might not consider UX as part of your team.
Develop your own notation to denote key moments in the interview. – Tweet This
Denote Source Material from Your Own Thoughts
The most important notation I use is to distinguish my own thoughts from what the person said.
For example, I talked about using parentheses to note an aside from the participant. I could just as easily use parentheses for my own thoughts. But I don’t want to confuse these.
Because I used to code, I use // to start my own thoughts. This makes it crystal clear what came from my head vs. what the participant said.
So take the following notes:
“we do all the right things”
customer interviews, co-creation exercises
it leads to no “tangible product output” // outcomes?
This is a snippet from an interview where the person is explaining that they do all the “right things” when it comes to product discovery, but that they get no “tangible product output.” I put that phrase in quotes because it surprised me. I was expecting him to say outcomes (captured in my comment), because product discovery is usually tied to outcomes not output.
Note the mix of summary (the second line) and exact quotes (the first and third lines).
Clearly denote source material (what the participant said) from your own thoughts and reactions. – Tweet This
Review and Extend Your Notes Immediately
It’s easy to misinterpret your notes later. So I always take a few minutes to review my notes as soon as possible after the interview and add any missing detail.
Sometimes my handwriting is illegible and I need to rewrite some words.
Sometimes I already can’t tell what I meant by my note and I’ll make a note to go back and listen to that part of the interview again.
I try to do this immediately after conducting an interview. But interviewing can be tiring, so sometimes I need a break and forget to do it right away.
However, I always do this before my next interview. I don’t want new content to interfere with the interpretation of my old notes.
Review your notes immediately following the interview. Add any missing detail. – Tweet This
Catalog Notes for Later Retrieval
Cataloging your source material is just as important as taking good notes.
I use a post-interview checklist to make sure that I can find everything I need later. It includes:
- Create a note in Evernote for this interview
- Add a photo of the participant
- Capture the three or four most salient things from the interview
- Add photos of handwritten notes to the note
- Add any screen grabs or other artifacts from the interview
- Add the audio file to the note
- Send the participant details about his or her incentive
It’s been a lot of fun doing primary research again. I’ve missed it. I’ll keep blogging about the process, and eventually about the results. To follow along, subscribe to the Product Talk mailing list.