Jobs To Be Done (JTBD)
Jobs To Be Done is a framework that views customers as 'hiring' products to make progress on a specific goal in a given context, focusing on the underlying job rather than demographics or features.
In depth
JTBD reframes the question from 'who is the customer' to 'what progress is the customer trying to make,' capturing the functional, emotional, and social dimensions of that goal. Teams uncover jobs through interviews about real switching moments, then express them as job statements like 'when I onboard a new hire, help me get them productive in a week without manual setup.' Because the job stays stable even as products and demographics change, it gives positioning and roadmap decisions a durable anchor.
A frequent pitfall is confusing a solution with a job: 'use our dashboard' is a feature, not a job, and over-fitting to it blinds you to competitors solving the same job differently. In a quiz-funnel and lead-qualification workflow, framing scorecard questions around the visitor's current job-in-progress, rather than product features, surfaces high-intent leads and lets the result page recommend the path that best advances their actual goal.
Example in practice
Frequently asked questions
Is JTBD a replacement for buyer personas?
No, they are complementary. Personas describe who is involved, while JTBD describes the progress they are trying to make, and combining them produces messaging that is both targeted and motivating.
How do you uncover a customer's job to be done?
The most reliable method is interviewing recent buyers about the moment they decided to switch and what they hoped would change. These switch stories reveal the functional and emotional job far better than feature surveys.
What is a good job statement format?
A common structure is 'When [situation], I want to [motivation], so I can [expected outcome].' Keeping it solution-agnostic ensures the statement stays valid even if your product changes.