## Setup
Interview type: customer
Interviewee: Priya, Director of Operations at a mid-market manufacturer
Date: not mentioned in transcript
Duration estimate: ~45 min (based on transcript length and pacing)

## Questions asked (in order)
Q1: "Can you walk me through how your team handles incident response today?"
Q2: "What's the most painful part of that workflow for you?"
Q3: "How did you end up choosing your current vendor?"
Q4: "If you could change one thing about your current process, what would it be?"
Q5: "Is there anything we haven't talked about that you wish I'd asked?"

## Key responses (paraphrased)

### Q1 — Current incident-response workflow
Response summary: A mix of manual escalation (Slack + email) and a paging tool for after-hours. Three on-call engineers rotate; a Director (Priya) is paged for sev-1s only. Average MTTR is 2-3 hours.
Notable quotes:
• "It works, in the sense that nothing's on fire most of the time. It does not work, in the sense that the same incidents keep coming back."

### Q2 — Pain points
Response summary: Repeated incidents from the same root causes; on-call engineers don't have time to do proper post-mortems, so patterns aren't learned. Tooling fragmentation forces context-switching during incidents.
Notable quotes:
• "We solve the same incident three times because the second engineer doesn't know the first engineer solved it last month."

### Q3 — Vendor selection
Response summary: Chose current vendor 2 years ago primarily for the integration with their existing monitoring stack. Knew it wasn't best-of-breed but was the best fit for their constraints at the time. Not enthusiastic about renewing.

### Q4 — If they could change one thing
Response summary: Knowledge propagation between on-call shifts. Wants something that surfaces "this exact pattern was solved last month, here's how" automatically.
Notable quotes:
• "I don't need another alert. I need a way to make the last time we solved this matter to the next person on-call."

### Q5 — Anything not covered
Response summary: Surfaced concern about audit + compliance — current tooling doesn't produce the incident records they need for ISO 27001 evidence; she has to manually compile them quarterly.

## Themes across the conversation
• Repeated work — multiple references to "solving the same thing twice" / "doing the same compilation work each quarter".
• Knowledge transfer gap — between shifts, between team members, between incidents.
• Tooling fragmentation — current stack is "fine in isolation, painful when in motion".

## Follow-ups to chase
• Audit / compliance workflow — only surfaced in Q5. Worth a deep-dive interview specifically on that.
• MTTR breakdown — she said 2-3 hours average but didn't segment by cause. Investigation vs fix vs comms?
• Decision-making power — she's a Director but didn't make the original vendor choice. Who did? Are they involved in renewal?

## Quality / coverage notes
Covered well: pain points, current workflow, ideal future state.
Left thin: budget / cost sensitivity, organisational decision-making, integration appetite.