Map functional, emotional, and social jobs with outcome expectations. Use when reframing decisions around motivation rather than features. For who the user is, use `user-persona`.
Installs into .claude/skills of the current project.
Are you the author of Jobs To Be Done?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/owl-listener-jobs-to-be-done)
---
name: jobs-to-be-done
description: Map functional, emotional, and social jobs with outcome expectations. Use when reframing decisions around motivation rather than features. For who the user is, use `user-persona`.
---
# 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.
