Product Jobs vs. Core Jobs: A Practitioner’s Guide to Better Discovery Interviews

If you’re new to Jobs-to-be-Done (JTBD), here’s the big idea: customers don’t really “buy products,” they “hire” them to help get a job done. That job might be functional, like monitor water quality or keep my floors clean. It might also be emotional, like feel confident in my appearance or be reassured that I’ve made the right decision.

In JTBD, we take the customer’s perspective seriously. Instead of focusing on product features, we focus on what people are actually trying to accomplish in their world. That mindset gives us a sharper lens for innovation.

But here’s where things often go sideways in Discovery Interviews: customers talk about both the job they’re trying to accomplish and their product experiences, often in the same sentence. If we don’t consciously separate the two, we risk blending them together into one messy pile of data. That leads to distorted insights and misdirected innovation.

This distinction is not just theoretical. It’s embedded in New Product Blueprinting, the leading B2B voice-of-customer methodology, and it’s a central idea in my book The Jobs-to-be-Done Pyramid™: An Innovation Architecture for Humans: Linking Function, Identity, and Emotion. In the Pyramid, Product Jobs occupy Level 1, while Core Jobs sit at Level 2. Let’s understand the difference!

The Core Difference

Product Jobs (Level 1) are the solution-dependent tasks customers perform across a product’s lifecycle. They’re about interacting directly with the product: acquiring it, preparing it, using it, maintaining it, and eventually disposing of it. Examples include installing a water sensor, cleaning a coffee machine, updating software, or returning a purchase of a product. In each case, these statements refer to a product. When the product changes, these jobs change too.

Core Jobs (Level 2) are the underlying, solution-independent goals customers ultimately care about: monitor water quality, ensure patient safety, keep a home clean, manage financial risk. These persist regardless of the product being used.

The tricky part is that customers rarely distinguish between them. A surgeon might say: “It takes me too long to set up the ultrasound machine before I can evaluate the trauma patient.” That one sentence contains both: a Product Job (setup) and a Core Job (evaluation). Both matter, but they belong to different categories.

Why Separation Transforms Interviews

When customers move fluidly between “what they do with the product” and “what they’re trying to accomplish,” it’s our responsibility as interviewers to sort their words. This isn’t just about organization, it’s about uncovering different types of innovation opportunities that would otherwise blur together.

Product Jobs spotlight practical frictions that customers experience throughout the lifecycle: installation headaches that delay project timelines, maintenance hassles that create recurring costs, or disposal burdens that leave customers frustrated long after purchase. These are immediate, observable pain points that directly relate to product interaction.

Core Jobs reveal a different category of frustrations, those around outcomes and strategic goals. When customers can’t achieve efficiency targets, miss critical deadlines, or feel they lack control over important processes, these failures often trace back to gaps in how well the product supports their fundamental objectives.

Without proper separation, everything collapses into a single undifferentiated list that obscures patterns and priorities. But when we tag them appropriately, relationships emerge. For instance, recurring Product Job frictions like slow setup procedures or unreliable maintenance protocols often cascade into Core Job failures such as delayed treatments or wasted resources. This cause-and-effect clarity is impossible to see when both levels are mixed together.

The separation also transforms how we build job maps. Combine both levels into one map, and you’ll get a confusing tangle that serves no one well. Keep them distinct, and each map tells a coherent story: one shows the product lifecycle journey, the other shows the broader process the customer is trying to accomplish. When you eventually connect the two maps, you can pinpoint exactly where Product frictions undermine Core outcomes, and that’s where breakthrough innovations often hide.

Strategic Implications for Blueprinting

Getting this distinction right at the start of a Blueprinting project determines everything that follows. The fundamental question shapes your entire approach: Are you innovating at the Core Job level, say, helping physicians get rapid, accurate imaging results that improve patient outcomes? Or are you focusing on Product Jobs, making ultrasound machines easier to acquire, set up, and maintain throughout their operational life? Both approaches are valid and valuable, but they call for different strategies, success metrics, and organizational teams.

This choice extends directly to market definition, which is one of the most critical early decisions in any innovation project. If you define your market in narrow Product Job terms, you are, by definition, looking to improve your current product, which is fine, but it’s a decision that should be made explicitly.

This is a solid strategy, but we should also keep some of our portfolio focused on Level 2 Core Jobs. For example, Blockbuster defined themselves as being “in DVD rentals.” This was a strategy that worked until it didn’t. 

Product Job framing alone that left them vulnerable when streaming eliminated the need for physical media entirely. Netflix defined themselves as helping people “be entertained at home,” a Core Job framing that left room to expand across multiple solution categories.

As I describe in The Jobs-to-be-Done Pyramid™, the way you categorize jobs is not just semantic precision, it fundamentally determines how you frame opportunities, scope projects, and set the strategic direction for your entire innovation portfolio. Teams that get this wrong early often spend months heading in directions that ultimately prove too narrow or unfocused.

The implications ripple through portfolio decisions as well. Organizations suffer when teams over-index on one level at the expense of the other. Focus only on Core Jobs, and you may develop breakthrough solutions that customers can’t actually adopt because basic usability barriers block implementation. Focus only on Product Jobs, and you may optimize today’s tasks while completely missing tomorrow’s market-shaping opportunities that redefine customer expectations.

Balanced portfolios systematically draw from both levels. Product Jobs typically generate opportunities that engage product teams, engineering groups, and customer support operations, the functions responsible for immediate user experience. Core Jobs fuel innovation initiatives that involve R&D, strategic planning, and merger-and-acquisition teams, the functions responsible for longer-term market positioning, and those untethered from current product forms. Organizations that manage this balance effectively sustain both current adoption rates and future growth potential.

Learning from Market Disruptors

Some of the most instructive examples come from companies that achieved massive disruption by innovating at the Product Job level while leaving Core Jobs essentially unchanged. Uber provides a perfect illustration: the fundamental Core Job of urban transportation, “get from A to B safely and efficiently,” remained exactly the same. What Uber revolutionized were the Product Jobs surrounding that experience: calling for transportation, waiting for pickup, handling payment, and managing receipts. By reimagining these Product Jobs through smartphone apps and integrated payment systems, they didn’t just improve convenience, they redefined customer expectations across the entire transportation industry.

Amazon followed a strikingly similar pattern in retail. The Core Job, “obtain goods I need when I need them,” stayed constant throughout their rise. What Amazon transformed were the painful Product Jobs that had frustrated customers for decades: browsing selection, placing orders, tracking shipments, and handling returns. One-click purchasing eliminated ordering friction, while their no-hassle return policy removed the traditional risk of buyer’s remorse. These Product Job innovations created competitive advantages that traditional retailers struggled to match.

Dyson took the same approach with home cleaning. The Core Job of “keeping floors clean and presentable” existed long before their innovations and remains unchanged today. But Dyson systematically addressed neglected Product Jobs that other manufacturers had accepted as unchangeable: replacing vacuum bags that reduced suction over time, dealing with clogged filters that required messy cleaning, and managing dust clouds that escaped during disposal. By eliminating these Product Job pain points, Dyson carved out a premium market position in what had been a commodity category.

Other disruptors found success by innovating at the Core Job level instead. Spotify transformed the Core Job from “own music I like” to “discover music I’ll enjoy,” fundamentally changing how people think about music consumption. Grammarly redefined writing assistance from “check spelling and grammar” to “communicate clearly and professionally,” expanding the scope of what writing tools could accomplish. Both paths can drive transformation, but teams need clarity about which level they’re targeting to execute effectively.

Practical Implementation That Works

The most effective teams develop simple but consistent practices that prevent the two levels from blurring together during the heat of customer conversations. During interviews, successful practitioners tag statements in real time using simple codes, “PJ” for Product Jobs, “CJ” for Core Jobs, directly in their notes. This habit creates immediate organization that pays dividends during analysis.

When customers inevitably mix both levels in a single statement, experienced interviewers split them with targeted follow-ups. If a customer says, “Setup takes forever and we miss our analysis deadlines,” effective interviewers probe each component separately: “Tell me more about what makes setup so time-consuming” targets the Product Job, while “What happens when analysis deadlines are missed?” explores the Core Job implications. This approach ensures that both types of opportunities receive proper attention.

In Blueprinting projects, the most successful teams build separate job maps before attempting to link them. One map traces the complete lifecycle of product interaction, from initial awareness through final disposal. The other map captures the broader process the customer is trying to accomplish, independent of any specific solution. Only after both maps are complete and validated do teams overlay them to identify where Product Job friction points cascade into Core Job failures.

Project scoping benefits enormously from explicit definition at the outset. Rather than allowing scope to drift through the project lifecycle, effective teams document clearly whether they’re targeting Product Jobs, Core Jobs, or both. This written commitment prevents mid-project confusion and helps stakeholders understand why certain opportunities receive priority over others.

When scoring opportunities, disciplined teams segment them by level to ensure proper weighting. Without this separation, small product annoyances can overshadow strategic breakthrough opportunities, or conversely, big-picture thinking can neglect practical adoption barriers that prevent customer success. Both extremes undermine innovation effectiveness, but systematic separation prevents these problems from occurring.

The Innovation Imperative

Neither Product Jobs nor Core Jobs represents an inherently superior innovation target. Both can fuel breakthrough innovations that reshape industries and create lasting competitive advantages. The critical discipline lies in separating them clearly and choosing the right level for each specific opportunity.

Product Job innovations demonstrate how rethinking lifecycle tasks can disrupt entire industries. Uber, Amazon, and Dyson prove that even seemingly mundane interactions, calling rides, placing orders, emptying vacuum bags, can become sources of transformative advantage when approached with fresh thinking and superior execution.

Core Job innovations show equal potential for market transformation. Spotify’s music discovery algorithms and Grammarly’s writing enhancement capabilities prove that addressing fundamental customer goals can be just as disruptive as improving product interactions. The key insight is that both approaches work, but they require different capabilities, timeframes, and success metrics.

The winning teams are those that separate Product Jobs and Core Jobs clearly, respect the innovation potential in both, and choose deliberately which level offers the best opportunity for each specific situation they encounter. This disciplined approach prevents the common trap of trying to innovate everywhere simultaneously, which typically results in mediocre progress across all fronts.

That’s the power of Jobs-to-be-Done when applied with systematic rigor. And it’s exactly why The Jobs-to-be-Done Pyramid™ framework exists: to help practitioners see the complete landscape—functional, identity, and emotional jobs across all five levels—and build innovation strategies that connect authentically with what customers truly need to accomplish.

To learn more about New Product Blueprinting, Jobs-to-be-Done, and the full Pyramid framework, feel free to reach out to us here, or you can read more on JTBD at www.JTBDPyramid.com