Jobs to Be Done is a framework that defines a product by the progress a buyer is trying to make, rather than by the buyer’s demographics or the product’s feature list.
What is Jobs to Be Done?
Jobs to Be Done is a framework that defines a product by the progress a buyer is trying to make. The organizing question isn’t who the buyer is or what the product does. It’s what the buyer was trying to accomplish when they went looking.
The framework’s standard phrasing is that people don’t buy a quarter-inch drill, they buy a quarter-inch hole. The B2B version is less tidy and more useful: a VP of Marketing doesn’t buy an analytics platform, she buys the ability to walk into a board meeting with a number she can defend.
Why Jobs to Be Done matters
Most B2B messaging describes the platform. The buyer is trying to solve a problem. That gap is the single most common finding in messaging work, and Jobs to Be Done is the framework that closes it.
It matters commercially because the job defines the real competitive set. If the job is defending a number to a board, your competition isn’t only other analytics vendors. It’s a spreadsheet, an agency’s monthly deck, and doing nothing. Companies that benchmark against the wrong competitive set build messaging that answers questions nobody asked.
How Jobs to Be Done works
You start from the moment of switching. Something changed in the buyer’s situation that made the old approach untenable, and that trigger is more diagnostic than any demographic attribute.
From there the framework asks what progress the buyer wanted, what they tried first, what made them abandon it, and what they were anxious about when considering the alternative. The output is a job statement, usually structured as a situation, a motivation, and an expected outcome.
Jobs to Be Done versus personas
A persona describes who the buyer is. A job describes what they’re trying to do. The two aren’t opposed, but they answer different questions and one of them is more actionable.
Personas drift toward demographic detail that doesn’t change a single word of the copy. Knowing the buyer is a 42-year-old VP who reads industry newsletters tells you nothing about what to say. Knowing she needs to defend a budget line she inherited and doesn’t trust tells you everything.
The sharper distinction: two buyers with identical personas can have different jobs, and two buyers with nothing demographic in common can share one. The job predicts behavior. The persona predicts the stock photo.
Functional and emotional dimensions
A job has a functional dimension, which is the practical outcome, and an emotional one, which is how the buyer needs to feel or be seen. B2B treats the second as soft and then loses deals to it.
The emotional dimension in B2B is usually about risk to the buyer personally. Nobody got fired for the safe choice. A messaging strategy that addresses only the functional job leaves the career-risk question unanswered, and that question is frequently what stalls the deal in committee.
Jobs to Be Done and messaging
Once the job is articulated, messaging has a test it can fail. Does this headline describe the progress the buyer wants, or does it describe our architecture?
The messaging friction that shows up in audits is almost always this: copy written from the inside out, describing what was built rather than what it lets someone do. The job statement is the reference document that makes the problem obvious.
How to find the job
- Interview recent buyers about the weeks before they started looking, not about the product.
- Ask what they tried first and why it stopped working.
- Ask what nearly stopped them from buying, which surfaces the anxiety the messaging has to address.
- Read lost-deal notes for the language prospects used before your category vocabulary got imposed on them.
- Look at the search and prompt phrasing that brings people to you, which is unfiltered job language.
Jobs to Be Done and content strategy
A content calendar organized by topic produces coverage. A calendar organized by job produces a sequence, because a job has stages: recognizing the problem, surveying approaches, evaluating options, justifying internally.
This also maps cleanly onto query intent. The questions a buyer asks early in a job are informational and the ones they ask late are comparative, and a page that answers the wrong stage well still converts badly.
Common mistakes
Writing the job as a feature in disguise. If the job statement contains your product category, you’ve described what you sell rather than what the buyer wants.
Defining the job too narrowly, which rebuilds the persona problem at a different level of abstraction. Defining it too broadly produces a statement so general it can’t discriminate between a good message and a bad one.
Treating it as a one-time workshop. Jobs shift as markets and buying committees change, and a job statement written three years ago may describe a trigger that no longer occurs.
How MSMC approaches Jobs to Be Done
We use it as the input to messaging work rather than as a standalone deliverable. The job statement is what the Messaging Friction Audit scores against, because the audit’s core question is whether your messaging describes your platform or your buyer’s problem.
The research step is buyer interviews focused on the switching moment, supplemented by the actual query and prompt language bringing people to the site. That language is unmediated by anyone’s category vocabulary, including ours.
FAQ
What is the Jobs to Be Done framework?
A way of defining a product by the progress a buyer is trying to make rather than by buyer demographics or product features. The organizing question is what the buyer was trying to accomplish when they went looking.
How is Jobs to Be Done different from a buyer persona?
A persona describes who the buyer is; a job describes what they’re trying to do. Two buyers with identical personas can have different jobs, and the job is the one that predicts behavior and dictates copy.
Does Jobs to Be Done work for B2B?
Yes, and the emotional dimension matters more than B2B usually admits. Much of the B2B job is about personal risk to the buyer, which is frequently what stalls a deal in committee.
How do you identify a job to be done?
Interview recent buyers about the weeks before they started looking: what changed, what they tried first, why it failed, and what nearly stopped them from buying. Search and prompt language is a useful second source.
How does Jobs to Be Done improve messaging?
It gives messaging a test it can fail. Once the job is written down, you can ask whether a headline describes the buyer’s progress or your own architecture, and the answer stops being a matter of taste.
Key takeaways
- Jobs to Be Done defines a product by the progress a buyer wants, not by demographics or features.
- The job defines the real competitive set, which often includes spreadsheets and doing nothing.
- A persona tells you who the buyer is; a job tells you what to say.
- The emotional dimension in B2B is usually personal career risk, and ignoring it stalls deals in committee.
- A written job statement gives messaging an objective test instead of a taste argument.
- Jobs shift over time, so a statement written years ago may describe a trigger that no longer happens.
Browse more definitions in the MSMC glossary.
Understanding this term is the starting point. To find out whether AI systems actually recognize and cite your company on this topic, run an AI visibility audit. For a detailed look at where your messaging breaks down in the buying process, see the Messaging Friction Audit.