jobs-to-be-done
Structured framework for uncovering customer jobs, pains, and gains to validate product ideas and improve messaging.
- Breaks customer needs into three categories: functional jobs (tasks to complete), social jobs (how they want to be perceived), and emotional jobs (emotional states they seek or avoid)
- Identifies four pain types: challenges blocking progress, costliness in time/money/effort, common mistakes, and unresolved problems current solutions don't address
- Surfaces four gain types: expectations that exceed solutions, time/money/effort savings, adoption factors driving switching, and life improvements from easier workflows
- Includes step-by-step guidance for discovery, prioritization, and validation, plus anti-patterns to avoid (feature wishlists, demographics, generic statements)
Purpose
Systematically explore what customers are trying to accomplish (functional, social, emotional jobs), the pains they experience, and the gains they seek. Use this framework to uncover unmet needs, validate product ideas, and ensure your solution addresses real motivations—not just surface-level feature requests.
This is not a survey—it's a structured lens for understanding why customers "hire" your product and what would make them "fire" it.
Key Concepts
The Jobs-to-be-Done Framework
Influenced by Clayton Christensen and the Value Proposition Canvas (Osterwalder), JTBD breaks customer needs into three categories:
1. Customer Jobs:
- Functional jobs: Tasks customers need to perform (e.g., "send an invoice")
- Social jobs: How customers want to be perceived (e.g., "look professional to clients")
- Emotional jobs: Emotional states customers seek or avoid (e.g., "feel confident in my work")
2. Pains:
- Challenges: Obstacles customers face
- Costliness: What's too expensive in time, money, or effort
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1K