jobs-to-be-done
This Claude Code skill maps user Jobs-to-Be-Done across functional, emotional, and social dimensions to uncover deeper motivations behind user behavior. Use it when analyzing interview data or product context to reframe design decisions around what users are fundamentally trying to accomplish rather than focusing on product features alone.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/jobs-to-be-done && cp -r /tmp/jobs-to-be-done/design-research/skills/jobs-to-be-done ~/.claude/skills/jobs-to-be-doneSKILL.md
# 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.
Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.
Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.
Create QA checklists for verifying design implementation accuracy.
Establish design review gates with criteria, checklists, and approval workflows.
Plan and facilitate design sprints from challenge framing through prototype testing.
Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
Design team workflows covering task management, collaboration rituals, and tooling.