Interviewing Guide for UX Dev.

Guide

Preparation

• Collect the demographics of each interviewee and include it in your report. (age, occupation, sex, interests that apply, geographic location, etc.)
• In some cases you will need a release form signed by each interviewee. This insures that the interviewee understands that there will be no compensation for their words or appearances in photography or video, and, that these will be made available for public viewing.
• Ask the interviewee if you will need to submit to a background check or sign a non-disclosure agreement. Get that done before you arrive.
• If you need specific technology: list that and send it to your interviewee. Going on sit e ahead of time is good practice if it is possible.
• If you may be working as a team, meet prior to the interview to set roles.... such as Interviewer, Note Taker, Photographer, Set Dresser (adjusts backgrounds for photographer), Food and Snacks.
• Follow Up Questions are sometimes required to insure that all of the information you desire is captured. Write down all of the potential follow up questions your team can generate. Try to build on one another’s ideas in order to flesh out meaningful subject areas.
• Identify themes or subject areas into which most questions fall; once you’ve identified the themes of your question-pool, determine the order that would allow the conversation to flow most naturally.
• Make sure that you leave room in your planning to ask plenty of “why?” questions, plenty of “tell me about the last time you _____?” questions, and plenty of questions that are directed at how the user FEELS.

Interviewing Guide

There should be very few questions asked because they tend to lead the conversation and do not allow the interviewee to set priorities. It's best to start with a very general question like "Tell me about some school field trips you went on?" When answering a general question like this, the person will often answer in priority of most important, second most important, etc. That is critical! They will also tell stories and bind together the things that matter to them through the connection between their stories.

Here are some dos and don'ts from the Stanford D School Bootcamp Guide:

• Ask why. Even when you think you know the answer, ask people why they do or say things. The answers will sometimes surprise you. A conversation started from any one question should continue on as long as there are still relevant "why?" questions.
• Encourage stories. Whether or not the stories people tell are true, they reveal how they think about the world. Ask questions that get people telling stories.
• Pay attention to nonverbal cues. Be aware of body language and emotions.
• Don’t be afraid of silence. Interviewers often feel the need to ask another question when there is a pause. If you allow for silence, a person can reflect on what they’ve just said and may reveal something deeper.
• Don’t suggest answers to your questions. Even if they pause before answering, don’t help them by suggesting an answer. This can unintentionally get people to say things that agree with your expectations.
• Ask questions neutrally. “What do you think about buying gifts for your spouse?” is a better question than “Don’t you think shopping is great?” because the first question doesn’t imply that there is a correct answer.
• Don’t ask binary questions. Binary questions can be answered in a word; you want to host a conversation built upon stories.

Photography

Each time you perform an interview or observational session, Take photos. These will be used for reference and potentially be used in some form as photography in the journey maps. Be sure to get shots that illustrate the story being told. Ask the interviewee to pose for you. Have some fun with it.

Q: What does your day look like?

A: Showed up to KCAD at 11:30

Worked on a writing assignment - printed out, ran late to class because of printer

Had a class at 12:30. Quick lunch at friends place at 5 lyon. Back at 3:30 to work on a digital modeling assignment. Class at 6:30 then IDSA meeting. stayed up late working on a Key shot rendering for vp3

Got to bed late - like 2:30

Q: What do you typically tote to KCAD?

A: Carries everything in his bag but plans to buy a separate case for his wacom tablet for Visual Production 3. His Samsonite backpack was heavy, worried pressure in his back pack may crush laptop

Teamwork

Here is an example of how a team can work together.

• Interviewer
  • Greets the interviewee.
  • Tell the interviewee what is going to happen and why.
  • Asks the questions.
  • Controls the pacing.
• Note Takers / Observers (could double as interviewer)
  • Be unobtrusive and quiet.
  • Type the notes into your computer or phone.
  • Include your own observations about how the subject is feeling in relationship to their stories.
• Photographer (could double as note taker)
  • Try to capture expressions that reflect the interviewees feeling toward the media
  • Ask the interviewee to pose for you. Have some fun with it.
  • Pay attention to composition, lighting and framing. Make them interesting.Photography Assistant (1)(optional)
  • Carry extra batteries
• Scout locations as soon as you arrive.
  • Make sure the "set" is dressed properly and change if needed.
  • Alter the lighting if needed.

Compilation

• Review all the notes and sort down to the most relevant.
• Group them by topic (not interviewee)
• Review all the photography together and sort down to the most relevant.
• Group them by topic (not interviewee)
• Identify the ones that could be used as reference for or in journey maps.
• Post Them for the entire team to reference during the design process.