What Jobs-to-be-Done is
The idea, as set out in the Harvard Business Review article listed under sources, is that customers do not buy products so much as hire them to get a job done. The job is the progress a person is trying to make in a given circumstance. The circumstance matters more than the customer's characteristics: the same person hires different things for a weekday commute and a weekend outing, and two people with nothing in common demographically may share a job exactly. The article's argument is that companies collect ever more data about who customers are while learning little about why they buy, and that the "why" lives in the job.
For a marketer, this changes the unit of analysis. Segmentation by age, region or company size describes the market; it does not explain purchase. A job explains purchase, because it describes the situation that creates demand and the outcome that would count as success. Messages written to the job land because they describe the reader's own situation back to them. Messages written to a demographic describe an average nobody recognises.
The framework makes visible the competition you did not know you had. If the job is "get dinner on the table on a weeknight without thinking about it", a meal kit competes with a supermarket ready meal, a takeaway app and a well-stocked freezer, not only with other meal kits. What it hides is everything outside the job: brand affinity that is not tied to progress, habit, and the parts of a purchase decided by price alone. The STP framework remains the tool for choosing which segments to serve; jobs are a better way to define those segments than demographics alone. The comparison of buyer personas and jobs-to-be-done sets out which planning questions each lens answers and how to write a job into a persona rather than choosing between them.
Functional, emotional and social jobs
| Dimension | What it describes | Typical phrasing | How it shows up in marketing |
|---|---|---|---|
| Functional | The practical task to be accomplished and the outcome that counts as done | "Get the quarterly accounts filed on time" | Feature pages, specifications, proof the task gets done |
| Emotional | How the person wants to feel, or stop feeling, while making the progress | "Stop worrying about this in the evenings" | Tone, reassurance, guarantees, the story a landing page tells |
| Social | How the person wants to be seen by others as a result | "Look organised in front of the board" | Case studies, badges, visible outcomes, what the product says about its user |
Most teams stop at the functional job because it is the easiest to hear in an interview and the easiest to write a feature for. The source article is explicit that jobs have social and emotional dimensions that can be more powerful than the functional ones, and that these are the dimensions competitors on feature lists rarely address. A budgeting app that files the same reports as its rivals wins by relieving a specific anxiety; a business tool wins by making its user look competent to a particular audience.
The three dimensions are not separate jobs so much as layers of one job. The functional layer sets what has to happen; the emotional layer sets how it must feel; the social layer sets what it must signal. A product that nails the functional layer and ignores the others is hired reluctantly and dropped the moment something better appears. The value proposition canvas takes the same three layers and splits them into pains and gains for mapping against a product, which is the natural next tool once the job is known.
Writing a job statement
A job statement is short, product-free and written from the customer's side. The widely used job-story format has three parts: when a situation arises, I want to make some progress, so that I can reach an outcome. "When a client asks for last month's numbers and I am away from my desk, I want to send a clean summary in a minute, so I can look in control rather than flustered." The situation is the trigger; the progress is the functional core; the outcome usually carries the emotional or social layer.
Three tests keep a statement honest. It should contain no product, feature or brand; if it does, it is a solution wearing a job's clothes. It should be stable over years, because jobs change far more slowly than the things hired to do them. And it should be specific enough that two people reading it would picture the same moment. "Manage my finances better" fails all three; it is vague, timeless in the wrong way and describes a wish rather than a situation.
Write several statements rather than one. A product is usually hired for a main job and a handful of related jobs, and some of the related ones are where the strongest messages live. Keep the statements with the research they came from, with a verbatim quote attached to each, so that a future writer can hear the customer rather than the summary.
Finding jobs through research
Jobs are found in stories, not in surveys. The most productive method is the switch interview: a long, open conversation with someone who recently bought, switched or cancelled, walked backwards from the moment of decision to the first thought. The questions are about what happened, what they tried, what they worried about, who else was involved and what finally tipped it. The interviewer resists asking what they want from a product, because people answer that question with feature lists copied from the market.
Listen for four things. The first thought: the moment the status quo stopped being acceptable. The workarounds: what they cobbled together before buying, which reveals the functional job. The anxieties: what nearly stopped them, which reveals the emotional layer. The audience: who they mentioned, which reveals the social layer. Patterns across a dozen or so interviews are more reliable than any single story. Interviews with people who moved from a rival also reveal when switching becomes possible, and the guide to winning customers who use a competitor turns those stories into timing, a lower-risk move and separate onboarding for switchers.
Quantitative sources then confirm and size what the interviews found. Search queries phrased as situations, support tickets, review text and sales-call notes all contain job language. The audience research guide covers the broader research toolkit, and the audience research for content guide shows how the same interviews feed a content plan directly.
Using jobs in positioning and content
A job statement is a positioning brief. The positioning guide needs a target, a frame of reference and a reason to believe; the job supplies all three. The target is whoever has the job; the frame of reference is whatever else gets hired for it, which is often not your product category; the reason to believe is proof that you do the functional job while relieving the emotional and social layers. Positioning against the job rather than against the category also explains why some categories feel crowded while the job itself is poorly served.
For content, the situation clause of each job statement is a topic list. Every "when" is a moment someone is searching, asking or scrolling, and content that names the moment outranks content that names the product. Headlines, ad copy and landing-page openings written in the customer's own job language convert better for a simple reason: the reader recognises themselves in the first sentence. The functional job becomes the body of the page, the emotional layer the tone, and the social layer the proof section.
Measurement follows the same shape. If a campaign is written to a job, the KPIA metric tied directly to an objective. for the campaign should be the progress the job describes, not only the click. A landing page built around a job should be tested on CVRShare of visits or clicks that convert. among people who arrive from job-language queries, and the longer test is whether customers acquired through a job message retain better and show higher LTVTotal value a customer brings over time. than those acquired through a feature message.
Worked example (illustrative)
An invoicing tool discovers its real job
A small invoicing tool for freelancers had positioned itself on speed: "send an invoice in 30 seconds". Growth had flattened at around 2,400 paying users, and the team ran 16 switch interviews with recent sign-ups and 9 with people who had cancelled. The functional job was as expected, but 19 of the 25 mentioned, unprompted, the discomfort of chasing late payers: the awkward email, the fear of damaging the relationship, the sense of looking unprofessional. The job statement became: "When a client is late paying and I need the money, I want to chase without sounding desperate or rude, so I can keep the client and keep my dignity." The team rewrote the homepage around that moment, built automated polite reminders with escalating tone, and ran a split test on paid search traffic for queries like "how to chase a late invoice". Over 6 weeks, the job-based page converted 4.1% of visitors to trial against 2.6% for the speed page, and trials from the job page converted to paid at 31% against 24%. Nothing about the product's speed changed.
Limits
Jobs-to-be-Done is strong on motivation and weak on everything else. It says little about how large a job's market is, how to reach the people who have it, what to charge, or how to compete once several products do the job well. Those questions still need segmentation, media planning and pricing work. The framework also depends on interview quality: a poorly run interview produces feature wish-lists dressed as jobs, and a statement built on those misleads more confidently than no statement at all.
Habit and brand loyalty are also under-explained. Many purchases are repeat hires made without any fresh consideration of the job, and a competitor who does the job better does not automatically get hired. Price can override everything. And in large organisations the "customer" is several people with different jobs, which the framework handles only if you write a statement for each role rather than one for the company.
Finally, the framework has several schools with different vocabularies, and the distinctions between them are of more interest to consultants than to marketers. Any version that produces a product-free, situational statement with functional, emotional and social layers will do the job this page describes.
The same thinking applied to customers who leave is covered in Jobs-to-be-Done for retention and churn, which uses switch interviews and the forces of progress to find the jobs a product has lost.
Common mistakes
- Writing the product into the job. "I want to use an app to track expenses" is a solution; the job is what tracking expenses gets the person.
- Stopping at the functional layer. The emotional and social layers are where most messages, and most switches, are decided.
- Asking what people want. Interviews that ask for wants produce feature lists; interviews that ask for stories produce jobs.
- One job per product. Most products are hired for a main job and several related ones, and the related ones often make the better campaign.
- Treating the job as a segment of people. The job belongs to a situation; the same person has it on some days and not others.
- Letting the statement drift into a wish. "Be more productive" is not a job. A job has a trigger, a piece of progress and a moment when it is done.
