Jobs to be Done (JTBD) is a [framework](https://www.productplan.com/glossary/jobs-to-be-done-framework/?ref=blog.builtfor.dev) for understanding customer needs and motivations. It focuses on the "job" a customer is trying to accomplish rather than on the customer's characteristics or the product itself. This approach shifts the emphasis from what customers buy to why they purchase.

## Key Concepts

- **The "Job"**: A job represents the progress a person aims to make in a specific circumstance. It's not about the product they're buying but the goal they're trying to achieve.
- **Functional, Emotional, and Social Dimensions**: Jobs encompass functional aspects (practical tasks), emotional aspects (desired feelings), and social aspects (how people want others to perceive them).
- **Circumstances and Desired Outcomes**: To accurately define a job, it's crucial to understand both the specific situation (circumstance) and what success looks like (desired outcome).

## The JTBD Statement

A typical JTBD statement follows this format:

> "When [circumstance], I want to [motivation], so I can [desired outcome]."

Example:

> "When troubleshooting a production issue, I want to instantly recreate the exact build environment so I can quickly identify and resolve the problem without guesswork."

## Why JTBD Matters

- **User-Centric Innovation**: By focusing on jobs, you can innovate in ways that truly matter to your users.
- **Better Positioning**: Understanding the job helps you communicate your value proposition more effectively.
- **Competitive Advantage**: Identifying underserved jobs can reveal opportunities for differentiation.
- **Product Development**: JTBD can guide feature prioritization and development decisions.

## Applying JTBD

- Identify the circumstances that trigger a need for your developer tool
- Understand the technical challenge your users are trying to solve with your tool
- Determine the functional, emotional, and social aspects of the job
- Define clear desired outcomes from the developer's perspective
- Use these insights to guide product development, messaging, marketing, and overall strategy

Customers don't simply purchase products; they "hire" them for specific jobs. Understanding these jobs is crucial for creating value and taking your developer tool to market.