modbender Jobs-To-Be-Done Analyzer
The Core Concept
Customers don't buy products. They HIRE products to do a job.
"People don't want a quarter-inch drill. They want a quarter-inch hole." Actually: They want a shelf → to display photos → to feel proud of family.
The Three Job Dimensions
| Dimension | Question | Format |
|---|---|---|
| Functional | What task needs doing? | "Help me [verb] [object]" |
| Emotional | How do I want to feel? | "Make me feel [emotion]" |
| Social | How do I want to be seen? | "Help me be seen as [quality]" |
The Process
- Job Statement: "When [situation], I want to [motivation], so I can [outcome]"
- Map all 3 dimensions for each user type
- Find real competition: What ELSE could do this job?
- Prioritize: Which jobs are most critical and underserved?
Output Format
PRODUCT: [What you're analyzing]
For [User Type]:
JOB: "When [situation], I want [motivation], so I can [outcome]"
📋 FUNCTIONAL: [Task to accomplish]
💜 EMOTIONAL: [Feeling desired]
👥 SOCIAL: [Perception desired]
ALTERNATIVES: [What else could do this job?]
UNDERSERVED: [What part isn't done well?]
PRIORITY: Critical / Important / Nice-to-have
Key Questions
- "What were you trying to accomplish when you [action]?"
- "Walk me through the last time you needed to [job]"
- "What would you do if [product] didn't exist?"
- "What's frustrating about how you currently [job]?"
Integration
Compounds with:
- first-principles-decomposer → Decompose job to atomic need
- cross-pollination-engine → Find how others solve similar jobs
- app-planning-skill → Use JTBD to inform features
See references/examples.md for Artem-specific JTBD analyses