Jobs to Be Done

JTBD for B2B: How Enterprise Product Teams Use Jobs Theory

How to apply Jobs to Be Done in B2B: multiple stakeholders, buying committees, longer cycles, and real examples from Pöttinger and Liebherr.

JTBD Was Built for Consumer Products. B2B Needs Something Different. Right?

Wrong.

This is the most common objection I hear when presenting Jobs to Be Done to B2B product teams: “Our market is different. We have buying committees, not individual consumers. Our sales cycles are 12 months, not 12 minutes. Our customers are engineers, not milkshake buyers. JTBD does not apply here.”

It applies here more than anywhere. And the reason is precisely the complexity that B2B teams cite as the objection.

Consumer products serve a single job executor who is also the buyer. The milkshake customer hires and fires the milkshake in one transaction. B2B products serve multiple job executors — the operator, the maintenance technician, the safety officer, the procurement manager — each with different jobs, different outcomes, and different satisfaction levels. They are evaluated by buying committees with 5-12 members, each applying different criteria. They operate in environments with regulatory constraints, integration requirements, and total cost of ownership calculations.

This complexity is not a reason to avoid JTBD. It is the reason JTBD is indispensable. Without a systematic framework for understanding what each stakeholder is trying to accomplish, B2B product teams are guessing at a puzzle with 10 times more pieces than consumer markets.

This article shows how JTBD applies to B2B, with specific attention to the challenges that enterprise product teams face: multiple job executors, complex buying dynamics, longer cycles, and the integration of JTBD insights into enterprise selling. We draw on real examples from companies like Pöttinger and Liebherr, as discussed in our podcast episodes #2 and #48.

For the full JTBD methodology, see our Complete Guide to Jobs to Be Done.


What Makes B2B Different (and Why It Matters for JTBD)

Multiple Job Executors

In consumer markets, one person buys the product and one person uses it (often the same person). In B2B, a single product may serve five or more distinct job executors:

For a loader crane (e.g., Liebherr or Palfinger):

  • The operator: Job = transport materials from ground level to elevated positions. Outcomes focus on speed, precision, and confidence.
  • The maintenance technician: Job = keep the crane in operational condition with minimal downtime. Outcomes focus on diagnostic clarity, parts availability, and repair speed.
  • The fleet manager: Job = maximize utilization and minimize total cost of ownership across the crane fleet. Outcomes focus on utilization data, maintenance forecasting, and lifecycle cost.
  • The safety officer: Job = ensure all lifting operations comply with safety regulations. Outcomes focus on documentation, compliance verification, and incident prevention.
  • The site manager: Job = coordinate material movement across the construction site efficiently. Outcomes focus on scheduling, throughput, and delay minimization.

Each of these stakeholders has a legitimate job with measurable outcomes. A product that excels for the operator but frustrates the maintenance technician has a problem. A product that satisfies the safety officer but creates inefficiencies for the site manager has a different problem. JTBD provides the framework for understanding and addressing all of these perspectives systematically.

Info

When mapping a B2B job, always ask: “Who else touches this product or is affected by how the job gets done?” The answer typically reveals 3-5 additional job executors whose outcomes your product team has not systematically studied. Each one represents both a risk (if their outcomes are poorly served) and an opportunity (if you serve them better than competitors).

The Buying Committee

B2B purchasing decisions are made by committees, not individuals. A typical enterprise buying committee includes:

  • The Economic Buyer: Controls the budget, evaluates ROI and TCO
  • The Technical Evaluator: Assesses product capabilities against requirements
  • The End User: Evaluates usability and fit with daily workflows
  • The Champion: Advocates for the purchase internally
  • The Blocker: Has the authority to veto or delay the decision

Each committee member applies different criteria. The economic buyer cares about total cost of ownership and payback period. The technical evaluator cares about specifications and integration. The end user cares about ease of use and daily workflow impact. The champion needs ammunition to sell the decision internally. The blocker needs assurance that risks are managed.

JTBD helps you understand each committee member’s decision criteria at the outcome level, not just the feature level. The economic buyer’s job is not “evaluate the crane’s price” — it is “minimize the risk of an investment that does not deliver the expected return.” The blocker’s job is not “find problems with the purchase” — it is “protect the organization from decisions that create operational, financial, or reputational risk.”

When you map each committee member’s job and outcomes, you can build a value proposition that addresses the entire committee — not just the person you happen to have the best relationship with.

Longer Sales Cycles

B2B sales cycles for industrial equipment, MedTech devices, and enterprise software range from 6 to 18 months. During this time, the buying committee evaluates alternatives, conducts pilot studies, negotiates terms, and seeks internal approval.

JTBD supports longer sales cycles in two ways:

  1. Better qualification: By understanding the outcomes that each stakeholder is trying to achieve, sales teams can quickly assess whether their product addresses the committee’s priority outcomes. If the highest-opportunity outcomes for this particular committee align with your product’s strengths, pursue aggressively. If they do not, qualify out early and save resources.

  2. Outcome-based selling: Instead of leading with features, sales teams lead with outcomes. “Our system minimizes the time to verify crane stability before lifting by 40%” is more compelling than “our system has an advanced stability display.” The first statement is customer-centric (here is what it does for you). The second is product-centric (here is what it has). In long sales cycles, customer-centric messaging sustains engagement because it connects to the committee’s actual priorities.

Higher Switching Costs

B2B switching costs include equipment replacement, retraining, integration with existing systems, regulatory re-certification, and operational disruption. These costs suppress switching behavior, meaning customers tolerate more dissatisfaction before changing products.

For the JTBD practitioner, this means two things:

  1. Underserved outcomes represent pent-up demand. When switching costs are high, customers live with unmet needs for years. The frustrations revealed by JTBD research are real and deeply felt — but customers have not acted on them because the cost of switching outweighed the cost of tolerating the problem. When a new product addresses these accumulated frustrations, the switching motivation can overcome the switching cost — especially if the product addresses multiple underserved outcomes simultaneously.

  2. Overserved outcomes are especially dangerous. In B2B, overserved outcomes (high satisfaction, lower importance) signal features where competitors can undercut you. A disruptive competitor can enter with a simpler, cheaper product that omits overserved features and instead addresses the underserved outcomes that incumbents have ignored. This is Clayton Christensen’s disruption theory, grounded in ODI’s quantitative framework.


JTBD in Practice: Pöttinger and Agricultural Equipment

Pöttinger, the Austrian agricultural equipment manufacturer, provides an instructive example of JTBD in a B2B context. As we discussed in podcast episode #2, agricultural equipment presents classic B2B complexity: the operator (farmer) is sometimes the buyer but often not (farm manager, cooperative purchasing, leasing companies), and the equipment serves multiple jobs across multiple stakeholders.

The Primary Job: Harvest the Crop with Maximum Yield and Minimum Loss

For the operator (farmer or machine operator), the primary functional job is harvesting. But the job map reveals that execution — the actual cutting, threshing, and collecting — is only one stage.

Prepare stage challenges:

  • Assessing field conditions and configuring the machine optimally for current crop type, moisture level, and terrain
  • Ensuring the machine is properly maintained and ready for the narrow harvest window
  • Coordinating with logistics (grain cart, truck) for seamless operation

Monitor stage challenges:

  • Tracking yield, loss rates, and quality metrics in real time
  • Detecting mechanical issues before they cause breakdowns during the harvest window
  • Adjusting for changing conditions (moisture variation across the field, terrain changes)

Conclude stage challenges:

  • Documenting yields and quality for contractual and regulatory purposes
  • Cleaning and preparing the machine for the next field or for storage
  • Sharing performance data with farm management systems

The Buying Committee Dimension

For a Pöttinger machine, the buying committee may include:

  • The farmer-operator: Focuses on operational outcomes (harvest quality, machine reliability, ease of use)
  • The farm manager/owner: Focuses on financial outcomes (yield per hectare, cost per ton, equipment ROI)
  • The service/maintenance provider: Focuses on serviceability outcomes (diagnostic access, parts availability, repair complexity)
  • The cooperative purchasing manager (for cooperative farms): Focuses on standardization and fleet management outcomes

Each stakeholder’s outcomes feed different sections of the value proposition. A single product must address outcomes across all stakeholder groups — or at least avoid creating unacceptable dissatisfaction for any of them.

In B2B, the product that wins is not the one that delights the operator — it is the one that satisfies the entire buying committee while delighting the operator. This is a much harder problem, and it is exactly the problem that JTBD is designed to solve. Map every stakeholder’s job. Measure every stakeholder’s outcomes. Address the intersections.

Martin Pattera

JTBD in Practice: Liebherr and Construction Equipment

Liebherr, the multinational construction equipment manufacturer, operates in a market where JTBD reveals opportunities that traditional competitive analysis misses. As covered in podcast episode #48, the construction equipment market is evolving rapidly due to digitalization, sustainability requirements, and skilled labor shortages.

How JTBD Reframes the Market

Traditionally, Liebherr’s competitive frame for mobile cranes is other mobile crane manufacturers — Tadano, Manitowoc, Terex. JTBD reframes competition around the job: “lift and position heavy components at a construction site safely and efficiently.”

This job-centric view reveals competition from:

  • Tower cranes (different product category, same job)
  • Heavy-lift helicopters (for remote or access-constrained sites)
  • Modular construction (prefabrication that eliminates the need for on-site heavy lifts)
  • Construction robots and automated positioning systems (emerging alternatives)

Where B2B Complexity Creates Opportunity

The most interesting JTBD insight from the construction equipment domain is the mismatch between what manufacturers optimize and what job executors need most.

What manufacturers optimize (Execute stage):

  • Lifting capacity
  • Reach
  • Speed of operation
  • Fuel efficiency

What operators need most (Prepare and Monitor stages):

  • “Minimize the time to assess whether the crane configuration is suitable for the planned lift” (Prepare)
  • “Minimize the uncertainty about ground conditions and their effect on crane stability” (Confirm)
  • “Minimize the time to detect a deviation from the planned lift path” (Monitor)
  • “Minimize the effort required to coordinate the lift with other site activities” (Define)

The opportunity gap — where manufacturer investment does not align with operator need — is largest in the stages surrounding execution, not in execution itself. This is a consistent pattern across industrial B2B.

The Multi-Stakeholder View

For a Liebherr mobile crane, the stakeholder map includes:

  • Crane operator: Primary job executor, focused on operational outcomes
  • Lift supervisor: Responsible for lift planning and safety, focused on risk management outcomes
  • Site manager: Coordinating the crane with other site activities, focused on scheduling and throughput outcomes
  • Maintenance team: Keeping the crane operational, focused on reliability and diagnostic outcomes
  • HSE (Health, Safety, Environment) officer: Ensuring regulatory compliance, focused on documentation and compliance outcomes

A JTBD study that only addresses the operator’s outcomes misses 60% of the value landscape. The lift supervisor’s outcomes around risk management and the HSE officer’s outcomes around compliance documentation represent significant unmet needs that competitors are also neglecting.


The B2B JTBD Process: How It Differs from Consumer

Step 1: Define Multiple Jobs

Instead of one job map, create a job map for each primary stakeholder. A B2B JTBD study typically involves 3-5 stakeholder groups, each with their own job, outcomes, and satisfaction levels.

This multiplies the research scope but also multiplies the strategic insight. The intersections — outcomes that are shared across stakeholders or outcomes where stakeholders conflict — are where the most valuable innovation opportunities live.

Step 2: Interview Across Roles

Your interview sample should represent all major stakeholder groups. A typical B2B JTBD study might include:

  • 10-12 operators/end users
  • 5-8 maintenance/service personnel
  • 5-8 procurement/fleet managers
  • 3-5 safety/compliance officers
  • 3-5 senior decision-makers

Total: 26-38 interviews. More than a consumer study, but the complexity of B2B buying justifies it.

Step 3: Quantify Per Stakeholder Group

The quantitative survey should segment by stakeholder role. You need statistically significant samples for each major stakeholder group — typically 50–150 respondents per group. This allows you to identify outcomes that are underserved for operators but well-served for maintenance staff (or vice versa), revealing trade-off decisions that a single aggregate survey would obscure.

Step 4: Map the Buying Committee Journey

Beyond the individual job maps, map the collective buying journey. At which stages do different committee members become involved? What outcomes drive their evaluation? Where in the buying process do decisions stall, and what unmet needs cause the stall?

A common finding: buying committees stall when the champion cannot articulate the product’s value in terms that resonate with other committee members. JTBD provides the champion with outcome-level ammunition: “This system addresses the three outcomes that our operators rate as most important and least satisfied” is more compelling than “This system has better specifications.”

Step 5: Build Multi-Stakeholder Value Propositions

The final output is not a single value proposition but a value proposition matrix: for each stakeholder role, here are the priority outcomes addressed and the evidence that your product addresses them. Sales teams use this matrix to navigate the buying committee, presenting the right outcomes to the right stakeholder at the right stage of the buying process.

Info

Create a one-page “outcome sheet” for each buying committee role. When the sales team meets with the maintenance manager, they bring the maintenance outcome sheet. When they meet with the CFO, they bring the economic buyer outcome sheet. Same product, different framing — both grounded in quantified customer outcomes.

B2B-Specific Challenges and Solutions

Challenge: “Our Customers Cannot Articulate Their Needs”

This objection surfaces in every B2B JTBD engagement. And it is both true and irrelevant.

Customers cannot articulate the solution they want (they did not ask for automatic outrigger positioning before it existed). But they can absolutely articulate the outcomes they care about (“I waste 15 minutes on every setup verifying that the outriggers are correctly deployed, and I am never fully confident”). JTBD captures outcomes, not solutions. Outcomes are articulable, stable, and measurable.

Challenge: “Our Market Is Too Technical for Emotional Jobs”

We addressed this in our article on functional, emotional, and social jobs, but it bears repeating in the B2B context: technical professionals have emotional and social needs. A crane operator who feels uncertain about stability is less productive and more prone to error. A maintenance technician who feels embarrassed about calling the manufacturer’s support line for a diagnostic question avoids calling — and the problem escalates. These are not soft issues. They are operational realities driven by emotional outcomes.

Challenge: “Our Products Serve Too Many Applications”

Industrial products often serve multiple applications, each with a different job context. A hydraulic pump that serves mobile cranes, excavators, and agricultural equipment is used in three different jobs. The solution: define the job at the right level of abstraction for each major application, and run separate outcome analyses for each. The pump manufacturer may find that crane operators and excavator operators have different patterns of unmet needs, requiring different product configurations or positioning strategies.

Challenge: “We Sell Through Distributors — We Don’t Know the End User”

This is a legitimate challenge and one that JTBD directly addresses. If you rely on distributors for customer feedback, you are getting filtered information — the distributor’s interpretation of what the customer needs, mixed with the distributor’s own commercial interests. JTBD research goes directly to the job executor. The resulting insights bypass the distributor filter and give you a direct understanding of end-user outcomes. This does not replace the distributor relationship — but it ensures that your product strategy is based on end-user reality, not the distributor’s interpretation of it.


Getting Started with B2B JTBD

Start Small but Complete

Pick one stakeholder group for one product in one market. Run a full JTBD/ODI cycle — qualitative interviews, outcome capture, quantitative survey, opportunity analysis. This gives you a proof of concept without requiring organizational transformation.

Choose the Right Pilot Product

Select a product where you suspect that customer needs are more complex than your current understanding reflects. Good candidates:

  • Products where customer satisfaction scores are moderate but market share is declining
  • Products where competitors are gaining ground despite inferior specifications
  • Products entering new applications or market segments
  • Products with high customer churn despite no obvious quality issues

Build Internal Champions

JTBD in B2B requires buy-in from product management, engineering, and sales. The most effective approach is to share early results with all three groups and let the data build the case. When the sales team sees outcome-based value propositions and the engineering team sees quantified priorities, adoption follows naturally.

For the detailed process of translating B2B JTBD insights into product specifications, see From JTBD to Product Requirements. For a comparison of JTBD-based segmentation versus traditional B2B personas, see JTBD vs. Personas.


Frequently Asked Questions

This is one of JTBD’s strengths in B2B. By mapping separate jobs for each stakeholder — the user, the buyer, the maintainer, the safety officer — JTBD explicitly captures the different outcomes that each stakeholder cares about. The buyer’s job (“make a purchasing decision that minimizes risk and maximizes ROI”) has different outcomes than the user’s job (“perform the daily task efficiently and reliably”). JTBD does not conflate these; it maps them separately and helps product teams address both. The product must satisfy the user’s job to create value. It must satisfy the buyer’s job to close the sale.
Start with the 2-3 most critical stakeholder groups: typically the primary user, the primary buyer, and one other role that significantly influences the purchase or use of the product (e.g., maintenance, safety, IT). A comprehensive study covers 4-5 stakeholder groups. Going beyond 5 creates research complexity that may not justify the marginal insight. Prioritize the stakeholder groups that have the most influence on the purchasing decision and the most interaction with the product.
JTBD does not replace these methods entirely, but it addresses their limitations. VOC captures what customers say they want (feature requests). JTBD captures what customers are trying to accomplish (outcomes). Win/loss analysis tells you why you won or lost specific deals. JTBD tells you which outcomes drive purchasing decisions across the market. The methods are complementary: use JTBD for strategic product decisions (what to build), and use VOC and win/loss for tactical adjustments (how to sell, how to position). Over time, JTBD should become the primary input to product strategy, with VOC and win/loss providing supplementary signals.
JTBD and ABM are complementary. ABM targets specific accounts with personalized outreach. JTBD provides the content of that outreach — the outcomes that matter to each stakeholder within the target account. A JTBD-informed ABM campaign leads with outcomes relevant to each committee member rather than generic product messaging. For example, the message to the VP of Operations emphasizes operational efficiency outcomes, while the message to the CFO emphasizes total cost of ownership outcomes. Same product, same account, different outcome framing.
The direct cost of a B2B JTBD/ODI study (including multiple stakeholder groups) is typically EUR 80,000-150,000 for a medium-complexity product. The ROI comes from: (1) reduced product failure risk — the published 86% ODI success rate versus the industry average of 17% means dramatically fewer wasted R&D investments; (2) faster product-market fit — products built against quantified outcomes reach market acceptance faster; (3) improved sales effectiveness — outcome-based selling reduces sales cycle length and improves win rates. For a product with EUR 10M+ annual revenue potential, the ROI on a EUR 100,000 study is substantial even with conservative improvement assumptions.

Apply JTBD to Your B2B Product Line

Book a complimentary discovery call to explore how these ideas apply to your organization.

Book a Discovery Call
Martin Pattera
Written by

Martin Pattera

Martin helps leadership teams build innovation capabilities and navigate strategic transformation. With experience spanning Fortune 500s and high-growth startups, he brings a practitioner's lens to strategy consulting.