Analyze customer feedback using Jobs to Be Done
Extract functional, emotional, and social customer drivers from raw user feedback. Use this to separate true user motivations from reactionary feature requests.
You getCore Job Statement, functional Dimension and emotional Dimension
Prompt
Act as a customer research lead. Analyze the user feedback, interview transcripts, or survey responses below using the Jobs-to-be-Done framework.
- Disregard specific feature suggestions and extract the underlying progress the customer is trying to make.
- Separate functional jobs from emotional anxieties and social motivations.
- Identify the current push factors away from existing solutions and pull factors toward new alternatives.
- List the habits or anxieties holding the customer back from adopting a change.
Output format:
- Core Job Statement: When [situation], I want to [motivation], so I can [expected outcome]
- Functional Dimension: The practical task to complete
- Emotional Dimension: How the user wants to feel or avoid feeling
- Social Dimension: How the user wants to be perceived by peers or leaders
- Forces of Progress: Four bullet points covering Push, Pull, Anxiety, and Habit
- Key Product Opportunity: 2-3 sentences on the highest-leverage product bet
Here is the customer feedback:Example output
Paste interview transcripts, customer support complaints, or NPS comments into ChatGPT, Claude, or Gemini. Follow up by asking the model to draft three distinct product hypotheses based on the identified forces of progress.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Reframe a feature request into a core user problem
Break down prescriptive feature requests into underlying user motivations, workflow bottlenecks, and testable problem statements.
Draft Multi-Tier SaaS Product Packaging and Feature Matrix
Generate a clear, competitive feature matrix for your SaaS product that aligns tiered capabilities with specific user upgrade triggers.
Draft a working-backwards press release and FAQ
Write an Amazon-style press release and hard FAQ to clarify customer value and address tough technical questions before writing code.
Draft a Zero-to-One Product Discovery Experiment Card
Generates a structured, one-page test card with a falsifiable hypothesis, cheap validation test, and numeric kill threshold for new features.
Write a Customer Interview Script That Validates a Problem with Past-Behavior Questions
Get a 30-minute problem-discovery interview script with past-behavior questions, two follow-up probes each, banned-question rewrites and evidence signals.
Classify onboarding drop-offs into cognitive and value friction
Audit user onboarding funnels by separating confusion from missing value motivation. Use it to prioritize growth experiments and UX redesigns.