Product Management 6 min read

Understanding Jobs To Be Done (JTBD) and Its Application to User Stories

The article explains the Jobs To Be Done (JTBD) framework, illustrating how it helps product teams uncover deeper user motivations, generate innovative solutions beyond existing workflows, and integrate this insight with agile user stories for more outcome‑focused product design.

Continuous Delivery 2.0
Continuous Delivery 2.0
Continuous Delivery 2.0
Understanding Jobs To Be Done (JTBD) and Its Application to User Stories

Jobs To Be Done (JTBD) is a theory for understanding why users purchase a product, focusing on the underlying job they want to accomplish rather than the specific solution they currently use. It aims to uncover the essence of user expectations to inspire new ideas and products.

In simple terms, JTBD describes the "better life" a user seeks, precisely capturing the goals a group of people wants to achieve in a given situation.

For example, early consumers wanted more comfortable, convenient transportation. Henry Ford did not create a "faster horse"; he created the affordable Model T, addressing the fundamental job of moving from point A to point B and revolutionizing travel.

The key insight of JTBD is that users may not explicitly request a product, yet the market reveals a need for it, allowing teams to look beyond existing workflows and consider entirely new solutions.

JTBD provides a framework to map what is happening in a product or service domain by recording each job as an action, then assembling these jobs like puzzle pieces to see the bigger picture.

When combined with agile user stories, JTBD helps teams avoid assuming a specific solution is already chosen, which can limit innovation. Instead, JTBD encourages the creation of solutions that are not constrained by known products, though this may involve higher risk and cost.

The method also supports strategic product vision and mission definition, ensuring teams are accountable for the ultimate purpose of the product rather than just feature implementation.

JTBD breaks work into three types: functional jobs (how users achieve a specific goal), emotional jobs (how users want to feel), and social jobs (how users want to be perceived by others).

In summary, JTBD offers a new perspective based on the theory that people use products to get jobs done, enabling a deeper understanding of user needs and fostering innovative product design.

For further reading, see "Outcome‑Driven Innovation: JTBD Theory in Practice" by Tony Ulwick on Medium and Strategyn’s resources on Jobs‑to‑Be‑Done.

product managementinnovationUser Storiescustomer researchJTBD
Continuous Delivery 2.0
Written by

Continuous Delivery 2.0

Tech and case studies on organizational management, team management, and engineering efficiency

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.