The job to be done

"The art is to always look for the why, the essence, and know when to stop this process"

"Or, finding the essence at the right level of abstraction for the job you want to do"  

Marketing theory

(boo)

Product design

(a bit more yay)

Focus on understanding the job people want to do and find out how the product fits into people's lives

Sell the product's outcome, not the product itself. Beautiful, cut grass - not lawnmower or GM seeds

Build products people want to buy

Write code

people want to use

What is the job of each:

application/service

class/object

method/function

(parameter/variable)

How can we find the jobs to be done?

Conversation

Examples

Specification

Domain understanding

Experimentation

Job stories?

When...

I want to...

So that...

How do you know when you've found the job?

Clarity

Simplicity

No "and"

(aka SRP)

Clearly named

It reads well...

...it feels good!

Job of this talk:

introduce people to the concept of  "the job to be done" applied to code