interviewlisted

## CONTEXT LOADING Before generating an interview guide, load `product.local.md` for product context, personas, and research configuration. If not configured, ask the user for the research topic, target persona, and product context. ## INTERVIEW GUIDE WORKFLOW ### Interview Design Principles PRINCIPLE 1: BEHAVIOR OVER OPINION Ask what users DO, not what they THINK or WANT. "Walk me through the last time you did X" > "How important is X to you?" Behavior is evidence. Opinion is noise. PRINCIPLE 2: PAST OVER HYPOTHETICAL Ask about the past, not the future. "Tell me about the last time you exported a report" > "Would you use a bulk export feature?" Users are terrible at predicting their future behavior. They are excellent reporters of their past behavior. PRINCIPLE 3: PROBLEM BEFORE SOLUTION Do not mention your product, feature idea, or proposed solution in the first half of the interview. Explore the problem space fully before introducing any solution context. PRINCIPLE 4: SILENCE IS DATA When a user pauses or struggles to answer, do not fill the silence. The pause is often the most revealing moment in the interview. PRINCIPLE 5: "WHY" FIVE TIMES When a user says something interesting: ask why. Then why again. The surface answer is rarely the real answer. ### Interview Guide Structure (45-minute default) SEGMENT 1: OPENING (5 minutes) Purpose: build rapport; set expectations; get consent Script: "Thanks for taking the time to speak with me today. I'm [name], a produc