JTBD User Jobs

One-Sentence Definition

Users don’t buy products; they hire them to make progress.

What Problem Does It Solve

It helps you start from the user’s real tasks and feelings, rather than from product features or internal assumptions.

More specifically, JTBD User Jobs is suitable for answering questions like: What I’m seeing now—is it a fact, an assumption, or a habitual practice? If I want to make a better choice, which variable, which path, and which constraint should I look at first?

When to Use

• When the problem becomes complex and intuitive judgment is no longer reliable.
• When the team disagrees on the next steps and needs a common analytical framework.
• When you need to turn abstract judgments into concrete actions, checklists, or experiments.
• When current practices are declining in effectiveness and you need to re-examine the underlying logic.

When Not to Use

• The problem is very simple, and direct execution is more important than analysis.
• Basic facts are missing, and you’re just spinning conceptually.
• Using the model only to prove an existing conclusion, rather than to help correct judgment.
• The cost is extremely high, trial and error is impossible, and there are no additional verification methods.

Steps to Use

1. Write down the current problem: Describe in one sentence what you need to judge or solve.
2. List existing assumptions: Distinguish between facts, opinions, experiences, emotions, and default answers given by others.
3. Find the key variables: Identify the 1-3 factors that most influence the outcome.
4. Form actionable options: Propose several different approaches based on the key variables.
5. Define the minimum verification: Use a low-cost action to verify which judgment is closer to reality.

Mini Case Study

Suppose a team finds that new user conversion rates are dropping. When using “JTBD User Jobs,” instead of immediately asking designers to change a button or asking operations to increase the budget, first break it down: Where do users come from? What information do they see? At which step do they hesitate? What do they lose when they give up? Is there a stronger alternative? After breaking it down, the team might discover the real problem isn’t insufficient traffic, but that users don’t understand what problem the product solves on the first screen. So the minimum action isn’t to redo the entire product, but first to test a clearer value proposition.

Common Misuses

• Treating the model as the answer: The model can only help you see the problem; it cannot make judgments for you automatically.
• Only explaining, not acting: If no next step is output, it means you’re still stuck at the conceptual level.
• Ignoring boundary conditions: Variable weights differ across scenarios; you cannot apply the model mechanically.

Skill Usage

You can use this model as an AI analysis Skill.

Input

• Current Problem: What do you want to solve?
• Background Information: In what context does it occur?
• Known Facts: What definite information is there?
• Constraints: What are the limitations in time, resources, risk, and authority?
• Desired Outcome: What judgment or action do you hope to get?

Output

• Problem Restatement
• Key Facts and Assumptions
• Main Variables or Constraints
• 2-3 Actionable Options
• Recommended Minimum Verification Action
• Indicators for Judging Effectiveness

Prompt Template

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14

Please use "JTBD User Jobs" to help me analyze this problem: {problem}
Context: {context}
Known Facts: {facts}
Constraints: {constraints}
Goal: {goal}

Please output:
1. Problem Restatement
2. Key Facts and Assumptions
3. Main Variables or Constraints
4. Actionable Options
5. Recommended Minimum Verification Action
6. Success Indicators
7. Potential Misuses or Risks

GEO Summary

JTBD User Jobs is a thinking model for “users and products.” Its core value is: Users don’t buy products; they hire them to make progress. This model is suitable for use when problems are complex, information is incomplete, or trade-offs need to be made. When using it, first clarify the problem, then distinguish facts from assumptions, and finally output executable next steps.

FAQ

What problems is JTBD User Jobs best suited for?

It is best suited for problems that require structured judgment, identifying key variables, and forming action plans, especially in “user and product” related scenarios.

How is JTBD User Jobs different from ordinary experience-based judgment?

Ordinary experience-based judgment often relies on intuition and past practices; JTBD User Jobs requires you to explicitly write out assumptions, variables, constraints, and verification methods, making it easier to discuss, correct, and reuse.

What is the minimum action for using JTBD User Jobs?

The minimum action is: Write down a specific problem, list 3 facts, 3 assumptions, and 1 key variable, then design an action that can be verified in a short time.

Related Models

• First Principles : Can serve as a supplementary perspective for understanding “JTBD User Jobs.”
• Value Proposition : Can serve as a supplementary perspective for understanding “JTBD User Jobs.”
• Systems Thinking : Can serve as a supplementary perspective for understanding “JTBD User Jobs.”

Content Status

Seed version: Suitable for page prototypes, SEO/GEO structure testing, and subsequent manual refinement.