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

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

Example for: feedback from engineering managers complaining about weekly status meetings

Core Job Statement
When executive reviews approach, I want to compile a clear, defensible summary of team delivery, so I can protect my team from context-switching while proving our business value.

Functional Dimension
Aggregate commit data, ticket completion rates, and blocker summaries across multiple GitHub and Jira repositories into an executive-level summary without manual copying.

Emotional Dimension
Relieve the dread of appearing unprepared during leadership meetings; feel confident that engineering work is accurately recognized.

Social Dimension
Look like an organized, business-aligned manager in the eyes of executive peers and the VP of Engineering.

Forces of Progress

  • Push: Spending three hours every Sunday manually assembling slide decks for Monday morning status meetings.
  • Pull: The promise of an automated dashboard that translates code commits into business milestone milestones.
  • Anxiety: Worry that automated summaries will misrepresent complex technical roadblocks or make engineers feel micro-managed.
  • Habit: Reliance on ad-hoc Slack messages and personal spreadsheet tracking that leadership is already accustomed to viewing.

Key Product Opportunity
Build an automated weekly roll-up generator that drafts an editable executive briefing from Jira updates. Let the manager edit the narrative tone before sending, solving the anxiety of automated misrepresentation while saving hours of manual data assembly.

Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Product Management