Segmentation often starts with who customers are: industry, age, role, income, company size. Those variables are convenient, but they rarely explain choice. Customers buy when a situation triggers a desire for progress and when an option feels safe, worth it, and easy enough to adopt. Jobs-to-be-done (JTBD) is the discipline of describing demand in those terms. It shifts marketing from describing audiences to understanding moments.
Need states extend the same idea. They describe recurring contexts and motivations that make customers receptive to specific kinds of value. Two people can share a demographic segment and still be in different need states, and the same person can move across need states over time. When you map jobs and need states, you can design offers, messaging, and journeys that fit real decision processes rather than abstract personas.
What Jobs-to-Be-Done Really Means
JTBD begins with a simple claim: customers “hire” products and services to help them make progress in a specific situation. The job is not the product; it is the progress. A drill is hired to create a hole, but the deeper job may be to organize a space, reduce stress, or feel competent. The deeper you go, the clearer you get on what customers truly value and what they will pay for.
Job: the progress a customer is trying to make in a particular context, including outcomes they want and constraints they must manage.
Situation: the trigger and context that create motivation to change. The same customer can hire different solutions in different situations.
Progress: movement from a current state to a desired state, often combining functional, emotional, and social outcomes.
JTBD is especially useful for understanding switching and non-consumption. Customers switch when the current solution fails the job often enough, a new option lowers the risk and effort of change, and the choice can be justified to others. And many markets look smaller than they are because customers are “hiring” substitutes such as spreadsheets, manual workarounds, personal relationships, or “do nothing.” Those substitutes are often the real competitor because they feel safe and familiar.
Writing Job Statements That Guide Decisions
JTBD becomes powerful when job statements are concrete enough to guide product priorities, messaging, and channel choices. The discipline is to include context and constraints and to avoid embedding a solution.
Job statement: When I am in this situation, I want to make progress, so I can achieve this outcome, without these costs or risks.
Example: “When I inherit a workflow I don’t fully trust, I want to validate results quickly, so I can make a decision with confidence, without spending days chasing inputs or risking an embarrassing mistake.” That statement suggests product requirements (transparency, validation), messaging (confidence, speed), and proof needs (accuracy, references).
Two tests keep job statements useful. Specificity test: can different teams interpret it the same way and design consistent priorities? Switching test: does it explain what would make someone change behavior and what would stop them?
Jobs are also hierarchical. Under a “big job” are sub-jobs like discovering options, reducing uncertainty, securing approval, implementing, and recovering from failures. Mapping sub-jobs prevents teams from misdiagnosing friction. A low conversion rate is often the sub-job “reduce risk” failing, not the sub-job “see more ads” failing.
Functional, Emotional, and Social Jobs
Most organizations over-index on functional value and underweight how customers feel and what the choice signals. JTBD makes these dimensions explicit.
Functional jobs: what the customer is trying to accomplish in practical terms, such as saving time, improving accuracy, or increasing throughput.
Emotional jobs: how the customer wants to feel, such as confident, relieved, in control, or proud. Anxiety and fear of regret are common adoption blockers.
Social jobs: how the customer wants to be seen by others. In B2B, this often shows up as career risk: “Will this make me look smart, or will it expose me if it fails?”
These dimensions explain why brand and proof create pricing power. A trusted option can win even when functional differences are small because it reduces anxiety and blame risk. They also explain messaging effectiveness. If the real barrier is fear of making a mistake, “more features” rarely converts. Proof and safety convert.
Need States: The Market as Moments
Need states describe recurring contexts and motivations that shape what customers want and how they choose. They are time-bounded demand pockets defined by a trigger, urgency, mindset, and constraints.
Need state: a situation in which a customer is receptive to a specific kind of value because the job has become salient.
In practice, need states often vary by three variables. Urgency: how immediate the job is. Risk: how costly it feels to be wrong. Effort tolerance: how much complexity the customer will endure. These variables shape what message works, what proof is required, and what pricing feels fair.
Need states also clarify channel choices. Search often maps to high-intent problem-solving need states. Social feeds often map to curiosity and identity-driven need states. Referrals and communities often map to trust-seeking states. Mapping the need states to channels stops you from forcing the same message into every environment and then blaming “the channel” when results differ.
Research Methods for Discovering Jobs and Need States
Jobs and need states are discovered through real decisions, not brainstorming. A strong starting point is to study recent switchers because they reveal triggers, alternatives, and trade-offs clearly.
Switch interviews: reconstruct the timeline. What triggered the search? What alternatives were considered? What objections nearly stopped the decision? What made the chosen option feel safe? What would have prevented the switch?
Observation: watch evaluation, purchase, onboarding, and renewal. Notice where customers pause, what they re-read, and what they avoid. Many need states are visible in behavior even when customers don’t name them.
Language mining: analyze sales calls, support tickets, reviews, and community posts to capture customer phrases that express jobs, fears, and desired outcomes. Those phrases often become the most effective messaging because they match the customer’s mental model.
Two cautions matter. First, customers describe outcomes more reliably than causes; treat qualitative findings as hypotheses about mechanisms. Second, jobs tend to be stable, but need states can be seasonal; sample across contexts so you know what is durable.
Quant validation: once you have job hypotheses, validate scale and impact. Use surveys that force trade-offs, analyze search queries and site behavior to see which jobs drive high intent, and segment cohorts by first-use case to see which jobs predict retention. The goal is to separate “interesting” jobs from “important” jobs, and to quantify which jobs are worth building a dedicated proposition around.
Competitive contrast: map alternatives job-by-job. Competitors often win not because they are better overall, but because they do one sub-job—setup, support, proof, approval—more reliably. This map produces practical priorities: a messaging fix when customers misunderstand, a product fix when customers can’t reach the first win, or an offer fix when risk remains too high.
Translating Jobs into Segmentation, Positioning, and Offers
JTBD pays off when it changes decisions. The most direct translation is to refine STP around jobs and need states. Instead of targeting “midmarket operations leaders,” you might target “teams under pressure to increase throughput without adding headcount.” The target becomes a demand pocket, not a demographic label.
Jobs-based segmentation: groups customers by progress sought and context. It often reveals similarities across industries and demographics, enabling clearer and more scalable messaging.
Positioning: becomes sharper when tied to a job: “For this job in this context, we deliver this outcome better than alternatives, and here is the proof.” Jobs also clarify trade-offs. If the job values speed, “fastest time-to-value” can be a credible position even if it sacrifices extreme customization.
Offer design: should address the sub-jobs that block adoption. If a key sub-job is “justify the decision,” include business-case framing and references. If a key sub-job is “reduce risk,” include trials, guarantees, migration support, and transparent terms. Many “conversion problems” are really “risk problems.”
Need states also inform packaging and pricing. High-urgency contexts can justify higher prices for speed and support. Low-urgency contexts often require low-friction entry points such as trials, freemium, or educational content that helps customers self-diagnose.
Prioritization: not every job deserves equal investment. A practical ranking considers frequency (how often the job occurs), intensity (how painful it feels), value (willingness to pay or economic impact), and win-ability (whether you can deliver a meaningfully better solution). High-frequency, high-intensity jobs with clear willingness to pay are typically the best beachheads.
Job-based experiments: can reduce uncertainty quickly. Test job-led landing pages versus feature-led pages. Test proof types that match the job’s risk profile, such as references, guarantees, or demos. Then measure not only conversion, but activation and early retention by job segment to ensure you are attracting the right customers.
Translating Jobs into Messaging and Content
JTBD improves communications by clarifying what to say first. Customers want to know whether you understand their situation and whether you can help them make progress.
Message sequencing: lead with the job and outcome, address the biggest risk in that context, provide proof, then make the next step easy. If the job is anxiety-driven, show proof and safety early. If the job is effort-sensitive, emphasize simplicity and time-to-value.
Content strategy: can be organized around jobs. Early content helps customers name the job and understand what “good” looks like. Mid-stage content helps reduce uncertainty through comparisons and proof. Late-stage content helps justify the decision, implement, and succeed. This creates a compounding library instead of a random assortment of topics.
Jobs also help you communicate to buying committees. Different stakeholders have different jobs: users want ease, managers want predictability, finance wants control, and compliance wants safety. A job lens lets you tailor proof without fragmenting the core promise.
Creative guidance: jobs provide the content of creative briefs. The brief becomes a belief shift: what the customer believes today that keeps them stuck, what they must believe to take the next step, and what proof will make that belief change. This keeps creative aligned to decision mechanics rather than to internal preferences.
Pitfalls and How to Avoid Them
JTBD can be misused. One pitfall is making jobs too broad. “Be more productive” is not a job; it is a wish. The fix is context: specify the situation and constraints.
Another pitfall is ignoring economics. A job can be real and still be unprofitable to serve at your current cost structure. Link jobs to willingness to pay and cost-to-serve before scaling.
A third pitfall is underestimating inertia. Even when the job is important, customers may stick with workarounds because they are “good enough.” The fix is adoption design: reversible trials, clear migration, and early wins that reduce the psychological cost of change.
Jobs-to-be-done and need states help marketing return to first principles: customers buy progress in context, under constraints, with motivations that are both functional and human. When you design around that reality, segmentation sharpens, positioning becomes more credible, content becomes more useful, and growth becomes less dependent on channel tricks.
Operating habit: revisit your job map whenever performance shifts. Rising CAC, slower sales cycles, or higher churn often signal that the dominant job or need state has changed, or that competitors improved on a sub-job you used to own. Updating the map keeps strategy grounded in reality and prevents drift into channel chasing.
- Job clarity: Can we name the situation, the desired progress, and the main constraint in one sentence?
- Proof fit: Do we have reasons to believe that match the job’s risk and accountability?
- Offer safety: Is adoption reversible enough to overcome inertia and switching fear?
- Time-to-value: Can customers reach the first meaningful win quickly in this job context?
- Economics: Do CAC, retention, and margin work for the job-driven segment we’re targeting?
