---
title: "Resource: Interview checklist"
source: 18F Guides
source_url: https://github.com/18F/guides
licence: CC0-1.0
domain: engineering
subdomain: 18f-guides
date_added: 2026-04-25
---

{% comment %}
Note that the permalink here does not include /resources/ so there's no indication where this page actually sits. This content is also very similar (or identical) to the Interview Checklist at https://guides.18f.gov/methods/interview-checklist/
{% endcomment %}

[Stakeholder and user interviews [18F design methods]](https://guides.18f.gov/methods/discover/stakeholder-and-user-interviews/) often progress through key moments: introductions lead to warm-up questions, which lead to topic-specific questions, activities, etc. This checklist outlines those key moments, and suggests things to do as you go through them. GSA Staff, please see this [Google Doc Template (GSA/TTS Access only)](https://docs.google.com/document/d/1zRA2EK9qZ5H_cM3Ki5xf6Gz72F6Ah6i0E87YpwHTC9A/edit)


## Pre-interview preparation
**Set aside 10 minutes** before the interview begins to help your team intentionally transition to an inquiring mindset, to clarify with your colleagues their respective roles, to check any technologies on which the interview will rely, etc.

### Make sure to {.guide-checklist}
- Remind your team of the purpose of the interview
- Establish clear roles for anyone who will join (for example, moderators, observers, notetakers, etc.).
- Confirm with teammates, especially remote ones, how they might ask questions during the interview (for example, in a Slack thread)
- Do a tech check: confirm that screen sharing, recording, etc. works
- Check receipt of a signed participant agreement ([example]({{ '/ux-guide/participant-agreement/' | url }}))
- Double-check any links, files, etc. that participants will need to evaluate (i.e., ensure that your concept, wireframes, or prototypes are available for testing)


## Introductions
**Spend 5 minutes** at the beginning of the interview to clarify with the participant the parameters of the interview, and to give them a chance to ask any logistics-related questions.

### Make sure to {.guide-checklist}
- Thank the participant for their time
- Introduce yourself, and anyone who is joining you
- Explain the purpose of your research
- Provide an overview of the shape of the interview, including any required logistics (for example, screen sharing)
- Confirm the expected length of the interview
- Confirm receipt of a signed participant agreement ([example]({{ '/ux-guide/participant-agreement/' | url }}))
- Explain
  - How you’ll take notes (for example, video recording).
  - How you’ll use any notes you take (for example, unattributed quotes)
- Ask the participant if they have questions at this time
- If the participant consents, turn on the recorder


## Warm-up / icebreaker
**Spend 5-10 minutes** establishing the cadence for the interview as a conversation rather than a stilted back and forth. Help the participant feel comfortable, and focus on gaining important context for the body of the interview.

### Make sure to {.guide-checklist}
- Be polite; you’re a guest in the participant’s world
- Give the participant your full attention (You can signal this by making eye contact, asking follow up questions, etc. Be aware that taking notes, especially on a laptop, can distract from the conversation itself)
- Ask open-ended questions that will give you relevant information and help you form a better understanding of who this person is
- Understand the degree to which this person is comfortable talking about themselves and their work, and at what speed. Be mindful and respectful of anything the participant is uncomfortable talking about
- Give the participant time to respond; don’t be afraid of awkward pauses
- Ask for a “tour”: note any organizations, tools, rituals, or processes that affect your participant’s perspective
- Start broad (“So to start, could you tell us how you got into this line of work?” or “What’s a day in your work-life like?”), and then slowly direct the interview toward any planned activities (“Could you share your screen and show me how you do that?”) or topic-specific questions (“How often do you file TPS reports?”)


## Activities or topic-specific questions
**Spend 25 minutes** exploring the topics or leading the participant through the activities (for example, screen sharing) the research was designed around.

### Make sure to {.guide-checklist}
- Know what you want to learn
- Demonstrate genuine curiosity
- Let the conversation flow naturally, and try and get the participant to tell stories — yes, stories — related to the things you’re studying
- Default to open-ended questions such as “Tell me about a time… ”, “Can you explain…”, “Why do you think…”
- Ask clarifying questions or ask your interviewee to repeat themselves if you missed something
- Use a diverse array of question types, such as context-gathering questions (asking about sequences of events, relationships, etc.), clarification questions, and comparison/contrasting questions
- Use transition phrases to help participants understand when you are moving between parts of the interview (“let’s go back to something you said before”)
- Test your own assumptions and understandings without asking leading questions. Ask “how” and “why” multiple times, and give the participant sufficient time to think about their answers
- Note the exact words and phrases people use. Don’t correct them, even their pronunciation, if you think they’re wrong
- Look people in the eye and give positive affirmations. Lean forward. Say things like “Wow,” or “Oh, interesting!” (when those reactions genuinely occur to you, of course)
- If you ask the participant to share their screen
  - Caution them to close anything they don't want recorded beforehand
  - Assure them that there are no wrong answers — you’re testing the design, not them
  - Ask them to think out loud
  - Ask “How would you expect this to work?”
- Periodically check to see if your teammates have any questions


## Wrap-up
**Spend 5 minutes** thanking the participant, communicating any next steps, and giving the participant a chance to ask any questions they might have.

### Make sure to {.guide-checklist}
- Thank the participant for their time and reiterate the value of their contributions
- Ask the participant if there was anything they think we missed or that they would like to add
- Ask if it would be okay to contact them again with any follow up questions
- Provide any agreed-upon compensation
- Turn off the recorder
- If possible, ensure the participant that they will receive a copy of what you’ve found during the research (so they know what happened with the input they gave)
- If desired, ask them who else you might talk to (fun fact: this is called snowball sampling)

## Post-interview activities
Once the interview is complete, **spend 15 minutes** completing a post-interview debrief. Tend to any post-interview logistics.

### Make sure to {.guide-checklist}
- If you’ve recorded the interview: Move any recordings from your Google Drive to the project folder
- Engage the team in a post-interview debrief ([example]({{ '/ux-guide/interview-debrief/' | url }})) to discuss surprises and reflect on what you heard
- Consider updating the interview guide based on this interview
- If you promised the participant any follow-up communications, identify who will send them and when
- Optional: Update your study contact list


## Contributors
Amy Ashida, Julia Lindpaintner, Andrew Maier, Victor Udoewa

## References
_Interviewing Users_ by Steve Portigal; _Practical Ethnography_ by Sam Ladner
