marketing-shibata50/designer-skills
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Create SKILL.md for Jobs-to-Be-Done framework

Browse source 
Added a new SKILL.md file outlining the Jobs-to-Be-Done framework for UX research, including context, instructions, and dimensions of user jobs.
This commit is contained in:
MC Dean 2026-03-07 15:05:28 +00:00 • committed by GitHub
parent 340377b9a8
commit 55360f249c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 32 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

32
design-research/skills/jobs-to-be-done/SKILL.md Normal file
View file

@ -0,0 +1,32 @@
---
name: jobs-to-be-done
description: Map user Jobs-to-Be-Done with functional, emotional, and social dimensions plus outcome expectations. Use when reframing product decisions around user motivations rather than features.
---
# 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. 2. **Map the job dimensions**:
3. - **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. 4. **Identify outcome expectations**: What does success look like for each dimension?
5. 5. **Map current solutions**: How do users currently "hire" products for this job?
6. 6. **Find opportunities**: Where are current solutions underserving the job?
7. Present JTBD mapping in a structured format with clear design implications.