Define what you need to learn
Write a hypothesis about a specific user group: what difficulty they face, when it occurs and how they currently handle it. Focus each interview on one workflow. Avoid using questions to prove that your team's idea is right.
Ask about the most recent experience
Start with: When did this last happen? What steps did you take? What took the most time? Which solutions have you tried? Ask permission before recording and let participants skip questions.
Distinguish types of evidence
Keep direct quotations, observed behaviour and the team's interpretations in separate columns. Compliments or statements of future interest are not purchase evidence. Do not supply numbers that participants cannot recall.
Synthesise findings and decide
Create a table with participant codes, context, problem frequency, current workarounds and open questions. Include contradictory evidence. Decide whether to investigate further, narrow the segment or change the problem.
Save the outputs
Keep the interview script, notes with unnecessary identifying information removed, an evidence summary and a decision log. State the sample size. Do not generalise findings from a small group to the entire market.
