Jobs To Be Done
- 949 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
jobs-to-be-done is a product research skill that maps user Jobs-to-Be-Done across functional, emotional, and social dimensions so developers prioritize outcomes over feature checklists.
About
jobs-to-be-done is a UX research skill from owl-listener/designer-skills applying the Clayton Christensen and Tony Ulwick JTBD framework to uncover why users hire a product, not just what features they request. The skill maps functional tasks, emotional needs, and social motivations alongside outcome expectations, reading interview data and product context files when provided. Developers and product engineers reach for jobs-to-be-done when reframing roadmap debates, writing PRDs, or evaluating whether proposed features solve the underlying job users are trying to accomplish. The framework shifts planning from output lists to measurable job outcomes, producing motivation maps that guide architecture and prioritization before implementation sprints begin.
- Maps functional, emotional, and social job dimensions
- Structures jobs using When [situation], I want to [motivation], so I can [outcome]
- Defines 8-stage job lifecycle (define through conclude)
- Identifies outcome expectations and opportunity gaps
- Reads interview data or product files when provided
Jobs To Be Done by the numbers
- 949 all-time installs (skills.sh)
- +47 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #496 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill jobs-to-be-doneAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 949 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you map Jobs-to-Be-Done for product decisions?
Reframe product decisions around real user motivations instead of feature lists.
Who is it for?
Developers and PMs reframing feature debates around user motivations and measurable job outcomes before writing specs.
Skip if: Teams needing competitor feature matrices or visual UI audits rather than motivation-centered requirement framing.
When should I use this skill?
A developer needs to reframe product decisions around user jobs, motivations, and outcomes instead of feature lists.
What you get
JTBD motivation map, outcome expectation list, and job-centered requirement framing for product decisions.
- JTBD motivation map
- Outcome expectation list
- Job-centered requirement framing
Files
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.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Use jobs-to-be-done for motivation and outcome mapping rather than competitive-analysis skills focused on rival UX benchmarking.
FAQ
What dimensions does jobs-to-be-done map?
jobs-to-be-done maps functional tasks users need done, emotional feelings they seek, and social perceptions they want. The skill applies the JTBD framework from Clayton Christensen and Tony Ulwick to reframe product decisions.
What inputs does jobs-to-be-done accept?
jobs-to-be-done reads interview transcripts, product context files, and user research artifacts when provided. The skill uses those inputs to produce motivation maps and outcome expectations for roadmap decisions.
Is Jobs To Be Done safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.