jobs-to-be-done

Explore customer jobs, pains, and gains using the Jobs-to-be-Done framework.

24|3|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill jobs-to-be-done-prorise-cool
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/Prorise-cool/prorise-claude-skills/tree/main/.claude/skills/product-specialist/references/domains/product-management/jobs-to-be-done
Command: npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill jobs-to-be-done-prorise-cool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically uncover the underlying needs, pains, and gains that drive customer behavior, moving beyond surface-level feature requests.

Core Features & Use Cases

  • Structured JTBD Framework: Guides you through identifying functional, social, and emotional jobs customers need done.
  • Pain Point Identification: Helps uncover challenges, costliness, common mistakes, and unresolved problems.
  • Gain Discovery: Surfaces customer expectations, desired savings, adoption factors, and life improvements.
  • Use Case: When designing a new feature, use this Skill to interview potential users and deeply understand why they need a solution, ensuring your product addresses real motivations.

Quick Start

Use the jobs-to-be-done skill to explore the functional jobs, pains, and gains for a new mobile banking app.

Frequently Asked Questions about jobs-to-be-done

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

FAQPage Schema
What is the Jobs-to-be-Done framework and how does it uncover customer needs?▼

The Jobs-to-be-Done (JTBD) framework uncovers customer needs by separating the functional, social, and emotional jobs users need done from specific solutions. It reveals underlying motivations through structured interviews, moving beyond surface-level feature requests to validate product ideas.

How do I identify customer pain points during product discovery?▼

To identify customer pain points during product discovery, systematically analyze user challenges, costliness, common mistakes, and unresolved problems. This approach surfaces the underlying frustrations and expectations driving behavior, ensuring your product addresses real motivations rather than assumed solutions.

What is the best way to validate product ideas using user research?▼

The best way to validate product ideas using user research is to systematically explore customer jobs, pains, and gains. By conducting structured customer interviews focused on functional, social, and emotional factors, you can separate jobs from solutions and reveal unmet needs.

How do I structure customer interviews to find unmet needs and gains?▼

Structure customer interviews to find unmet needs and gains by exploring expectations, desired savings, adoption factors, and life improvements. This targeted questioning framework helps map the underlying motivations behind user behavior and effectively refine product messaging.

Can I use the JTBD framework for market research and messaging refinement?▼

Yes, you can use the JTBD framework for market research and messaging refinement. By systematically exploring functional, social, and emotional jobs alongside customer pains and gains, you separate jobs from solutions to reveal underlying motivations for targeted product discovery.

Why should I separate customer jobs from solutions during product discovery?▼

You should separate customer jobs from solutions during product discovery to systematically uncover the underlying needs driving customer behavior. This prevents over-reliance on surface-level feature requests and ensures your product addresses real functional, social, and emotional motivations.