Unlocking Product Innovation with Jobs‑To‑Be‑Done: A Practical Guide
This article introduces the Jobs‑To‑Be‑Done (JTBD) framework, explains how it differs from ordinary user needs, outlines step‑by‑step analysis methods, provides a real‑world SaaS example, and shows why focusing on jobs drives more innovative and market‑aligned product decisions.
Steve Jobs once said, “Consumers don’t know what they need until you show them the product.” Henry Ford added, “If I had asked customers what they wanted, they would have said a faster horse.” These quotes illustrate that product innovation requires deeper insight than simple user surveys.
JTBD是什么
JTBD (Jobs To Be Done) is a theory introduced by Harvard professor Clayton Christensen in 2003. It provides a systematic framework for uncovering the underlying tasks users aim to accomplish, serving as a foundation for disruptive innovation.
JTBD emphasizes that users purchase products to complete specific jobs. Unlike ordinary needs, which are explicit requests tied to a product’s features, jobs represent the ultimate outcomes users seek.
那Jobs和一般需求的区别?
General needs are explicit, product‑specific requests (e.g., “I want a non‑stop train ticket”). Jobs are the broader objectives behind those requests (e.g., “I want to travel quickly, cheaply, and comfortably”). Jobs are stable over time, while general needs change with context.
基于Jobs分析 vs 基于具体的产品分析?
Product‑centric analysis answers questions such as which features to improve, what users dislike, and what new features to add. Jobs‑centric analysis focuses on the user’s ultimate task, the scenario, desired outcomes, pain points, and new opportunity areas, independent of any specific product.
What scenario does the user apply the solution?
What is the user’s task in that scenario?
What progress or achievement does the user gain after completing the task?
What pain points or obstacles exist during task execution?
What new opportunities arise from fulfilling the task?
一个基于jobs分析应用示例
Project background: CoolHome, a B2B SaaS serving store designers and sales staff, needed research on store scenarios to inform new solutions.
Map the main business processes of the store scenario as the analysis context.
Observe current user behaviors and conduct interviews to uncover sub‑tasks (functional, emotional, social) behind those behaviors.
Identify pain points and anxieties in the current solution.
Co‑create with multiple roles to explore new product or solution directions.
Using the “first‑time customer reception” scenario as an example, the analysis uncovers the tasks, desired outcomes, and hidden opportunities.
写在最后
JTBD的价值?
Helps identify innovative opportunity points and expand possibilities.
Filters out solutions unrelated to the core job, saving time.
Reveals true competitors, which may be cross‑industry products that satisfy the same job.
JTBD是很早的概念,但是为什么并没有流行起来?
Its core ideas overlap with common user‑centered thinking, leading to underappreciation.
It is a theoretical framework rather than a concrete method, resulting in varied interpretations.
Practical application (e.g., Outcome‑Driven Innovation) requires extensive skills, multi‑role collaboration, and executive support, making adoption challenging.
我为什么想要介绍JTBD?
JTBD addresses the hardest part of product innovation—understanding the true, stable user needs behind surface requests. By focusing on jobs, teams can avoid feature bloat, align on long‑term goals, and create solutions that genuinely help users achieve their desired outcomes.
Qunhe Technology User Experience Design
Qunhe MCUX
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.