jobs-to-be-done

Identify functional, social, and emotional jobs from customer research data.

142|16|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/amplitude/builder-skills --skill jobs-to-be-done-amplitude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/jobs-to-be-done
Command: npx skills add https://github.com/amplitude/builder-skills --skill jobs-to-be-done-amplitude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle to move beyond surface‑level feature requests and uncover the deeper functional, social, and emotional motivations that dictate why customers hire, switch, or abandon products.

Core Features & Use Cases

  • Job Identification: Breaks down customer input into functional, social, and emotional jobs.
  • Pain & Gain Mapping: Lists current pains, desired gains, and quantifiable metrics for each job.
  • Prioritization & Implications: Ranks jobs by intensity, frequency, and underservedness, then translates insights into concrete product strategy recommendations.
  • Use Case Example: Feed interview notes, churn data, or a list of feature requests and receive a structured report that tells you which underlying jobs to target for maximum impact.

Quick Start

Provide your product research and ask the skill to prioritize functional, social, and emotional jobs with associated pains, gains, and actionable recommendations.

Frequently Asked Questions about jobs-to-be-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I uncover customer motivations behind feature requests?

To uncover customer motivations, you can apply the jobs-to-be-done framework to feature request lists. This process identifies the underlying functional, social, and emotional jobs driving behavior, moving beyond surface-level requests to reveal true product strategy insights.

What is the jobs-to-be-done framework for product strategy?

The jobs-to-be-done framework is a method to identify the functional, social, and emotional tasks customers are trying to accomplish. It helps product teams understand why users hire or abandon products by analyzing pains, desired gains, and underserved motivations.

How do I analyze churn data to find why customers abandon products?

You can analyze churn data by processing it through a jobs-to-be-done analysis to identify unmet functional, social, or emotional jobs. This approach ranks jobs by intensity and underservedness to reveal the core motivations causing customer abandonment.

Can I use interview transcripts to map functional, social, and emotional jobs?

Yes, you can feed interview transcripts into this analysis to break down customer input. It generates a structured report mapping functional, social, and emotional jobs alongside current pains, desired gains, and quantifiable metrics for product strategy.

How do I prioritize product jobs by intensity and underservedness?

You prioritize product jobs by evaluating customer input to rank functional, social, and emotional jobs based on their frequency, intensity, and underservedness. This generates actionable product strategy recommendations targeting the highest impact areas.

When do I need to analyze emotional jobs for customer behavior?

You need to analyze emotional jobs when surface-level feature requests fail to explain customer churn or adoption. Applying this framework reveals hidden social and emotional motivations, translating them into concrete implications for product strategy.