Stats
Actions
Tags
Applies JTBD framework to analyze requirements, uncovering functional, emotional, and social customer jobs for reframing features as outcomes and prioritizing motivations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/requirements-elicitation:jtbd-analysisThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Jobs to Be Done is a framework for understanding why customers "hire" products to help them make progress in specific circumstances.
Jobs to Be Done is a framework for understanding why customers "hire" products to help them make progress in specific circumstances.
Keywords: jobs to be done, JTBD, customer jobs, functional jobs, emotional jobs, social jobs, job statements, outcome-driven innovation, Clayton Christensen, hiring products, customer progress
Use this skill when:
Customers don't buy products.
Customers HIRE products to get a JOB done.
Classic Example: People don't buy a 1/4" drill. They hire it to make a 1/4" hole. But even deeper: they hire it to hang a picture, which helps them feel at home.
| Dimension | Description | Example |
|---|---|---|
| Functional | The practical task to accomplish | "Hang a picture on the wall" |
| Emotional | How the person wants to feel | "Feel proud of my decorated home" |
| Social | How they want to be perceived | "Be seen as having good taste" |
When [situation], I want to [motivation], so I can [expected outcome].
Examples:
job_statements:
- context: "When I'm starting a new project"
motivation: "I want to quickly find qualified freelancers"
outcome: "so I can get work done without spending weeks recruiting"
- context: "When I'm cooking dinner for guests"
motivation: "I want a recipe that's impressive but not complex"
outcome: "so I can enjoy the evening without stress"
- context: "When my flight is delayed"
motivation: "I want real-time updates on my phone"
outcome: "so I can plan my connections and notify people waiting"
Understand why customers switched to your product:
switch_interview_flow:
1. First thought:
"When did you first start thinking you needed [solution]?"
2. Passive looking:
"What did you do about it initially?"
3. Active looking:
"When did you start actively looking for alternatives?"
4. Deciding:
"What made you finally choose [product]?"
5. Consuming:
"What happened after you started using it?"
6. Satisfaction:
"How is it working out? What's still frustrating?"
PUSH (Away from current situation)
├── Problems with current solution
├── Frustrations and pain points
└── Triggering events
PULL (Toward new solution)
├── Attraction to new way
├── Hoped-for outcomes
└── Perceived improvements
INERTIA (Keeping current behavior)
├── Habits and familiarity
├── Switching costs
└── "Good enough" mentality
ANXIETY (About new solution)
├── Will it actually work?
├── Learning curve
└── Risk of wrong choice
For change to happen: Push + Pull > Inertia + Anxiety
Break down the main job into stages:
job_map:
main_job: "Prepare a healthy meal for my family"
stages:
1_define:
name: "Define what to make"
sub_jobs:
- "Decide on dietary constraints"
- "Consider what's in the fridge"
- "Find a suitable recipe"
2_prepare:
name: "Prepare ingredients"
sub_jobs:
- "Gather all ingredients"
- "Prep vegetables and proteins"
- "Measure quantities"
3_execute:
name: "Cook the meal"
sub_jobs:
- "Follow recipe steps"
- "Time multiple dishes"
- "Adjust seasoning"
4_complete:
name: "Serve and clean up"
sub_jobs:
- "Plate attractively"
- "Clean as you go"
- "Store leftovers properly"
translation_pattern:
job: "Find a suitable recipe quickly"
requirements:
functional:
- "Search recipes by ingredient"
- "Filter by dietary restrictions"
- "Sort by prep time"
emotional:
- "Show confidence ratings"
- "Display success photos"
- "Offer beginner-friendly options"
social:
- "Enable sharing on social media"
- "Show what friends have made"
- "Community ratings and reviews"
More precise than job statements:
[Direction] + [measure] + [object of control] + [context]
Examples:
outcome_statements:
- "Minimize the time it takes to find a relevant recipe"
- "Increase the likelihood that ingredients are in stock"
- "Reduce the effort required to clean up after cooking"
- "Minimize the risk of burning or overcooking food"
HIGH IMPORTANCE
│
OVER-SERVED │ UNDERSERVED
(Don't invest) │ (Opportunity!)
│
──────────────────────────────────────────────
│
APPROPRIATELY │ APPROPRIATELY
SERVED │ SERVED
(Low value area) │ (Maintain)
│
LOW IMPORTANCE
│
LOW SATISFACTION ───────── HIGH SATISFACTION
Opportunity Score = Importance + (Importance - Satisfaction)
Add these to stakeholder interviews:
jtbd_questions:
context:
- "When do you typically need to [activity]?"
- "What triggers you to start this process?"
motivation:
- "What are you ultimately trying to achieve?"
- "Why is this important to you?"
current_solution:
- "How do you handle this today?"
- "What's frustrating about the current approach?"
desired_progress:
- "In an ideal world, how would this work?"
- "What would success look like?"
emotional:
- "How do you feel when this goes wrong?"
- "How would you feel if this was effortless?"
social:
- "Who else is affected by how you do this?"
- "How do others perceive this activity?"
# After elicitation, analyze through JTBD lens
/requirements-elicitation:discover "inventory management"
# Then apply JTBD framework
# Load this skill and analyze:
# 1. What job are users hiring this system to do?
# 2. What are the functional/emotional/social dimensions?
# 3. Which jobs are underserved?
jtbd_analysis:
domain: "inventory management"
date: "2025-12-26"
main_job:
statement: "Keep the right products in stock without excess inventory"
context: "As a retail manager responsible for product availability"
job_dimensions:
functional:
- "Predict demand accurately"
- "Reorder at the right time"
- "Track stock levels"
emotional:
- "Feel confident about stock decisions"
- "Avoid the stress of stockouts"
- "Pride in efficient operations"
social:
- "Be seen as competent by leadership"
- "Maintain customer satisfaction"
- "Demonstrate data-driven decisions"
job_map:
- stage: "Monitor inventory levels"
jobs: [...]
opportunities: [...]
opportunity_scores:
- job: "Predict seasonal demand"
importance: 9
satisfaction: 4
score: 14 # High opportunity
- job: "Generate reorder reports"
importance: 6
satisfaction: 7
score: 5 # Low priority
/interview - Conduct JTBD-style interviews/simulate - Simulate stakeholders for JTBD exploration/discover - Full elicitation workflow/prioritize - Use JTBD opportunity scores for prioritizationFor detailed guidance:
External:
Last Updated: 2025-12-26
npx claudepluginhub melodic-software/claude-code-plugins --plugin requirements-elicitationApplies the Jobs-to-be-Done framework to uncover customer jobs, pains, and gains, producing structured analyses with job performer definitions, process maps, and outcome statements.
Applies JTBD product methodology: job statements, struggling moments, hire/fire criteria. Useful when feature requests or personas aren't driving product decisions.
Conducts JTBD analysis: synthesizes job statements, analyzes switch interviews (Moesta/Spiek four forces), applies Ulwick ODI, and maps jobs for small teams (1-5 people). Useful for user motivation and switch trigger research.