Content Marketing Glossary

  • What is Jobs-to-be-Done (JTBD)?

What is Jobs-to-be-Done (JTBD)?

Jobs-to-be-Done (JTBD)

Jobs-to-be-Done (JTBD) is a framework for understanding customer behaviour that shifts the question from ‘who is the customer?’ to ‘what job is the customer hiring this product to do?’ Popularised by Clayton Christensen and refined by Bob Moesta, Alan Klement, and others, JTBD treats purchases as ‘hires’ - customers hire products to solve specific situational needs and fire them when they stop delivering on those jobs. The framework produces sharper product, marketing, and positioning decisions than demographic-based customer thinking.

The central insight

Three foundational JTBD observations:

People don’t buy products; they hire them for jobs. The product is a means to an end; the end is the job-to-be-done. Understanding the job illuminates why people buy and why they stop.

The same job can be served by very different products. Milkshakes compete with bagels (job: something to eat on my commute), not with other milkshakes. Competitive set defined by job, not category.

Jobs are situational. The same person hires different products for different situations. The job, not the buyer demographic, determines fit.

Functional, emotional, and social jobs

JTBD typically distinguishes three job types:

Functional job. The practical task the product performs. ‘Get my coffee made quickly in the morning.’

Emotional job. How the customer wants to feel. ‘Feel professional and prepared for the workday.’

Social job. How the customer wants to be perceived. ‘Look like someone who cares about good coffee.’

Most products serve all three simultaneously. Products that only serve the functional job get beaten by competitors that also serve emotional and social jobs.

The JTBD interview

The core research method, roughly:

Recruit recent buyers. People who purchased the product or a competitor recently. Fresh memory.

Walk through the decision timeline. ‘When did you first realise you needed something like this? What happened next?’ Build the timeline of their consideration and purchase.

Identify the trigger events. What specific situations preceded their search? These are the jobs the product is hired for.

Understand the forces. JTBD uses a ‘four forces’ model - push (current situation dissatisfaction), pull (new product attraction), anxiety (worry about switching), habit (inertia with current solution).

Write the job story. ‘When [situation], I want to [motivation], so I can [expected outcome].’

Job stories vs user stories

A common distinction worth noting:

User story (Agile). ‘As a [user type], I want [feature], so that [benefit].’ Feature-centric.

Job story (JTBD). ‘When [situation], I want to [motivation], so I can [expected outcome].’ Situation-centric.

The shift from user type to situation is the central JTBD move. Same user type has different jobs in different situations.

Common JTBD applications

Five practical uses:

Product prioritisation. Which features best serve the most-hired-for jobs? Roadmap follows job importance.

Positioning. Position the product against the alternative solutions to the same job, not against product-category competitors.

Messaging. Lead with the job, not the product. ‘When you need to draft content at scale in your voice’ rather than ‘AI content tool.’

Segmentation. Segment by job, not by demographic. Users hiring the product for different jobs have different needs.

Churn understanding. Why are customers firing the product? The job stopped being served well, or a better alternative emerged for that job.

Common JTBD mistakes

Four patterns:

Conflating job with feature. ‘The job is email management’ is a category. ‘When I return from holiday and have 400 unread emails, I want to quickly triage them’ is a job.

Too abstract. ‘The job is to be productive’ is too general to be actionable. Jobs should be specific.

Ignoring emotional and social layers. Pure functional-job analysis misses why people prefer one product over another that serves the functional job equally well.

One-job-per-customer thinking. Customers hire the product for multiple jobs across different contexts. Treat this as multiple job profiles, not a single average.

JTBD in content strategy

Three applications:

Content planning organised by job, not topic. ‘Content that helps users hired-for-job-X’ rather than ‘articles about topic Y.’

Audience framing in articles. Open with the situation the reader is in (the job), not with generic category introduction.

Example selection. Concrete examples of people doing the job the content addresses - rather than generic ‘marketers’ or ‘businesses.’

Penfriend’s content briefs use job-story framing when possible. ‘When [specific situation], the reader wants to [motivation], so they can [outcome].’ This grounds the generated content in situational specificity rather than abstract topic coverage - which is how content-market fit tends to happen.

Related terms