The famous JTBD example is McDonald milkshakes. Christensen team found that customers "hired" milkshakes for the morning commute: something to drink, something to fill time, something to hold off hunger until lunch. The insight reshaped the product completely.
Jobs to be Done (JTBD) is a product and marketing framework developed by Clay Christensen and Tony Ulwick. It argues that customers do not buy products, they "hire" them to do a job. Understanding that job (the progress the customer is trying to make, in their life or business) is a more durable guide to product and marketing decisions than demographics or features. JTBD is used to interview customers, position products, and plan roadmaps around real customer motivation.
Six things to understand about JTBD: the core idea, where it came from, how to run a JTBD interview, how to apply it to product, how to apply it to marketing and sales, and the common misreadings.
JTBD says customers do not buy products. They hire them to make progress on a job: a goal they are trying to accomplish in their life or business. The job is what you solve. The product is the instrument. Features and demographics describe the instrument. The job describes the customer.
JTBD comes from two parallel traditions. Clayton Christensen (Harvard Business School) formalized it as "job-to-be-done theory" in books like "The Innovator Solution." Tony Ulwick (Strategyn) developed "Outcome-Driven Innovation" as a related method with more structured interview techniques. The two schools diverge in detail but share the core idea.
JTBD interviews focus on specific past purchases: what the customer was doing when they first thought about buying, what triggered the switch, who was involved, what alternatives they considered, what finally tipped them. The focus is on story, not opinion. "What were you doing when..." produces richer data than "what features matter."
Product decisions guided by JTBD focus on the progress the customer is trying to make. Features are evaluated by whether they help with the job. Roadmap priorities are decided by which jobs are most important and which are underserved. JTBD often leads to product decisions that look surprising from a demographic lens.
Marketing uses JTBD to position the product by the job it does, not the category label. "The CRM you hire to replace three subscriptions" is a job-focused position. "The best CRM for B2B" is a category-focused position. The first speaks to buyer motivation. The second speaks to a comparison matrix.
Many teams misinterpret JTBD as "add a goals section to the persona." That misses the point. JTBD is not a demographic descriptor. It describes progress the customer is trying to make, often across many personas. The same job (replace three subscriptions with one data model) can be shared by RevOps, founders, and CFOs.
JTBD recognizes three dimensions of any job. Products that solve all three win more consistently than products that solve only the functional dimension.
The practical task the product helps complete. "Track my pipeline." "Send a confirmation to a customer." "Reconcile two data sources." Functional jobs are what feature matrices measure. They are necessary but not sufficient. A product that solves only the functional dimension is often beaten by one that also solves emotional or social dimensions.
The feeling the customer wants to have while or after doing the job. "I want to feel in control of my pipeline." "I want to feel confident the message was sent." "I want to feel like my team is set up for success." Emotional jobs are what brand loyalty is built on. Products that get this right often outsell functionally superior competitors.
How the customer wants others to see them. "I want to be perceived as a data-driven leader." "I want my team to see me as competent." "I want to look responsible to my CFO." Social jobs are what underlies status purchases, enterprise vendor selection ("nobody got fired for buying X"), and visible brand choices.
A SaaS product that lets a manager hit their forecast (functional), feel confident in pipeline reviews (emotional), and look rigorous to the CFO (social) wins consistently against products that solve only the functional dimension. The three jobs often reinforce each other in a successful positioning.
Products built purely from a feature matrix (functional only) often underperform. Buyers choose the alternative that feels better even if the matrix says it should lose. Teams running pure functional positioning tend to lose head-to-head to competitors who tapped into emotion or social dimensions.
B2B purchases are often framed as rational, but the buyers are humans with careers and anxieties. The anxious CFO buying from the "safe" vendor is making an emotional choice. The ambitious VP picking the innovative vendor is making a social one. B2B JTBD applies even when the deal looks like a straight ROI calculation.
JTBD interviews follow a specific structure called the "switch interview," designed by the Rewired Group. The structure reveals the push, pull, anxiety, and habits around a specific past purchase. Four phases guide the conversation.
Start with the first moment the customer thought about buying. What were they doing. What triggered the thought. Who was there. The question anchors the conversation in a specific past moment rather than in general opinion. The answer is often surprising and reveals the real push.
Explore the push forces (what was making the current situation uncomfortable) and the pull forces (what was promising about the new option). Push forces are usually underweighted by vendors. Products that acknowledge the push ("you are tired of reconciling data across three systems") land harder than products that lead with the pull.
What anxieties did they feel about switching ("what if the migration breaks something"). What habits worked against the change ("we have always used this tool"). Products that preempt the anxiety and provide a soft break from the habit convert at higher rates. Many JTBD interviews reveal that anxiety, not price, is the real reason buyers delay.
Which specific interaction or data point tipped the decision. A specific demo moment. A specific review. A specific recommendation. The moment is often not what the vendor expects. Patterns across many interviews reveal what actually closes deals, which rarely matches the top of the marketing deck.
Each interview covers one specific past purchase, not multiple vendors. Two interviewers (one asking, one taking notes) reduces missed detail. The interview lasts 60 to 90 minutes. The data is qualitative but rich. Patterns emerge after 8 to 12 interviews on a given topic.
JTBD interviews deliberately avoid "what features do you want." That question produces wish lists that do not predict buyer behavior. The interview focuses on what the customer actually did, which is a more reliable predictor of what they will do again. Opinion data is auxiliary.
JTBD outputs are useful across the organization. Four applications are common. Each one changes a specific decision the team was making from gut feel into data-informed judgment.
The product team ranks features not by internal votes but by which jobs they help with. Underserved jobs (that buyers care about but no vendor solves well) are top priority. Overserved jobs (many vendors already solve) are low priority. Roadmap decisions become about progress for buyers rather than clever features.
Marketing writes positioning that leads with the job: "The CRM you hire to replace three subscriptions." The buyer sees themselves in the frame immediately. The alternative ("the leading all-in-one CRM for B2B SaaS") is a category position that works harder for less reward.
Sales discovery pivots from feature-centric questions ("do you need custom objects") to job-centric ones ("what progress are you trying to make"). Reps who ask JTBD-style discovery questions get richer context. The resulting proposals land harder because they speak to the real buyer motivation.
JTBD informs pricing by anchoring it to the value of the progress the customer makes. A product that lets a team hit their forecast is worth more than a product that merely tracks activity, even if both have similar feature matrices. Value-based pricing often emerges from JTBD research.
Strkr unifies CRM, marketing, messaging, projects, and docs on one data model. Published pricing, mobile parity, custom objects on day one. Starter at $29, Pro at $59, Scale at $119 per seat per month.
Jobs to be Done (JTBD) is a product and marketing framework developed by Clay Christensen and Tony Ulwick. It argues that customers do not buy products, they hire them to do a job: a goal they are trying to make progress on. Understanding the job is a more durable guide to product and marketing decisions than demographics or feature lists.
A manager hires a CRM to feel in control of their pipeline during Monday reviews. A founder hires a payments platform to look responsible to the board about financial controls. A CFO hires a SaaS vendor to replace three subscriptions and save the integration cost. The job describes the progress, not the feature.
Personas describe who the buyer is (demographics, role, size). JTBD describes what progress they are trying to make. The same JTBD can span many personas. The same persona can have different JTBDs in different contexts. Mature teams use both. Personas tell you who to talk to. JTBD tells you what to say.
Follow the switch interview structure: focus on one specific past purchase, ask about the first thought that led to buying, explore push and pull forces, probe anxieties and habits that resisted the change, and nail down the decision moment. Two interviewers, 60 to 90 minutes. Patterns emerge after 8 to 12 interviews on a given topic.
Functional (the practical task the product helps complete), emotional (how the customer wants to feel), and social (how the customer wants to be perceived). Products that solve all three win more consistently than products that solve only the functional dimension. B2B purchases have all three even when they look purely rational.
Clay Christensen (Harvard Business School) formalized the theory in books like "The Innovator Solution." Tony Ulwick (Strategyn) developed Outcome-Driven Innovation as a related, more structured method. Bob Moesta and others at Rewired Group developed the switch interview technique. The schools diverge in detail but share the core idea.
Discovery pivots from feature-centric questions ("do you need custom objects") to job-centric ones ("what progress are you trying to make"). Proposals land harder because they speak to buyer motivation, not product capability. Enablement content maps features to the jobs each one helps with, so reps can tell the right story in the right conversation.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
