People do not buy products. They hire something to make progress in a situation they are stuck in, and they fire whatever they were using before. Jobs to Be Done is the discipline of finding that progress and building around it instead of around your own features. Done well, it tells you what to make, who to make it for, and how to talk about it.
The job is the progress, not the product
A job is the change a person is trying to bring about. Theodore Levitt’s old line still carries it: nobody wants a quarter-inch drill, they want a quarter-inch hole. Clayton Christensen pushed the idea further with the milkshake study, where the surprising finding was that a large share of milkshakes were “hired” for a boring morning commute. The job was not “enjoy a treat.” It was “keep one hand busy and stay full until lunch without making a mess in the car.” Reframing the milkshake around that job changes the product, the price, and the place it sits on the menu.
The unit of analysis matters. A job is stable over time even as the products that serve it churn. People have wanted to send a message reliably for centuries. The hired solution moved from courier to post to telegram to email to chat, but the underlying job barely shifted. When you anchor strategy to the job rather than the current product category, you stop being surprised by your real competition.
Your competition is not the company that looks like you. It is whatever the customer hires instead, including doing nothing at all.
That last point gets missed constantly. For most products the strongest competitor is inertia: a spreadsheet, a workaround, or simply living with the problem. If your strategy only accounts for named rivals, you are ignoring the option most customers actually choose.
Functional, emotional, and social dimensions
Every meaningful job has three layers, and weak research only captures the first.
The functional layer is the practical task. Reconcile the invoices. Get to the airport. Find a contractor who answers the phone.
The emotional layer is how the person wants to feel along the way, or stop feeling. Stop dreading month-end close. Feel competent in front of the finance team. Not worry that something is quietly broken.
The social layer is how they want to be seen by others. Look organized to the board. Be the person who picked the tool that worked. Avoid the embarrassment of championing something that failed.
Products that win usually serve all three. A budgeting app that balances the numbers but leaves people feeling judged has solved the functional job and lost on the emotional one. When you map a job, write all three layers down explicitly. The functional layer tells you what to build. The emotional and social layers tell you how to position it and what will actually drive the switch.
The four forces of progress
The most useful diagnostic in JTBD is the forces that govern whether someone switches. Picture a tug of war.
Two forces push toward change. Push is the dissatisfaction with the current situation: the spreadsheet broke again, the old vendor raised prices. Pull is the attraction of the new solution: this thing promises to fix exactly that.
Two forces hold people back. Anxiety is the fear of the new: will it actually work, will switching be painful, will I look foolish if it fails. Habit is the comfort of the present: the current way is annoying but known, and known is safe.
A switch happens only when push and pull together beat anxiety and habit. Most teams pour everything into pull by adding features and louder claims. That is the smallest lever. The faster wins usually come from reducing anxiety, with proof, guarantees, migration help, and a credible first step, and from acknowledging the push the customer already feels. If you only sell the upside and never address the fear of changing, you lose deals to inertia and never see why.
How to actually find the job
You do not find jobs in a survey. You find them by reconstructing real decisions in detail. The core method is the switch interview, where you talk to someone who recently bought or changed solutions and walk backward through the timeline of their decision.
A workable sequence:
- Recruit recent switchers. Talk to people who made a real purchase or change in the last few months, while the memory is fresh and the reasons are concrete. Avoid hypotheticals about what people might do.
- Build the timeline. When did the thought first occur? What was happening that day? What did they try first? Anchor every answer to a moment, not a generality. “What set this off?” beats “what features do you want?”
- Hunt for the four forces. Listen for the push that started the search, the pull that drew them in, the anxiety that slowed them down, and the habits they had to break. The richest material is in the hesitation.
- Note the hiring and firing criteria. What made them finally commit? What did they stop using, and why? The thing they fired tells you who you really compete with.
- Separate the job from the solution. Strip the product language out of their account until you are left with the progress they wanted. That sentence is the job.
Ten to fifteen of these interviews on a single switch will surface clear patterns. You are not after statistical weight here. You are after the causal mechanism: the specific chain of events that turns a vague annoyance into a purchase.
This is also where JTBD and persona work reinforce each other. Demographics describe who someone is; the job describes what they are trying to get done. Build customer personas that teams actually use on top of jobs, not the other way around, and they stay grounded in behavior instead of decorating a slide.
Turning jobs into strategy
The insight is worthless until it changes a decision. Three places it should bite.
Product. Score features against the jobs they advance. A feature that serves a real, underserved job earns priority. A feature that serves no job, however clever, is a candidate to cut. The job statement becomes the filter for a roadmap that would otherwise be run by whoever argues loudest.
Messaging. Sell the progress, in the customer’s words. The phrases you collect in switch interviews are the raw material for a value proposition that actually sells. When the headline names the job and the emotional payoff, prospects recognize themselves. When it lists features, they have to translate, and most will not bother.
Positioning. Your category and your differentiation both flow from the job. If customers hire you instead of a spreadsheet, your real argument is against the spreadsheet, not against the venture-backed rival nobody in the room has heard of. JTBD keeps brand positioning honest by tying it to the choice customers genuinely make.
The common trap is treating JTBD as a one-time workshop. Jobs are stable, but which jobs you choose to serve, and how well you serve them, is a live decision. Revisit the interviews when you enter a new segment or when win rates drift for reasons the dashboard cannot explain.
How Strynal approaches Jobs to Be Done
We treat the job as the foundation of the work, not a deliverable that gets filed away. Every engagement starts on a blank page, so before we name a category or draw a homepage, we reconstruct the decisions real customers made and the progress they were chasing. The team that runs those interviews is the team that turns them into positioning and product priorities, which means nothing gets lost in a handoff between the people who learned it and the people who use it.
That continuity is the point. Jobs thinking only pays off when the same understanding shapes the strategy, the message, and the build. If you are trying to work out what customers actually hire you for, our strategy and positioning work is built around exactly that question. Start a conversation and tell us where the current story stops landing.