jobs-to-be-done

Structure customer jobs, pains, and gains using the JTBD template.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/sicktastic/skill-issue --skill jobs-to-be-done-sicktastic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/sicktastic/skill-issue/tree/main/product-management/jobs-to-be-done
Command: npx skills add https://github.com/sicktastic/skill-issue --skill jobs-to-be-done-sicktastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague wish lists into a structured Jobs-to-be-Done analysis so you can understand the functional, social, and emotional jobs customers are trying to complete, as well as the pains and gains shaping their decisions.

Core Features & Use Cases

  • JTBD Framework Overview: Clearly separates customer jobs from solutions and highlights the pains, costs, mistakes, and unmet needs preventing progress.
  • Prioritization Guidance: Encourages ranking pains by intensity and differentiating must-have gains from nice-to-haves to inform discovery, product-market fit work, and messaging.
  • Use Case: Use this Skill when validating a new feature to ensure it targets a real job, addresses acute pains, and delivers tangible gains for the chosen persona.

Quick Start

Guide me through documenting functional, social, and emotional customer jobs plus associated pains and gains for a new discovery interview.

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 structure customer jobs, pains, and gains during product discovery?

The best way to document functional, social, and emotional jobs is using the JTBD template, which separates customer jobs from solutions and highlights the pains, costs, mistakes, and unmet needs preventing progress.

What are functional, social, and emotional jobs in user research?

Functional, social, and emotional jobs in user research represent the distinct tasks and psychological motivations customers are trying to complete, which shape their product decisions and highlight unmet needs.

How do I prioritize customer pains and gains for product strategy?

You prioritize customer pains and gains for product strategy by ranking pains by intensity and differentiating must-have gains from nice-to-haves to inform discovery, product-market fit work, and messaging.

When do I need a jobs-to-be-done framework for product management?

You need a jobs-to-be-done framework for product management during discovery, competitive analysis, and messaging planning sessions to ensure new features target real customer jobs, address acute pains, and deliver tangible gains.

Can I use jobs-to-be-done analysis for validating a new feature?

Yes, you can use jobs-to-be-done analysis for validating a new feature to ensure it targets a real job, addresses acute pains, and delivers tangible gains for your chosen persona.

How to turn vague user research wish lists into a structured analysis?

To turn vague user research wish lists into a structured analysis, apply the JTBD template to categorize functional, social, and emotional jobs while mapping the associated pains and gains shaping customer decisions.