Builds features based on Jobs-to-be-Done theory using Bob Moesta's frameworks. Use when designing features, identifying customer jobs, understanding push/pull forces, or uncovering hidden needs beyond stated feature requests.
Claude uses this skill when:
Core Principle:
"People don't buy products, they hire them to make progress in their lives."
The Job:
Four Forces:
PUSH (away from current):
- Pains with current solution
- Frustrations
PULL (toward new):
- Attraction to new solution
- Expected benefits
ANXIETY (hesitation):
- Fear of new
- "What if it doesn't work?"
HABIT (inertia):
- "Current way works okay"
- Switching cost
# Feature: [Name]
## The Job
**When** [situation],
**I want to** [motivation],
**So I can** [expected outcome].
### Example:
When I'm planning my week,
I want to see all my commitments in one place,
So I can feel in control and not miss anything.
## Forces Analysis
### Push (Problems with Current)
- [Current pain 1]
- [Current pain 2]
### Pull (Attraction to New)
- [Desired benefit 1]
- [Desired benefit 2]
### Anxiety (Hesitations)
- [Worry 1: "What if..."]
- [Worry 2: "What if..."]
### Habit (Inertia)
- [Current habit 1]
- [Switching cost]
## Design for the Job
### Functional
[How feature helps get job done]
### Emotional
[How feature makes them feel]
### Social
[How it affects their image]
## Address Forces
- **Reduce anxiety:** [how]
- **Overcome habit:** [how]
- **Amplify pull:** [how]
Understand Job:
Forces:
Design:
Wrong Question: "How do we make better milkshakes?" Right Question: "What job is the milkshake being hired for?"
Discovery:
Result: Different products for different jobs
Bob Moesta:
"People don't want a quarter-inch drill. They want a quarter-inch hole."
Clayton Christensen:
"When we buy a product, we essentially 'hire' something to get a job done."