Jobs-to-be-Done Positioning Framework

What it is

A positioning approach grounded in the idea that customers don't buy products: they hire products to get jobs done. Originated by innovation researcher Tony Ulwick and later popularised by Harvard Business School professor Clayton Christensen and strategist Bob Moesta, JTBD positioning focuses on the job (the outcome the customer wants to achieve), the context (the circumstances that trigger the need), and the competing solutions (including non-product alternatives). Instead of asking "who is our customer?", JTBD asks "what job are they trying to do?" The shift matters because customer segments, defined by firmographic or demographic profile, can change from year to year, while the underlying job a customer is trying to accomplish is often far more stable. This is why JTBD positioning tends to age better than persona-based positioning built purely on job titles or company size.

When to use it

• When your target market is fragmented or your product serves multiple use cases
• When you need to understand why customers choose your product over alternatives, including doing the work manually
• When existing competitive positioning feels generic or doesn't explain actual customer behaviour
• For new categories or products where traditional positioning frameworks don't fit
• When you want messaging that focuses on customer outcomes rather than product features
• When churn analysis shows customers leaving for a "job" reason (they stopped needing to do the job, or found an entirely different way to do it) rather than a feature gap
• When onboarding data shows customers using the product for a purpose the team didn't originally design for; a signal that the real job differs from the assumed one

Ownership

At a scaled company, a Head of Product Marketing owns the finished job statement and messaging hierarchy, typically working with a Product Manager or UX researcher who runs the switch interviews and contributes job-mapping data. A solo or founding PMM conducts the interviews and writes the job statement alone, pulling directly from support tickets and sales calls rather than commissioning separate research. Interview execution can sit with a researcher or PM at a larger company, but interpreting results into a positioning decision should stay with PMM, since it is the function accountable for how the job becomes external messaging.

How to apply it

1. Identify the Core Job: Describe the job in terms of the outcome, not the tool. Example: "Get my team aligned on project priorities" (not "use project management software"). Write the job as a verb plus object plus context, a structure borrowed from Ulwick's "outcome-driven innovation" method, so it stays tool-agnostic even as the market's tools change.
2. Define the Functional, Emotional, and Social Dimensions: What does the customer want to accomplish (functional)? How do they want to feel (emotional)? What do they want others to perceive (social)? Most positioning stops at the functional dimension, which is also the easiest for competitors to copy. The emotional and social dimensions are frequently where lasting differentiation lives, because they are harder to observe and harder to replicate.
3. Map the Context: When and why does this job become urgent? What triggers the need? Is it seasonal? Event-driven? Ongoing friction? Distinguish between the job itself, which may be constant, and the trigger, which is the specific moment it becomes urgent enough to act on; messaging aimed at the trigger moment converts far better than messaging aimed at the general, ongoing job.
4. Identify Competing Solutions: What would customers do if your product didn't exist? Spreadsheets? Manual tracking? Competitor products? Outsourcing? Understanding the competitor (often not your direct rival) is key. In most JTBD research, "do nothing" or "keep doing it manually" turns out to be the largest single competitor by market share, even though it never appears in a competitive battlecard.
5. Articulate the Switch: What would make a customer switch from their current solution to yours? What pain point in their current approach does your product eliminate? Map the switch as a four-forces exercise (push from the old way, pull towards the new way, anxiety about the new way, and habit or attachment to the old way); a compelling push and pull can still lose to high anxiety or strong habit if you don't address them directly in messaging and onboarding.
6. Test with Customers: Interview users about the job they're trying to do. Are they describing the same job you identified? If not, refine. Use "switch interviews," structured conversations with customers who recently bought, that walk backwards from the purchase moment to the first moment they realised the old way wasn't working; this timeline reveals the actual job far more reliably than a features-based survey.
7. Build the job map into a messaging hierarchy: Once validated, order your messaging so the functional job comes first (what it does), the emotional and social jobs reinforce it (how it feels, how it looks to others), and named competing solutions, including manual alternatives, are addressed explicitly in objection-handling materials for sales.