interview-snapshotlisted

# Interview Snapshot One interview in, one structured markdown file out. Nothing else. This is the atomic unit of customer research. Before ever running cross-interview synthesis, every interview passes through here first. Teresa Torres calls out combining synthesis steps as her single biggest anti-pattern; this skill is the guardrail that prevents it. ## When to use - Granola just synced a discovery interview transcript into the vault - A recorded interview was transcribed via Fireflies, Otter, etc. - You took live interview notes and want them structured - You are about to run discovery-process Phase 4 (synthesis) and have raw transcripts ## When NOT to use - For internal team meetings (use post-meeting skill) - For usability tests (they need a different schema: task-by-task observations) - For NPS surveys or quantitative survey data - To synthesize multiple interviews at once. **Never.** Run this skill once per interview, THEN move to cross-interview synthesis. ## The schema (five sections, in order) ### 1. Experience Map A timeline of what the participant actually did. First-person, past tense, concrete. Not what they *would* do or what they *usually* do, but what happened the most recent time. Structure: ```markdown **Trigger:** What kicked off the experience **First action:** Literal first thing they did **Next steps:** Ordered sequence of what followed **Tools / people touched:** Every app, site, document, human involved **Outcome:** Did they finish? Abandon