jtbd-analysis

# Jobs to Be Done (JTBD) Analysis

Jobs to Be Done is a framework for understanding why customers "hire" products to help them make progress in specific circumstances.

## When to Use This Skill

**Keywords:** jobs to be done, JTBD, customer jobs, functional jobs, emotional jobs, social jobs, job statements, outcome-driven innovation, Clayton Christensen, hiring products, customer progress

**Use this skill when:**

- Understanding the underlying motivation behind feature requests
- Reframing requirements from features to customer outcomes
- Discovering unmet needs that competitors haven't addressed
- Prioritizing features based on importance vs satisfaction
- Interviewing customers about their struggles and desired progress
- Analyzing why customers switch to or from competitors

## Core Concepts

### The JTBD Framework

```text
Customers don't buy products.
Customers HIRE products to get a JOB done.
```

**Classic Example:** People don't buy a 1/4" drill. They hire it to make a 1/4" hole. But even deeper: they hire it to hang a picture, which helps them feel at home.

### Job Dimensions

| Dimension | Description | Example |
| --------- | ----------- | ------- |
| **Functional** | The practical task to accomplish | "Hang a picture on the wall" |
| **Emotional** | How the person wants to feel | "Feel proud of my decorated home" |
| **Social** | How they want to be perceived | "Be seen as having good taste" |

### Job Statement Format

```text
When [situation], I want to [motivation], so I can [expected outcome].
```

**Examples:**

```yaml
job_statements:
  - context: "When I'm starting a new project"
    motivation: "I want to quickly find qualified freelancers"
    outcome: "so I can get work done without spending weeks recruiting"

  - context: "When I'm cooking dinner for guests"
    motivation: "I want a recipe that's impressive but not complex"
    outcome: "so I can enjoy the evening without stress"

  - context: "When my flight is delayed"
    motivation: "