JTBD Method Overview & Core Concepts

JTBD Method Overview & Core Concepts

Overview

This section introduces the JTBD (Jobs To Be Done) methodology and its application in IoT solution sales and product design. After completing this section, you will be able to:

• Understand the origins, core assumptions, and mental model of JTBD
• Distinguish between functional, emotional, and social jobs
• Use Job Statements and Job Maps to structure customer needs
• Apply JTBD thinking to requirements discovery and solution positioning in IoT scenarios

Prerequisites

Before starting this section, ensure:

• Completed all previous 21 chapters with a holistic understanding of IoT systems
• Basic business thinking and understanding of B2B sales processes
• Experience with customer needs or pre-sales communication (preferred)

Key Concepts

What is JTBD?

JTBD (Jobs To Be Done) is a needs-insight methodology proposed by Clayton Christensen (Harvard Business School professor). Its core idea is:

Customers don’t buy products; they “hire” products to accomplish a job.

Traditional marketing focuses on “who the customer is” (demographics), while JTBD focuses on “what the customer wants to accomplish” (the job). This shift in perspective helps IoT practitioners:

• Break free from feature-list thinking and understand real customer motivations
• Discover unmet latent needs
• Build more persuasive solution narratives

Core Assumptions of JTBD

Assumption	Description
Jobs are stable	People’s fundamental needs (jobs) remain constant over time; what changes are the ways to fulfill them
Jobs are context-dependent	The same person has different jobs in different contexts
Jobs are independent of demographics	Age, gender, and job title are not the primary determinants of needs
Customers define success as “progress”	The completion criterion is “my life/work is better because of this”

Example: A factory manager hires an IoT monitoring system not because he is “a 45-year-old male manufacturing executive,” but because he needs to “stay on top of production line status in real-time, even while traveling, and respond to anomalies immediately.”

Three Types of Jobs

JTBD categorizes customer needs into three dimensions:

1. Functional Job

   • Specific, measurable operations the customer needs to accomplish
   • Example: Monitor workshop temperature/humidity in real-time, remotely restart abnormal equipment, count daily production output

2. Emotional Job

   • Psychological feelings the customer wants while accomplishing the job
   • Personal dimension: Reduce anxiety, gain a sense of control, feel confident
   • Example: The factory manager wants to “sleep peacefully” while traveling, without worrying about the production line

3. Social Job

   • The image the customer wants to project to others
   • Example: The factory manager wants his boss to see him as “well-managed and embracing digitalization”

💡 Key Point for IoT Practitioners: In pre-sales communication, functional jobs are easy to understand, but what truly moves decision-makers are often the emotional and social jobs.

Job Statement

A Job Statement is a structured description of a JTBD, formatted as:

When [situation/trigger], I want to [motivation/goal], so I can [expected outcome]

IoT Scenario Examples:

Scenario	Job Statement
Factory Environment Monitoring	When workshop temperature/humidity is abnormal, I want to receive an immediate alert, so I can take action before equipment is damaged
Asset Tracking	When expensive equipment is moved, I want to locate it in real-time, so I can quickly recover it and hold someone accountable
Energy Management	When monthly electricity exceeds budget, I want to identify high-consumption equipment, so I can develop an energy-saving plan
Remote Inspection	When I’m traveling on business, I want to remotely check production line status, so I don’t miss any anomalies
Smart Home	When I leave home, I want to turn off all non-essential appliances with one tap, so I can save electricity and ensure safety

Job Map

A Job Map breaks down a job into specific steps. A complete Job Map contains 8 steps:

1. Define     → Determine job objectives and required resources
2. Locate     → Obtain inputs/materials needed to accomplish the job
3. Prepare    → Organize inputs, prepare the execution environment
4. Confirm    → Verify readiness, decide whether to execute
5. Execute    → Perform the job
6. Monitor    → Monitor execution process and intermediate results
7. Modify     → Make adjustments based on monitoring results
8. Conclude   → End the job, output results

Example: “Factory Energy Management”:

Step	Job	How IoT System Supports
Define	Set monthly energy control targets	Dashboard showing historical energy baselines
Locate	Obtain power consumption data per device	Smart meters + MQTT auto-collection
Prepare	Organize data, generate energy reports	Node-RED data processing + InfluxDB storage
Confirm	Verify data accuracy	Data validation rules + anomaly alerts
Execute	Develop and deploy energy-saving measures	Remote device control / automated scheduling
Monitor	Real-time energy consumption monitoring	Grafana real-time dashboard
Modify	Adjust strategy based on data feedback	Threshold alerts + adaptive control logic
Conclude	Archive monthly energy reports	Automated report generation + email delivery

Why IoT Practitioners Need JTBD

Shifting from Technical Thinking to Customer Thinking

Common technical traps for IoT practitioners:

❌ Technical thinking: "Our solution supports MQTT, Modbus, OPC-UA, compatible with 200+ device protocols"
✅ Customer thinking: "Our solution can get your factory devices online in 3 days, reducing anomaly response time from 2 hours to 5 minutes"

Needs Hierarchy Model

In IoT pre-sales scenarios, customer needs can be re-layered using JTBD:

Layer 4: Social Value   → "My boss sees me as a driver of digital transformation"
Layer 3: Emotional Value → "I don't have to worry about being woken up at midnight"
Layer 2: Business Outcome → "Production line downtime reduced by 60%"
Layer 1: Technical Feature → "Temperature sensor + MQTT + Alert engine"

Golden rule for pre-sales communication: Start from Layer 4/Layer 3, quantify value with Layer 2, prove feasibility with Layer 1.

JTBD Application in IoT Pre-Sales Process

Initial Customer Contact
    ↓
Step 1: Use JTBD interviews to uncover real jobs
    ↓  Example question: "When equipment fails, how do you find out now? What's your handling process?"
Step 2: Structure needs with Job Statements
    ↓  "When XX happens, you want YY, so that ZZ"
Step 3: Map system capabilities with Job Maps
    ↓  Match each of the 8 steps to system features
Step 4: Build solution narrative with three value layers (functional/emotional/social)
    ↓  Form a compelling pre-sales proposal
Step 5: Prove feasibility with technical architecture (C4 Model)

JTBD Interview Practice

Interview Framework

When communicating with customers, use these question frameworks to uncover JTBD:

Question Type	Example Question
Trigger Event	”What situation would make you decide to solve this problem?”
Current Approach	”How do you handle this problem now?”
Pain Points	”What’s the biggest inconvenience with the current approach?”
Expected Outcome	”Ideally, what result would you like to achieve?”
Constraints	”What limitations do you have in budget, time, or personnel?”
Success Criteria	”If done well, how would you judge this project as successful?”

IoT Scenario Interview Example

Scenario: A food processing factory, manager wants to deploy an IoT monitoring system

Q: What made you want to deploy a monitoring system?
A: Last month, a batch of products was scrapped because the workshop temperature exceeded limits. Loss was about 200,000 yuan.

Q: How did you find out about the temperature issue at the time?
A: Quality control discovered it during a routine inspection, almost 4 hours later.

Q: Ideally, how would you want to handle this situation?
A: I want to be notified the moment temperature exceeds limits, preferably with automatic activation of backup air conditioning.

Q: If that were achieved, what would it mean to you?
A: I wouldn't have to worry about being woken up at night to handle these things anymore, and I'd have a good answer for my boss.

JTBD extracted from the interview:

Type	Job Statement
Functional	When workshop temperature exceeds limits, I want to receive an immediate alert, so I can initiate emergency measures within 5 minutes
Functional	When temperature remains abnormal, I want the system to automatically activate backup equipment, so I can reduce manual intervention
Emotional	I want to sleep peacefully at night without worrying about production line problems
Social	I want my boss to see that I’m actively promoting factory digitalization

Verification

Verify understanding of the JTBD method:

1. Concept Mastery

   • Can explain the difference between JTBD and traditional requirements analysis
   • Can distinguish functional, emotional, and social jobs
   • Can write a correctly formatted Job Statement

2. Practical Application

   • Can draw a Job Map for an IoT scenario
   • Can extract three types of jobs from a customer interview
   • Can restructure a pre-sales proposal’s requirements description using JTBD

3. Mindset Shift

   • Can consciously switch to customer perspective in technical discussions
   • Can identify emotional and social dimensions in customer needs

Best Practices

• ✅ Recommended: Before each pre-sales communication, list the customer’s Top 3 Job Statements
• ✅ Recommended: Use Job Maps to verify the proposal covers the complete job lifecycle
• ✅ Recommended: Explicitly address emotional and social jobs in the proposal
• ❌ Avoid: Only listing features without explaining “what job it helps accomplish”
• ❌ Avoid: Assuming customers can clearly express their needs (JTBD requires mining latent needs)
• ❌ Avoid: Equating JTBD with User Stories (they are fundamentally different)

Summary

Key takeaways from this section:

1. JTBD is a needs-insight mental model

   • Customers don’t buy products; they hire products to accomplish jobs
   • Focus on “what the customer wants to accomplish,” not “who the customer is”

2. Jobs have three dimensions

   • Functional: Specific, measurable operational goals
   • Emotional: Psychological feeling requirements
   • Social: Image requirements in others’ perception

3. Job Statement and Job Map are core tools

   • Job Statement: When → I want to → so I can
   • Job Map: Define → Locate → Prepare → Confirm → Execute → Monitor → Modify → Conclude

4. IoT practitioners should master JTBD in pre-sales

   • Switch from technical thinking to customer thinking
   • Build solution narratives with the three-layer value model
   • Uncover deep needs through structured interviews

References

• Christensen, C. M. (2016). Competing Against Luck: The Story of Innovation and Customer Satisfaction
• Ulwick, A. W. (2016). Jobs to Be Done: Theory to Practice
• JTBD Framework Overview - Strategyzer
• Clayton Christensen Institute - Jobs to Be Done

Building a commercial IoT product?

We provide ESP32 ODM design-to-manufacturing services. From prototype to production — the team behind this tutorial can build it with you.

Talk to us →