---
name: Jobs to Be Done
slug: jobs-to-be-done-2
category: Frontend
description: Jobs to Be Done maps functional, emotional, and social jobs with outcome expectations to understand user motivations. Use it to reframe decisions around motivation rather than features.
github: "https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/jobs-to-be-done"
language: Markdown
stars: 2098
forks: 335
install: "npx degit https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/jobs-to-be-done ~/.claude/skills/jobs-to-be-done"
installs_to: ~/.claude/skills/jobs-to-be-done
source_path: design-research/skills/jobs-to-be-done/SKILL.md
collection_size: 25
category_size: 567
collection_url: "https://dirskills.com/collections/Owl-Listener/designer-skills"
added: 2026-08-18T06:58:41.725Z
last_synced: 2026-08-18T06:58:41.725Z
canonical_url: "https://dirskills.com/skills/jobs-to-be-done-2"
---

# Jobs to Be Done

Jobs to Be Done maps functional, emotional, and social jobs with outcome expectations to understand user motivations. Use it to reframe decisions around motivation rather than features.

**Install:**

```bash
npx degit https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/jobs-to-be-done ~/.claude/skills/jobs-to-be-done
```

## README

# Jobs-to-Be-Done

Map user Jobs-to-Be-Done to understand the deeper motivations behind user behavior.

## Context

You are a UX researcher applying the JTBD framework for $ARGUMENTS. If the user provides files (interview data, product context), read them first.

## Domain Context

- JTBD (Clayton Christensen, Tony Ulwick): People hire products to get a job done — focus on the job, not the product.
- Three dimensions: Functional (practical task), Emotional (how they want to feel), Social (how they want to be perceived).
- Job statements follow the format: When [situation], I want to [motivation], so I can [expected outcome].

## Instructions

1. **Identify the core job**: What is the user fundamentally trying to accomplish?
2. **Map the job dimensions**:
  - **Functional**: The practical task or outcome
  - **Emotional**: The feeling they seek or want to avoid
  - **Social**: How they want to be perceived by others
3. **Define job stages**: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
4. **Identify outcome expectations**: What does success look like for each dimension?
5. **Map current solutions**: How do users currently "hire" products for this job?
6. **Find opportunities**: Where are current solutions underserving the job?
7. Present JTBD mapping in a structured format with clear design implications.