home / skills / menkesu / awesome-pm-skills / jtbd-building

jtbd-building skill

/jtbd-building

This skill helps design features using Jobs-to-be-Done theory to uncover real customer needs beyond requests.

npx playbooks add skill menkesu/awesome-pm-skills --skill jtbd-building

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.0 KB
---
name: jtbd-building
description: 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.
---

# Jobs-to-be-Done Product Design

## When This Skill Activates

Claude uses this skill when:
- Designing new features
- Understanding customer needs
- Moving beyond feature requests
- Identifying real jobs to be done

## Core Frameworks

### 1. Jobs Theory (Source: Bob Moesta, JTBD Co-Creator)

**Core Principle:**
> "People don't buy products, they hire them to make progress in their lives."

**The Job:**
- Functional: What needs to get done?
- Emotional: How do they want to feel?
- Social: How do they want to be perceived?

### 2. Forces Diagram

**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
```

---

## Action Templates

### Template: JTBD Analysis

```markdown
# 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]
```

---

## Quick Reference

### 🎯 JTBD Checklist

**Understand Job:**
- [ ] Situation identified
- [ ] Motivation clear
- [ ] Desired outcome defined
- [ ] Job story written

**Forces:**
- [ ] Push forces (current pains)
- [ ] Pull forces (desired benefits)
- [ ] Anxiety forces (hesitations)
- [ ] Habit forces (inertia)

**Design:**
- [ ] Solves functional job
- [ ] Addresses emotional job
- [ ] Considers social job
- [ ] Reduces switching anxiety

---

## Real-World Examples

### Example: Milkshake Marketing (Bob Moesta)

**Wrong Question:** "How do we make better milkshakes?"
**Right Question:** "What job is the milkshake being hired for?"

**Discovery:**
- Morning commuters: Long, thick shake for entertainment during boring drive
- Parents: Quick, thin shake to feel like good parent ("I got you a treat")

**Result:** Different products for different jobs

---

## Key Quotes

**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."

Overview

This skill builds features and product decisions using Jobs-to-be-Done (JTBD) theory and Bob Moesta’s practical frameworks. It helps move teams beyond surface feature requests to uncover real customer jobs, emotional and social outcomes, and the forces that enable or block change. Use it to design features that customers will actually hire to make progress.

How this skill works

The skill structures discovery into a clear job statement (situation, motivation, expected outcome) and a forces diagram (Push, Pull, Anxiety, Habit). It translates those insights into functional, emotional, and social design requirements and concrete tactics to reduce anxiety, overcome inertia, and amplify attraction. Templates and checklists make it easy to apply JTBD across features and user segments.

When to use it

  • Designing a new feature or product to ensure it solves a real job
  • Prioritizing roadmap items by which jobs deliver the most progress
  • Converting vague feature requests into concrete jobs and outcomes
  • Diagnosing low adoption to identify anxiety or habit barriers
  • Segmenting users by the different jobs they hire your product to do

Best practices

  • Write a concise job story: When [situation], I want to [motivation], so I can [outcome]
  • Map Push, Pull, Anxiety, and Habit forces for each job and segment
  • Design for functional, emotional, and social outcomes — not just tasks
  • Start with observed behavior and interviews, not feature wish lists
  • Prototype to reduce anxiety and test switch-enabling experiences

Example use cases

  • Turn customer support requests into job statements and surface root causes
  • Design onboarding flows that reduce anxiety and demonstrate immediate pull
  • Create product variants for distinct jobs (e.g., quick snack vs. long commute)
  • Prioritize roadmap by which jobs unlock most user progress or retention
  • Run adoption experiments that target habit barriers and switching costs

FAQ

How is a job different from a feature?

A job describes the progress a customer wants to make (situation, motivation, outcome); a feature is one possible solution to help complete that job.

When should I use the forces diagram?

Use it whenever adoption stalls or you need to design an experience that convinces users to switch — it clarifies what pushes users away, pulls them toward, and what blocks change.