Jobs to be Done Framework

⬢ TIER 2Soft

Medium

Salary impact

3 months

Time to learn

Medium

Difficulty

Careers

At a glance

Jobs to be Done (JTBD) is a framework for understanding why customers choose products. Instead of demographics or features, JTBD asks: what problem is the customer trying to solve? A customer isn't buying a drill; they're hiring it to make holes. JTBD leads to better product decisions, faster user adoption, and stronger positioning. Competency takes 2-3 months. Practitioners earn 15-20% premium in product/marketing roles.

What is Jobs to be Done Framework

Jobs to be Done (JTBD) is a framework for understanding customer motivation. The core insight: customers don't buy products; they hire them to get a job done. A customer doesn't buy a power drill; they hire it to make holes in walls. Understanding the job, not the drill, leads to better product, positioning, and customer fit. JTBD involves customer interviews to uncover the job (goal + desired outcome + constraints + context). Product decisions flow from job clarity.

🔧 TOOLS & ECOSYSTEM

Customer interviews (qualitative)Jobs mapping worksheetsOutcome importance/satisfaction matrixCompetitive landscape analysisProduct-market fit assessmentCustomer journey mappingPositioning frameworksMessaging testingVideo testimonial analysisJTBD templates

💰 Salary by region

Region	Junior	Mid	Senior
USA	$65k	$105k	$160k
UK	$50k	$80k	$125k
EU	$55k	$88k	$135k
CANADA	$68k	$108k	$165k

🎓 Certifications

Reforge Jobs to be Done Course Clayton Christensen's JTBD Workshop Intercom's JTBD Guide

🎯 Careers using Jobs to be Done Framework

Biotech Researcher

Blogger Substack Writer

Personal Stylist

Radio Cellular And Tower Equipment Installers And Repairers

❓ FAQ

What's the difference between Jobs to be Done and user personas?

Personas describe 'who' (demographic, psychographic). JTBD describes 'why' (job customer is trying to accomplish). Example: Persona = 'Sarah, 28, product manager, San Francisco'. Job = 'I need to schedule meetings without email chains'. Personas get stale; jobs are timeless (until customer need changes). Use both: persona describes decision-maker, job describes motivation.

How do I discover the 'job' a customer has?

Interview customers about a specific purchase. Ask: Why did you buy this? What were you doing before? What bothered you? When did you realize you needed a solution? Most important: listen for the goal, frustration, constraint. 'I was manually building spreadsheets' (outcome desired: automation). 'It was eating 5 hours/week' (constraint: time-limited).

Can a product have multiple jobs?

Yes. Slack's primary job: 'replace fragmented communication with centralized searchable history'. Secondary jobs: 'integrate my work tools', 'discover team news'. Products succeed when they nail primary job first, then expand to secondary jobs. Trying to address 5 jobs day 1 diffuses focus.

How do I use JTBD for positioning?

Position relative to jobs, not features. Instead of 'Slack: real-time chat', say 'Slack: replace fragmented communication'. Instead of 'zoom: HD video', say 'Zoom: run meetings without flying to office'. Customer job goes first; product is secondary.

Does JTBD work for B2B vs B2C?

Yes. B2B example: CFO's job = 'reduce accounting overhead'. B2C example: Parent's job = 'keep kids entertained on airplane'. Jobs are universal. B2B jobs tend to involve efficiency/cost; B2C involve convenience/enjoyment. Underlying framework is same.