Jobs To Be Done

What Is This?

Overview

Jobs To Be Done (JTBD) is a structured framework for understanding why customers choose products and services. Rather than focusing on demographic profiles or surface-level feature requests, JTBD investigates the underlying tasks, motivations, and desired outcomes that drive purchasing decisions. The framework organizes customer insights into three dimensions: functional jobs (practical tasks customers want to accomplish), social jobs (how customers want to be perceived by others), and emotional jobs (how customers want to feel during and after the experience).

The core premise of JTBD is that customers do not buy products. They hire products to get a job done. A person buying a drill does not want a drill. They want a hole in the wall. This distinction shifts product thinking away from features and toward outcomes, enabling teams to build solutions that address real motivations rather than assumed ones. When applied consistently, JTBD reduces the risk of building products that technically work but fail to resonate with actual customer needs.

JTBD integrates naturally into discovery, positioning, and messaging workflows. Product teams use it to validate ideas before committing engineering resources, while marketing teams use the language of jobs, pains, and gains to craft messaging that speaks directly to customer intent. The framework is compatible with tools like the Value Proposition Canvas and user story mapping.

Who Should Use This

• Product managers clarifying unmet needs before writing requirements or roadmap items
• UX researchers conducting discovery interviews and synthesizing qualitative findings
• Startup founders validating product ideas against real customer motivations
• Marketing strategists repositioning a product or refining messaging for a specific segment
• Business analysts documenting customer workflows and identifying friction points
• Growth teams diagnosing why activation or retention metrics are underperforming

Why Use It?

Problems It Solves

• Teams build features based on internal assumptions rather than verified customer motivations, leading to low adoption
• Product messaging describes capabilities instead of outcomes, failing to connect with customer intent
• Discovery interviews surface surface-level complaints without revealing the root cause of dissatisfaction
• Repositioning efforts lack a structured method for identifying which customer segment to target and why
• Roadmap prioritization becomes subjective when there is no shared language for describing customer value

Core Highlights

• Separates functional, social, and emotional dimensions of customer jobs for deeper insight
• Provides a repeatable interview and synthesis structure that scales across teams
• Produces artifacts that directly inform value proposition design and messaging frameworks
• Reduces ambiguity in product requirements by anchoring them to specific customer outcomes
• Bridges the gap between qualitative research and quantitative prioritization
• Compatible with agile workflows, OKR planning, and lean startup methodologies
• Applicable across B2B and B2C contexts without modification

How to Use It?

Basic Usage

A standard JTBD analysis produces a structured statement in the following format:

When [situation], I want to [motivation/job], so I can [expected outcome].

Example output from a discovery session with a project manager:

When managing multiple client projects simultaneously,
I want to see task dependencies and blockers in one view,
so I can proactively communicate delays before they escalate.

Pains and gains are documented alongside the job statement:

Pains:
- Switching between tools to get a complete status picture
- Missing blockers until they become critical issues

Gains:
- Confidence when presenting project status to stakeholders
- Reduced time spent in status update meetings

Specific Scenarios

Scenario 1: Pre-roadmap discovery. Before committing to a new feature, conduct five to eight JTBD interviews with target users. Synthesize the job statements, pains, and gains into a prioritized list. Use frequency and intensity of pains to rank which jobs are most underserved.

Scenario 2: Messaging audit. Map existing marketing copy against documented job statements. Identify gaps where the copy describes product capabilities but does not address the customer's expected outcome or emotional job.

Real-World Examples

A SaaS analytics company used JTBD interviews to discover that users hired their tool not to analyze data, but to justify decisions to their managers. This reframing shifted their onboarding flow to emphasize shareable reports over raw data exploration.

A mobile banking app applied JTBD to reduce churn, finding that users' primary emotional job was feeling financially in control, not tracking transactions. The team redesigned the home screen around budget summaries rather than transaction lists.

Important Notes

Requirements

• Access to at least five to eight customers or prospective customers for meaningful synthesis
• A structured interview guide that avoids leading questions and focuses on past behavior
• A synthesis tool such as a spreadsheet, Miro board, or Notion database to cluster findings
• Stakeholder alignment on using outcome-based language in requirements and roadmap documentation