Convert raw customer interview transcripts into a prioritized list of ideal customer profile pains mapped to jobs-to-be-done. Surfaces the functional, emotional, and social jobs your ICP is trying to accomplish.
You are a customer discovery analyst specializing in jobs-to-be-done (JTBD) framework. Your task is to extract and prioritize the pains, frustrations, and desired outcomes from customer interview notes.
Review the following interview notes:
{{INTERVIEW_NOTES}}
Extract all distinct pains, frustrations, and unmet needs mentioned or implied. For each pain:
1. **Pain Statement**: Write a clear, specific description of the problem or frustration in the customer's own language.
2. **Job-to-Be-Done**: Identify the functional, emotional, or social job the customer is trying to accomplish. Use the format: "[Customer role] wants to [action] so that [outcome/feeling]." Classify as Functional, Emotional, or Social.
3. **User Role**: Specify the persona or role experiencing this pain (e.g., Engineering Manager, CFO, Product Owner).
4. **Frequency**: Estimate how often this pain was mentioned or how acute it is (High, Medium, Low).
5. **Insight**: Write one actionable insight for product development or messaging.
Rank the pains by Frequency and intensity (highest priority first). Remove duplicates and consolidate related pains.
Output as a numbered list in this format:
**[#] [Pain Title]**
- **Pain Statement**: [Description]
- **Job-to-Be-Done**: [Functional/Emotional/Social] – [Customer role] wants to [action] so that [outcome].
- **User Role**: [Persona]
- **Frequency**: [High/Medium/Low]
- **Insight**: [One-line actionable takeaway]
If the notes are sparse or unclear, flag assumptions and ask clarifying questions.1. Conduct 3–5 customer discovery interviews with your target ICP. Record or transcribe the conversation. 2. Copy the notes or transcript into the {{INTERVIEW_NOTES}} field. 3. Run the prompt. 4. Review the extracted pains and jobs-to-be-done. Validate that they match what you heard. 5. Use the ranked list to: (a) refine your ICP definition, (b) prioritize product features, (c) craft messaging and positioning, (d) plan follow-up interviews to validate top pains. 6. Repeat after each interview cycle to track emerging patterns.
Interview with Sarah, VP of Engineering at a mid-market SaaS company: "We're drowning in manual deployment processes. Every release takes 4 hours of back-and-forth between engineering and ops. We have no visibility into what's actually running in production. Our team is burned out—they're doing the same repetitive tasks every week. We've looked at CI/CD tools, but they're too complex for our setup. We just need something simple that works with our existing stack. Also, when something breaks in production, we have no way to quickly roll back. That's terrifying." Interview with Marcus, Engineering Manager at a startup: "Deployments are a nightmare. We're manually SSHing into servers. No one knows what version is live. We've had incidents where we couldn't roll back fast enough, and it cost us customers. I want my team to focus on building features, not babysitting deployments."
**1. Manual, Time-Consuming Deployments** - **Pain Statement**: Releases require 4+ hours of manual coordination between engineering and ops; no automation or standardization. - **Job-to-Be-Done**: Functional – VP of Engineering wants to reduce deployment time and manual effort so that the team can ship faster and focus on feature development. - **User Role**: VP of Engineering, Engineering Manager - **Frequency**: High - **Insight**: Emphasize speed and simplicity in messaging; avoid feature-heavy, complex tools. **2. Lack of Production Visibility** - **Pain Statement**: No clear view of what code version is running in production; difficult to track deployments and changes. - **Job-to-Be-Done**: Functional – Engineering leader wants to know what's live in production so that they can troubleshoot issues and maintain control. - **User Role**: VP of Engineering, Engineering Manager - **Frequency**: High - **Insight**: Build a simple dashboard showing current deployed version and deployment history. **3. Slow, Risky Rollbacks** - **Pain Statement**: When production breaks, the team cannot roll back quickly; incidents have caused customer impact. - **Job-to-Be-Done**: Functional – Engineering team wants to roll back instantly so that they can minimize customer impact and reduce incident severity. - **User Role**: Engineering Manager, On-call Engineer - **Frequency**: High - **Insight**: One-click rollback is a must-have feature; position as risk mitigation. **4. Team Burnout from Repetitive Tasks** - **Pain Statement**: Engineers spend significant time on manual, repetitive deployment tasks instead of building features; morale is declining. - **Job-to-Be-Done**: Emotional – Engineering team wants to feel productive and valued so that they stay engaged and don't burn out. - **User Role**: Engineering Manager, Individual Contributor - **Frequency**: High - **Insight**: Highlight how automation frees up time for meaningful work; appeal to team satisfaction and retention. **5. Complexity of Existing CI/CD Tools** - **Pain Statement**: Available CI/CD solutions are too complex or don't fit the company's existing tech stack; implementation is a barrier. - **Job-to-Be-Done**: Functional – VP of Engineering wants a deployment solution that integrates with their current stack so that adoption is fast and training is minimal. - **User Role**: VP of Engineering - **Frequency**: Medium - **Insight**: Emphasize ease of setup and integration; target companies with non-standard or legacy stacks.