jtbd-analyzer
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
More from fimoklei/pm-ai-playbook
first-principles-decomposer
Break any problem down to fundamental truths, then rebuild solutions from atoms up. Use when user says "firstp", "first principles", "from scratch", "what are we assuming", "break this down", "atomic", "fundamental truth", "physics thinking", "Elon method", "bedrock", "ground up", "core problem", "strip away", or challenges assumptions about how things are done.
20optimize-docs
Condense markdown documentation for token efficiency while preserving all semantic meaning. Use when rules, documentation, or config files need optimization. Target 25-40% reduction through systematic condensation patterns.
18idea-challenger
Pre-launch red team analysis that identifies failure modes and validates assumptions before resource commitment. Use when evaluating new products/features/strategies, before significant resource allocation, when stakeholders seem overly optimistic, or when cost of failure would be high (reputation, budget, market position).
18pre-mortem-analyst
Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".
18inversion-strategist
Flip problems upside down - instead of "how to succeed", ask "how to definitely fail" then avoid those paths. Use when user says "invert", "inversion", "flip it", "opposite approach", "how would this fail", "avoid failure", "what NOT to do", "Munger", "anti-goals", "guarantee failure".
18security-threat-model
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling.
16