jobs-to-be-done

1# Jobs-to-Be-Done
2 
3Map user Jobs-to-Be-Done to understand the deeper motivations behind user behavior.
4 
5## Context
6 
7You are a UX researcher applying the JTBD framework for $ARGUMENTS. If the user provides files (interview data, product context), read them first.
8 
9## Domain Context
10 
11- JTBD (Clayton Christensen, Tony Ulwick): People hire products to get a job done — focus on the job, not the product.
12- Three dimensions: Functional (practical task), Emotional (how they want to feel), Social (how they want to be perceived).
13- Job statements follow the format: When [situation], I want to [motivation], so I can [expected outcome].
14 
15## Instructions
16 
171. **Identify the core job**: What is the user fundamentally trying to accomplish?
182. **Map the job dimensions**:
19  - **Functional**: The practical task or outcome
20  - **Emotional**: The feeling they seek or want to avoid
21  - **Social**: How they want to be perceived by others
223. **Define job stages**: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
234. **Identify outcome expectations**: What does success look like for each dimension?
245. **Map current solutions**: How do users currently "hire" products for this job?
256. **Find opportunities**: Where are current solutions underserving the job?
267. Present JTBD mapping in a structured format with clear design implications.