Glossary/Jobs To Be Done (JTBD)
Product Management
2 min read
Share:

What is Jobs To Be Done (JTBD)?

TL;DR

Jobs To Be Done (JTBD) is a product strategy framework that focuses on the underlying 'job' a customer is trying to accomplish rather than the customer's demographics or the product's features.

Jobs To Be Done (JTBD) at a Glance

📂
Category: Product Management
⏱️
Read Time: 2 min
🔗
Related Terms: 4
FAQs Answered: 2
Checklist Items: 5
🧪
Quiz Questions: 6

📊 Key Metrics & Benchmarks

20-30%
Feature Adoption
Average percentage of features actively used
2-4 weeks
Time-to-Value
Optimal feature release to business impact
$50K-200K
Decision Cost
Cost of a wrong prioritization decision per quarter
30-50%
Zombie Features
Features with <5% monthly active usage
10x
Discovery ROI
Value of proper discovery vs. building wrong thing
40-60%
PRD Accuracy
Requirements that survive contact with users

Jobs To Be Done (JTBD) is a product strategy framework that focuses on the underlying 'job' a customer is trying to accomplish rather than the customer's demographics or the product's features. Developed by Clayton Christensen, Tony Ulwick, and Bob Moesta, JTBD reframes product decisions around customer needs.

The classic example: 'People don't want a quarter-inch drill. They want a quarter-inch hole.' JTBD goes further: they don't even want the hole — they want to hang a family photo to feel a sense of belonging.

JTBD interviews reveal the functional, emotional, and social dimensions of customer needs, leading to products that customers actually want rather than products that check feature boxes.

🌍 Where Is It Used?

Jobs To Be Done (JTBD) is leveraged heavily during the product discovery and strategic roadmapping phases of software development.

It is central to cross-functional alignment between engineering, design, and go-to-market teams to ensure R&D capital is deployed efficiently toward validated market motion.

👤 Who Uses It?

**Chief Product Officers (CPOs) & Product Leads** operationalize Jobs To Be Done (JTBD) to translate raw engineering velocity into measurable business outcomes.

**Founders** use this methodology to navigate the transition from a sales-led motion to a product-led growth (PLG) vector.

💡 Why It Matters

JTBD prevents the most common product failure: building features nobody wants. By understanding the job customers are hiring your product to do, you build solutions that deliver real value.

🛠️ How to Apply Jobs To Be Done (JTBD)

Step 1: Assess — Evaluate your organization's current relationship with Jobs To Be Done (JTBD). Where is it strong? Where are the gaps?

Step 2: Define Goals — Set specific, measurable targets for Jobs To Be Done (JTBD) improvement aligned with business outcomes.

Step 3: Build Plan — Create a phased implementation plan with clear milestones and ownership.

Step 4: Execute — Implement changes incrementally. Start with high-impact, low-risk improvements.

Step 5: Iterate — Measure results, learn from outcomes, and continuously refine your approach to Jobs To Be Done (JTBD).

Jobs To Be Done (JTBD) Checklist

📈 Jobs To Be Done (JTBD) Maturity Model

Where does your organization stand? Use this model to assess your current level and identify the next milestone.

1
Initial
14%
No formal Jobs To Be Done (JTBD) processes. Ad-hoc and inconsistent across the organization.
2
Developing
29%
Basic Jobs To Be Done (JTBD) practices adopted by some teams. Documentation exists but is incomplete.
3
Defined
43%
Jobs To Be Done (JTBD) processes standardized. Training available. Metrics established but not yet optimized.
4
Managed
57%
Jobs To Be Done (JTBD) measured with KPIs. Continuous improvement active. Cross-team consistency achieved.
5
Optimized
71%
Jobs To Be Done (JTBD) is a strategic advantage. Automated where possible. Data-driven decision making.
6
Leading
86%
Organization sets industry standards for Jobs To Be Done (JTBD). Published thought leadership and benchmarks.
7
Transformative
100%
Jobs To Be Done (JTBD) drives business model innovation. Competitive moat. External recognition and awards.

⚔️ Comparisons

Jobs To Be Done (JTBD) vs.Jobs To Be Done (JTBD) AdvantageOther Approach
Ad-Hoc ApproachJobs To Be Done (JTBD) provides structure, repeatability, and measurementAd-hoc requires zero upfront investment
Industry AlternativesJobs To Be Done (JTBD) is tailored to your specific organizational contextAlternatives may have larger community support
Doing NothingJobs To Be Done (JTBD) creates measurable, compounding improvementStatus quo requires zero effort or change management
Consultant-Led OnlyJobs To Be Done (JTBD) builds internal capability that scalesConsultants bring external perspective and benchmarks
Tool-Only SolutionJobs To Be Done (JTBD) combines process, culture, and measurementTools provide immediate automation without culture change
One-Time ProjectJobs To Be Done (JTBD) as ongoing practice delivers compounding returnsOne-time projects have clear scope and end date
🔄

How It Works

Visual Framework Diagram

┌──────────────────────────────────────────────────────────┐ │ Jobs To Be Done (JTBD) Framework │ ├──────────────────────────────────────────────────────────┤ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────────┐ │ │ │ Assess │───▶│ Plan │───▶│ Execute │ │ │ │ (Where?) │ │ (What?) │ │ (How?) │ │ │ └──────────┘ └──────────┘ └──────┬───────┘ │ │ │ │ │ ┌──────▼───────┐ │ │ ◀──── Iterate ◀────────────│ Measure │ │ │ │ (Results?) │ │ │ └──────────────┘ │ │ │ │ 📊 Define success metrics upfront │ │ 💰 Quantify impact in financial terms │ │ 📈 Report progress to stakeholders quarterly │ │ 🎯 Continuous improvement cycle │ └──────────────────────────────────────────────────────────┘

🚫 Common Mistakes to Avoid

1
Implementing Jobs To Be Done (JTBD) without executive sponsorship
⚠️ Consequence: Initiatives stall when competing with feature work for resources.
✅ Fix: Secure VP+ sponsor who can protect budget and prioritize the initiative.
2
Treating Jobs To Be Done (JTBD) as a one-time project instead of ongoing practice
⚠️ Consequence: Initial improvements erode within 2-3 quarters without sustained effort.
✅ Fix: Embed into regular rituals: quarterly reviews, team OKRs, and reporting cadence.
3
Not measuring Jobs To Be Done (JTBD) baseline before starting
⚠️ Consequence: Cannot demonstrate improvement. ROI narrative impossible to build.
✅ Fix: Spend the first 2 weeks establishing baseline measurements before any changes.
4
Copying another company's Jobs To Be Done (JTBD) approach without adaptation
⚠️ Consequence: Context mismatch leads to poor results and wasted effort.
✅ Fix: Use frameworks as starting points. Adapt to your team size, stage, and culture.

🏆 Best Practices

Start with a 90-day pilot of Jobs To Be Done (JTBD) in one team before rolling out
Impact: Validates approach, builds evidence, and creates internal champions.
Measure and report Jobs To Be Done (JTBD) impact in financial terms to leadership
Impact: Ensures continued investment and executive support for the initiative.
Create a Jobs To Be Done (JTBD) playbook documenting processes, tools, and decision frameworks
Impact: Enables consistency across teams and reduces onboarding time for new team members.
Schedule quarterly Jobs To Be Done (JTBD) reviews with cross-functional stakeholders
Impact: Maintains momentum, surfaces issues early, and keeps the initiative visible.
Invest in training and certification for Jobs To Be Done (JTBD) across the organization
Impact: Builds internal capability and reduces dependency on external consultants.

📊 Industry Benchmarks

How does your organization compare? Use these benchmarks to identify where you stand and where to invest.

IndustryMetricLowMedianElite
TechnologyJobs To Be Done (JTBD) AdoptionAd-hocStandardizedOptimized
Financial ServicesJobs To Be Done (JTBD) MaturityLevel 1-2Level 3Level 4-5
HealthcareJobs To Be Done (JTBD) ComplianceReactiveProactivePredictive
E-CommerceJobs To Be Done (JTBD) ROI<1x2-3x>5x

❓ Frequently Asked Questions

What is Jobs To Be Done?

JTBD is a product strategy framework that focuses on the underlying task or goal a customer is trying to accomplish, rather than on demographics or feature requests.

How do you do JTBD research?

Conduct 'switching interviews' — interview customers who recently switched to or from your product. Ask about the timeline of their decision, what triggered the switch, and what job they needed done.

🧠 Test Your Knowledge: Jobs To Be Done (JTBD)

Question 1 of 6

What is the first step in implementing Jobs To Be Done (JTBD)?

🔗 Related Terms

Need Expert Help?

Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.

Book Advisory Call →