liveBook · Manning

Jobs-to-be-done

As explained in Decision Engineering

Jobs-to-Be-Done is a product-management framework that explains adoption in terms of customers hiring products to make progress in a circumstance.

Jobs-to-Be-Done reframes adoption as hiring a product to make progress in a specific circumstance. In technical decisions, people reach for systems to complete tasks, not for the systems themselves. section 2.1.1

Before settling on a proposed system, clarify:

A familiar solution request

“We need a CRM” can be a reflexive solution. Step back to describe the job and its context before deciding whether a CRM—or another approach—fits. section 2.1.1

How Decision Engineering covers it

How deep it goes
Defines the hiring-and-progress premise and offers framing questions without prescribing a formal procedure.
Examples
Uses CRM, message queue, and documentation platform requests as examples of reflexive solution choices.
What you can do after
Evaluate architectural requests by identifying the situation, struggling person, and desired improvement before choosing a system.
How it connects
Connects product management and architecture decisions through customer adoption and task progress.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Decision Engineering. The section links point to the parts of the book it draws on.