Interview Goal & Context

Write one clear sentence defining what decision or hypothesis this interview is designed to inform.

Example: Understand why first-time users abandon the onboarding flow before completing their first project setup, to inform a redesign sprint in Q3.

Participant Profile

Describe the ideal respondent — their role, experience level, and any behavioral or demographic criteria that qualify them for this study.

Example: B2B SaaS product manager, 2–7 years of experience, has conducted at least 3 user interviews in the past 6 months, currently uses a competitor tool for research synthesis.

Core Discussion Questions

List 5–8 open-ended questions ordered from warm-up to deep-dive, each targeting a specific behavior, pain point, or mental model you want to explore.

Example: 1. Walk me through the last time you ran a round of user interviews — what did that process look like? 2. Where did things slow down or feel frustrating? 3. How do you currently decide which insights are worth acting on? 4. What does a good interview debrief look like for your team?

Post-Interview Synthesis Notes

Capture the top 3 themes, one standout quote, and a single recommended next action immediately after each session while it's fresh.

Example: Themes: analysis bottleneck, stakeholder communication friction, lack of tagging system. Standout quote: "I spend more time writing up the findings than actually doing the interviews." Next action: prototype a one-click tagging UI for recurring themes.

1. Define your research goal
   Before writing a single question, write one sentence in Section 1 that names the decision your team needs to make — this keeps every question focused and prevents scope creep during the session.
2. Recruit to your participant profile
   Use Section 2 to screen respondents before scheduling, ensuring every interview generates comparable, relevant data rather than noisy outliers.
3. Run the interview using your question guide
   Work through Section 3 in order but treat it as a conversation — probe on unexpected answers and use the questions as anchors, not a rigid script.
4. Fill in synthesis notes within 30 minutes
   Complete Section 4 immediately after each session so your pattern recognition is still active, then stack notes across all participants to identify recurring themes.

• Manual tagging across dozens of transcripts
  Reading every transcript and applying consistent theme tags by hand takes hours per study and introduces subjective bias that varies by who does the coding.
• Synthesis degrades as team size grows
  When multiple researchers each summarize their own sessions differently, cross-session patterns get missed and the final readout reflects whoever wrote the fastest, not the strongest signal.
• Insights arrive too late to influence decisions
  By the time notes are cleaned up, themes are identified, and a slide deck is assembled, the sprint planning meeting has already happened and the opportunity to act is gone — Usercall surfaces themes automatically the moment interviews are complete, so your team acts on evidence while it's still relevant.