7 Must-Read Books on Jobs To Be Done

7 Must-Read Books on Jobs To Be Done

Customers are not interested in an interaction with you, your company, or even your product. Customers need to get a job done, and they will “hire” your product to do that job. Jobs-to-be-Done is more than just a framework or exercise, but a way of thinking about how you organise yourself around, and respond to, customer needs. This collection shares the best books on Jobs-to-be-Done, so you can create products that your customers will hire.

Intercom on Jobs-To-Be-Done

Intercom on Jobs-To-Be-Done

by Des Traynor

Why read?

Customers are not interested in an interaction with you, your company, or even your product. Customers need to get a job done, and they will “hire” your product to do that job. Jobs-to-be-Done is more than just a framework or exercise, but a way of thinking about how you organise yourself around, and respond to, customer needs. This collection shares the best books on Jobs-to-be-Done, so you can create products that your customers will hire.

73 pages, Intercom 2016

The Jobs To Be Done Playbook

The Jobs To Be Done Playbook

Align Your Markets, Organization, and Strategy Around Customer Needs
by Jim Kalbach

Why read?

These days, consumers have real power: they can research companies, compare ratings, and find alternatives with a simple tap. Focusing on customer needs isn’t a nice–to–have, it’s a strategic imperative.

The Jobs To Be Done Playbook (JTBD) helps organizations turn market insight into action. This book shows you techniques to make offerings people want, as well as make people want your offering.

180 pages, Two Waves Book 2020

Jobs to be Done

Jobs to be Done

Theory to Practice
by Anthony W. Ulwick

Why read?

Why do so many innovation projects fail? What are the root causes of failure? How can they be avoided?

Since 1991, Tony Ulwick has pioneered an innovation process that answers these questions. In 1999, Tony introduced Clayton Christensen to the idea that “people have underlying needs or processes in their lives, that they are addressing in some way right now” — an insight that was to become Jobs-to-be-Done Theory.

202 pages, Idea Bite Press 2016

When Coffee and Kale Compete

When Coffee and Kale Compete

Become great at making products people will buy
by Alan Klement

Why read?

A Job to be Done is the process a consumer goes through whenever she aims to transform her existing life-situation into a preferred one, but cannot because there are constraints that stop her. When Coffee and Kale Compete by Alan Klement helps you become better at creating and selling products that people will buy.

227 pages, CreateSpace Independent Publishing Platform 2018

Jobs to Be Done

Jobs to Be Done

A Roadmap for Customer-Centered Innovation
by Stephen Wunker, Jessica Wattman, David Farber

Why read?

Successful innovation doesn’t begin with a brainstorming session — it starts with the customer. So in an age of unlimited data, why do more than 50% of new products fail to meet expectations? The truth is that we need to stop asking customers what they _want, _and start examining what they need.

First popularized by Clayton Christensen, the Jobs to be Done theory argues that people purchase products and services to solve a specific problem. They’re not buying ice cream, for example, but celebration, bonding, and indulgence.

224 pages, AMACOM 2016

The Jobs-to-be-Done Handbook

The Jobs-to-be-Done Handbook

Practical techniques for improving your application of Jobs-to-be-Done
by Chris Spiek, Bob Moesta

Why read?

This book is for the Jobs-to-be-Done student and practitioner alike, who may already have a grasp of the concepts. This book is your go-to reference for quickly referring to any of the concepts or processes, so that you can be effective in a flash.

66 pages, CreateSpace Independent Publishing Platform 2014

Agile Retrospectives

Agile Retrospectives

Making Good Teams Great
by Esther Derby, Diana Larsen

Why read?

Derby and Larsen show you the tools, tricks, and tips you need to fix the problems you face on a software development project on an on-going basis.

178 pages, Pragmatic Bookshelf 2006