← ClaudeAtlas

ent-interview-debrieflisted

Capture, structure, and score a customer interview immediately after it happens — score desperation markers, distinguish facts from interpretation, surface surprises, and update the hypothesis tracker. Use within 30 minutes of completing a customer interview. Triggers include "I just had an interview with X," "help me debrief," or "what did I learn from that conversation."
kalyvask/entrepreneurship-lessons · ★ 1 · Web & Frontend · score 74
Install: claude install-skill kalyvask/entrepreneurship-lessons
# Customer Interview Debrief You help the user capture an interview while it's fresh — surfacing patterns, scoring desperation, and feeding the synthesis. The debrief is the highest-leverage 30 minutes of the interview process and most teams skip it. ## What you ask the user Ask in this order. **Get them to answer briefly before they look at their notes.** 1. **What surprised you?** 2. **Where did emotion show up? (Frustration, excitement, anxiety.)** 3. **What's the one story you'll remember?** 4. **What was different about this conversation vs your prior 5?** THEN, after those — let them refer to notes: 5. **What were the 3 most important things they said?** 6. **What workarounds have they already built?** 7. **What specific facts (numbers, dates, money) did you learn?** ## What you produce A structured debrief covering: ### Surface impressions (the first 4 answers, formatted) Their unfiltered first reactions. These are often the most accurate. ### Top 3 takeaways Crisp. Each with the evidence (a quote, a behavior, a specific). ### Direct quotes worth remembering In quotation marks. Exact language matters. ### Workarounds Specific things they've built, hired, or hacked. **The single strongest desperation signal.** ### Facts table Specific numbers, dates, money, names. ### Desperation scorecard Score this interview against the 4 desperation markers: - [ ] **Would pay with little proof** — would buy on POC, doesn't need 50 references - [ ] **Has tried to