Separate user behaviors from user opinions in interviews
Sort raw user interview transcripts into verifiable past actions and unverified personal opinions to prevent product bias.
Prompt
Act as a rigorous user research analyst. Analyze interview notes to separate verifiable past actions from subjective opinions, hypothetical promises, and polite compliments. Rules: Classify every user statement as either Observed Past Behavior or Stated User Opinion; explain the product design risk of treating each opinion as a concrete user requirement; do not assume future behavior based solely on an opinion. Output format: 1. Behavioral Breakdown Table (Columns: Quote or Note, Classification, Evidence Level, Product Risk if Misinterpreted), 2. Confirmed Usability Insights (bullet list of actual behaviors), 3. Research Gaps to Validate (bullet list of questions to confirm opinions with data). The interview notes are below:Example output
Paste this prompt into Claude, ChatGPT, or Gemini, then paste your raw user interview text at the bottom. Follow up by asking the model to suggest two analytics events to track in production to verify the stated opinions.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build a customer interview repository summary
Condense customer interviews into clean, standardized summaries ready to store in product research repositories.
Spot leading questions in customer interview transcripts
Audit your customer interview notes to find biased questions, analyze how they skewed responses, and get neutral rewrites.
Extract customer pain points from call notes
Turn unstructured user interview notes into prioritized product pain points, real customer quotes, and actionable recommendations.
Turn discovery call notes into testable product hypotheses
Transform messy customer feedback into structured, prioritized product hypotheses with clear validation tests and metrics.
Separate firm commitments from casual suggestions
Sort meeting talk into binding commitments and casual brainstorm ideas so task ownership stays unambiguous. Use this whenever raw notes or transcripts blur intent.
Turn raw workshop ideas into prioritized next steps
Organize unstructured brainstorming notes into clear action clusters categorized by operational impact and implementation effort.
- Assign clear single owners to workshop actions
- Design a structured off-site workshop run of show
- Draft a board pre-read memo for async sign-off
- Draft a confidential skip-level action plan
- Establish strict rules to separate brainstorming from critique
- Run a silent brainwriting agenda that includes everyone