jobs-to-be-done

Identify functional, social, and emotional customer jobs, pains, and gains.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/Johnnnmai/100x-product-manager --skill jobs-to-be-done-johnnnmai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/Johnnnmai/100x-product-manager/tree/main/skills/jobs-to-be-done
Command: npx skills add https://github.com/Johnnnmai/100x-product-manager --skill jobs-to-be-done-johnnnmai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps you systematically understand the underlying reasons customers use products by identifying their functional, social, and emotional jobs, along with their associated pains and desired gains.

Core Features & Use Cases

  • Jobs-to-be-Done Framework: Apply a structured lens to uncover unmet needs and motivations.
  • Pain & Gain Identification: Detail customer challenges, costs, and what would delight them.
  • Use Case: Before building a new feature, use this Skill to interview potential users and map out the specific jobs they are trying to get done, ensuring your solution addresses real needs rather than assumptions.

Quick Start

Use the jobs-to-be-done skill to explore the functional, social, and emotional jobs for a new project management tool.

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 needs and motivations for product discovery?

To uncover customer needs and motivations, systematically explore customer context through the Jobs-to-be-Done framework, identifying functional, social, and emotional jobs alongside current alternatives to reveal unmet needs.

What is the Jobs-to-be-Done framework and how does it separate customer needs from solutions?

The Jobs-to-be-Done framework is a structured lens that separates underlying customer motivations from specific solutions by mapping functional, social, and emotional jobs, enabling product teams to address real user needs rather than assumptions.

How do I identify customer pains and desired gains during user research?

Identify customer pains and desired gains by detailing user challenges and costs through deep dives into customer context, mapping what frustrates them currently and what outcomes would delight them during product validation.

When do I need to map customer jobs for roadmap prioritization?

You need to map customer jobs for roadmap prioritization before building new features or validating solutions, ensuring development efforts address unmet functional, social, and emotional needs rather than internal assumptions.

Does this jobs-to-be-done analysis work for evaluating competitive landscapes and market alternatives?

Yes, jobs-to-be-done analysis works for evaluating competitive landscapes by requiring a deep dive into current alternatives customers use, uncovering unmet needs and mapping the competitive context surrounding their functional and emotional jobs.