12 Outcome-Backed Jobs to Be Done Examples (And What They Prove)

McDonald's milkshake research revealed an effective market seven times larger than years of attribute focus groups had found. Intercom restructured from one product to four and grew 500% in 18 months. Cordis Corporation climbed from 1% to over 20% market share in angioplasty after applying the same framework.

In each case, the product team shifted one question: from "what features do users want?" to "what progress are customers trying to make?" The business results followed.

Below, 12 jobs to be done examples organized from foundational theory through org design, each paired with the outcome data most competing articles leave out. Strategyn reports an 86% success rate for projects following the ODI process, compared to a 17% industry average. The cases below illustrate why.

Key Takeaways

1. Every consumer JTBD example in this list has a B2B industrial counterpart that's equally valid and far less cited in product literature. Cordis (medical devices), Cox Automotive (dealer SaaS), and Hussmann (retail refrigeration) each produced verifiable market-share gains.
2. The McDonald's milkshake study's most useful finding: the real competitive set (bananas, donuts, Snickers, bagels) was invisible to every attribute-based research method McDonald's had used for years.
3. JTBD's highest day-to-day value for practitioners is shared language. A single job statement travels from discovery through requirements through GTM without translation.

Top 12 Jobs to Be Done Examples

Ordered by impact and teachability, from foundational theory through org design:

1. McDonald's Milkshake: the commuter job that revealed a 7x larger market
2. Intercom: the four-product restructure that drove 500% growth in 18 months
3. Cordis Corporation: from 1% to 20%+ market share in angioplasty via ODI
4. Southern New Hampshire University: 50 anomalous students grew to 200,000+
5. Airbnb: the emotional and social jobs hotels never competed for
6. Slack: the pre-launch JTBD memo that shaped company positioning
7. Netflix vs. Blockbuster: two different jobs, two different business architectures
8. Spotify: three job types driving one product strategy
9. Cox Automotive vAuto: a 20x install base from identifying the right dealer segment
10. Dollar Shave Club: the $1 billion over-served segment Gillette missed
11. Zoom: solving the reliability failure of an incumbent category
12. Meta's JTBD Pod Structure: jobs as the unit of org design

How to Evaluate a JTBD Example

Four things worth checking in any jobs to be done case study:

• Job specificity: Is the statement specific enough to exclude products that don't do this job? "Restore blood flow to an artery" is a job. "Make patients healthier" is not.
• Competitive set visibility: Does the example reveal competitors the product team hadn't considered? The milkshake study's most instructive finding was that bananas and bagels competed with milkshakes.
• Outcome documentation: Consumer examples are everywhere. Examples with verifiable business outcomes (market share numbers, growth rates, install base changes) are far more instructive.
• Transferability: Can you apply the same research method to your own context? Cases with a named discovery method (switch interview, ODI scoring, contextual inquiry) are more reusable than narrative retrospectives.

Comparison Table

1. McDonald's Milkshake

The commuter job that revealed a 7x larger market

Before Christensen and Moesta conducted their demand-side research in the 1990s, McDonald's had run repeated focus groups on milkshakes. Customers asked for sweeter flavors, chunkier ingredients, more variety.

McDonald's tested every recommendation. Sales didn't move.

The JTBD-informed observation, 18 hours of watching who bought milkshakes and when, revealed something the focus groups couldn't. Nearly half of all milkshakes sold before 9 AM went to lone commuters on their way to work.

They weren't buying a milkshake because they wanted a milkshake. They were hiring it to survive a boring solo drive: one hand on the wheel, something slow-sipping, filling, and engaging for 45 minutes.

The real competition wasn't Dairy Queen. It was bananas (gone in two minutes), donuts (too messy), bagels (too dry), and Snickers bars (guilt-inducing).

Afternoon milkshake sales told a completely different story: a parent treating a child after school. Different job, different competitive set, different product design needed.

Christensen (Harvard Innovation Labs):

There's a job out there somewhere that arises in people's life on occasion that causes them to need to buy a milkshake... It turns out the job that all of these people were trying to get done was: I have a long and boring drive to work and I needed something that would just keep me engaged with life while I'm driving the car.

When McDonald's tested a JTBD-guided redesign, the effective market turned out to be seven times larger than conventional attribute analysis had found. The real competitive set was invisible to any method that started with the product, not the job.

Pros

• Reveals non-obvious competitive substitutes that product-centric research systematically misses
• Explains why repeated attribute optimization can fail even with high-quality customer feedback
• Produces clear product specification directly from job requirements (thickness, delivery speed, one-handed form factor)

Cons

• The "7x" market size figure is Christensen's reported finding, not an official McDonald's data release
• Requires significant field observation time: 18 hours in this case
• Produces two distinct product briefs when multiple demand contexts exist (morning commuter vs. afternoon parent)

Method used

Demand-side observation combined with switch interviews (who is hiring this, when, against what alternatives). The Re-Wired Group documents the methodology in full.

2. Intercom

Four distinct jobs, 500% growth in 18 months

After three years as an all-in-one customer communication platform, Intercom had plateaued. Customer relationships were strong, but growth had stalled.

JTBD research revealed four distinct jobs customers were hiring Intercom to do: getting help when something broke, learning how to use a feature, being onboarded, and receiving proactive nudges about relevant events. One product and one interface was forcing customers to use the same experience for four different contexts. The result: suboptimal design for each job, no pricing differentiation across them.

Intercom rebuilt from one product into four. Inbox (support), Articles (self-serve learning), Product Tours (onboarding), and Bots (proactive automation) each addressed one job. Value-based pricing followed directly from the job structure: each product priced on the value of its specific job.

The outcome: 500% growth in 18 months, 4x website traffic, and 3x additional revenue. Des Traynor, co-founder: "Five years later, it's still the foundation of our product and marketing strategies. I can't think of one area of our business JTBD hasn't improved."

Intercom's four-job restructure also produced the Job Story format now standard in UX practice: When [situation], I want to [motivation], so I can [expected outcome]. The Job Story format emerged from the need to write product specs that didn't collapse four distinct jobs into a single user story.

Pros

• Demonstrates that one product serving multiple distinct jobs can grow faster by separating them into distinct product lines
• Produced the Job Story statement format, which UX practitioners now use as a standard
• Outcome data is specific and well-documented

Cons

• Multi-product restructures require significant engineering and go-to-market investment
• Job discovery at this depth requires substantial qualitative research that most product teams lack time for
• Applies most cleanly to platforms serving multiple user types; harder to replicate for single-use-case tools

Method used

JTBD interviews with customers, analyzed by The Re-Wired Group.

3. Cordis Corporation

From 1% to 20%+ market share via Outcome-Driven Innovation

Cordis was competing in the angioplasty balloon market. Their market share was 1%.

Strategyn's Outcome-Driven Innovation process began with a single functional job: "Restore blood flow to an artery."

ODI research then identified 12 distinct outcome metrics that customers used to evaluate success at that job, including minimizing procedure time, minimizing the risk of arterial damage, and maximizing control of balloon positioning. Each metric was scored on importance and current satisfaction. The gaps between importance and satisfaction revealed exactly which outcomes were underserved.

Cordis focused product development on those gaps. The result: 19 new products, every one becoming #1 or #2 in its market segment, and market share growing from 1% to over 20%.

This is the clearest available example of ODI as distinct from narrative JTBD research. The job doesn't change. The outcome metrics that define "doing the job well" are what ODI surfaces and scores.

B2B and industrial companies find ODI more applicable than the switch-interview method precisely because outcome metrics are measurable in technical fields in ways emotional jobs are not. This case study appears in zero top-10 SERP competitors for this keyword.

Pros

• Specific market share data (1% to 20%+) makes the business case quantifiable
• ODI process is replicable: define the functional job, identify outcome metrics, score importance × satisfaction, target the gaps
• Proves JTBD applies in regulated, technical B2B contexts where most practitioners assume it doesn't

Cons

• Full-scale ODI requires Strategyn's methodology and survey tooling; harder to run independently
• Specific years for the case study are not confirmed in public sources, so present it as historical
• Technical job statements require domain expertise to write correctly

Method used

Outcome-Driven Innovation via Strategyn: importance × satisfaction scoring of outcome metrics within a defined functional job.

4. Southern New Hampshire University

50 anomalous students became a 200,000-student strategy

In 2010, Southern New Hampshire University had 50 to 60 students paying full tuition but never showing up in person. Conventional analysis would flag them as data anomalies to ignore. Bob Moesta's team interviewed them instead.

The job these students were hiring SNHU to do was fundamentally different: adult learners who had tried college once before, it hadn't worked, and they needed credentials without disrupting current obligations. The job: "Make progress in my career without disrupting current obligations."

Traditional college was designed around a completely different job. SNHU's campus experience, admissions process, academic calendar, and advising model were all optimized for students with no existing obligations. Redesigning the online experience around the adult learner's job required faster admissions decisions, shorter modular courses, and proactive dedicated coaches rather than once-a-semester check-ins.

SNHU now has over 200,000 students and is one of the largest universities in the world by enrollment. The methodological lesson: anomalous customers who are hiring your product in an unexpected way are often the highest-value JTBD signal available, not noise to filter out.

Pros

• Demonstrates that anomalous, non-typical customers are frequently the richest source of genuine JTBD insight
• Applies to service organizations and institutions, not just SaaS or consumer products
• Outcome (200,000+ students) is independently verifiable

Cons

• Org-level transformation at SNHU's scale took years and significant change management
• Defining the job clearly enough to drive architectural redesign required multiple research cycles
• The adult learner job is specific context; the pattern generalizes, but the insights don't transfer directly

Method used

Switch interviews with anomalous users. Re-Wired Group case study documents the process.

5. Airbnb

The emotional and social jobs hotels structurally can't address

Hotels serve the functional job: find a place to sleep. Airbnb identified social and emotional jobs that hotels can't address by design.

The social job ("Have a story to tell about where I stayed") and the emotional job ("Feel like a local, not a tourist") shaped every design decision. Reviews build trust and community signal. Experiences provide local access.

Neighborhood guides reinforce local identity. None of these decisions came from feature prioritization. They came from the jobs being served.

The JTBD framing also redefined Airbnb's competitive set. Airbnb doesn't primarily compete with Marriott. It competes with staying with friends, not going on the trip at all, and "stay at a cheaper hotel."

Every product decision that makes an Airbnb stay feel more local and less like an anonymous check-in addresses the emotional and social jobs hotels structurally can't serve.

Airbnb grew from 2,500 listings (2009) to 6.6 million (2022). Long-term stays and Experiences, both added later, are extensions of the same emotional job.

Pros

• Shows how emotional and social jobs define competitive positioning that functional alternatives can't replicate
• Competitive set redefinition (not vs. Marriott but vs. staying with friends) is a directly applicable insight
• Growth trajectory is publicly documented

Cons

• Emotional and social jobs are harder to score and measure than functional jobs
• Replicating Airbnb's job-based positioning requires the same trust infrastructure (reviews, photos, host profiles), a high upfront investment
• Two-sided marketplace complicates job definition: host jobs and guest jobs are distinct and sometimes in tension

Method used

Demand-side market analysis; job-based product architecture. thrv.com analysis documents the job framing.

6. Slack

The pre-launch JTBD memo that became company strategy

Before Slack shipped, CEO Stewart Butterfield wrote a company memo titled "We Don't Sell Saddles Here."

The memo is one of the clearest applications of JTBD thinking by a CEO in writing, and it predates the product launch.

The memo's core argument: Slack wasn't selling chat software. It was selling a reduction in the cost of communication and zero-effort knowledge management.

Selling features (channels, DMs, integrations) to customers who already had email was a losing proposition. Selling the progress customers would make (decisions faster, context preserved, context searchable) was how you create a new category.

Slack's JTBD: "Reduce communication overhead and make team knowledge instantly searchable." That job statement shaped product positioning, pricing, and every GTM message from day one.

u/ToStringMethod in r/ProductManagement: "I am a fan of JTBD because it aligns the entire product lifecycle around customer outcomes. By defining the product through the lens of the job the customer is hiring it to do, you establish outcome-focused language right from inception." (r/ProductManagement, May 2025)

Slack reached 12 million daily active users before being acquired by Salesforce. The JTBD insight wasn't discovered retroactively: it was the founding strategic frame.

Pros

• The original pre-launch memo is publicly available and gives practitioners direct access to JTBD thinking as a primary-source document
• Demonstrates JTBD as positioning and messaging strategy, not just product research
• 12 million DAU is publicly documented

Cons

• Slack's job definition is abstract enough that teams can misread it as permission for feature sprawl
• New category creation requires capital and distribution at Slack's scale; the lesson generalizes, the scale doesn't
• Post-acquisition complexity and enterprise tension post-date the JTBD insight

Method used

JTBD as pre-launch positioning framework. Butterfield's memo is the primary source.

7. Netflix vs. Blockbuster

Two different jobs, two entirely different business architectures

Blockbuster's job: "Be the convenient stop to pick up the latest releases for movie night." That job required real estate in high-traffic locations, deep new-release inventory, and fast checkout.

Netflix identified a different job: "Help me discover and watch films that match my tastes, on my schedule, without late fees or trips to the store."

That job required logistics infrastructure, personalization algorithms, and customer behavioral data. No overlap with Blockbuster's architecture.

Because the jobs were different, every business decision diverged. Blockbuster optimized for location density and new-release stock. Netflix optimized for taste-matching and delivery convenience.

Blockbuster saw Netflix as a niche mail-order service. Netflix saw the job (reliable access to the films you want, on your terms) as a large underserved market with low switching cost from store rentals.

Netflix grew from 7.5 million subscribers (2007) to over 260 million (2023). Blockbuster filed for bankruptcy in 2010.

The Netflix case illustrates the consequence of defining your market by product category (video rental) vs. by the underlying job (watch what I want, when I want).

Netflix didn't follow a formal JTBD process, but the lesson holds. One definition puts you in the same market as Blockbuster. The other puts you in a different market entirely.

Pros

• Demonstrates how market definition drives strategic investment decisions, not just product design
• Business architecture differences are observable in hindsight without needing internal research documentation
• Strong cautionary example for incumbents that define their market by product category rather than by job

Cons

• Netflix's success involved many factors beyond job-based positioning (timing, broadband adoption, DVD logistics economics)
• Using failure cases as JTBD evidence is retrospective: the lesson is clear, but the prediction wasn't
• The "Blockbuster didn't understand JTBD" framing can oversimplify a complex competitive failure with multiple causes

Method used

Job-based market definition applied by Christensen's research; subscriber data from Netflix Investor Relations.

8. Spotify

Three job types driving one product strategy

Spotify's job architecture is one of the clearest available demonstrations of how functional, emotional, and social jobs interact in a single product.

Before Spotify, finding music required active curation: building playlists track by track, browsing albums, buying individual downloads. The functional job: "Find the right music for this moment without effort." Discover Weekly, Release Radar, and Daily Mix address this job directly.

Each reduces curation work to zero.

The emotional job ("Match my mood with the perfect soundtrack") drove mood-based playlists (Focus, Sleep, Party) and the emotion-labeled genre categories. The social job ("Signal my taste to others") produced Spotify Wrapped, social sharing, collaborative playlists, and the public follower count. Every major Spotify feature maps to one of the three job types.

Teresa Torres (@ttorres): "Good product discovery starts with a clear desired outcome." (June 2023) Spotify's feature output is a working demonstration of what discovery anchored to functional, emotional, and social jobs looks like in production.

Pros

• Clean mapping of all three JTBD types to distinct, named product features
• 40% algorithmic engagement provides a quantifiable proxy for functional job delivery
• Spotify Wrapped as a social-job product is one of the most widely studied growth experiments of the last decade

Cons

• Social job measurement is indirect (sharing behavior) rather than directly surveyed
• Spotify's personalization infrastructure is impossible to replicate for most teams at any reasonable cost
• The three-job framework applies to many products; Spotify is one illustration, not a recipe

Method used

Three-job-type product strategy (functional, emotional, social). Spotify Newsroom documents Discover Weekly engagement data.

9. Cox Automotive vAuto

A 20x install base from identifying the right dealer segment

Cox Automotive applied JTBD to identify which dealer segments were most underserved in the inventory management job. "Auto dealer" is not a job-based segment.

Strategyn's ODI process identified a more precise segment: dealers managing high inventory turn with limited staff and no manual analysis capacity. The specific outcome metrics that segment was failing to meet became the product development target.

Randy Kobat, SVP Cox Automotive: "The project had a significant financial impact to the vAuto business. Today, we have about 4,000 clients using the solution." The install base grew 20x.

This case matters for B2B SaaS practitioners because it illustrates the ODI market segmentation step specifically. Job-based segments are defined by shared outcome metrics, not by company size, industry, or buyer persona.

Two dealers with identical firmographic profiles can have completely different unmet job outcomes depending on staff size and inventory strategy. ODI finds the segment defined by shared unmet needs, a segmentation that drives product differentiation rather than just targeted marketing.

Pros

• B2B SaaS context is directly applicable to product managers outside consumer tech
• 20x install base growth is a verifiable outcome
• Named executive quote (Randy Kobat) adds source credibility

Cons

• Strategyn is both the research firm and the publisher of this case study, a potential interest in positive framing
• ODI surveys require significant investment and survey design expertise to run independently
• Specific timeline for the case study is not confirmed in publicly available sources

Method used

Strategyn ODI: importance × satisfaction scoring of outcome metrics, job-based market segmentation.

10. Dollar Shave Club

The $1 billion over-served segment Gillette missed

Gillette's product strategy was internally consistent: keep improving the razor. More blades, vibration cartridges, moisture strips, better pivoting heads. Each generation addressed what the most demanding shaving enthusiasts valued.

Dollar Shave Club found a large segment with a completely different job: "Get a decent razor at a fair price, delivered without effort." On shaving performance, this segment was over-served. The features Gillette was charging for were features this segment didn't value and wouldn't pay for.

Strategyn on LinkedIn (May 2026) (LinkedIn):

Gillette kept making razors better. Dollar Shave Club made them good enough. Unilever paid $1 billion for the difference. The segment that only needed a decent razor at a fair price existed in the market the entire time. Not a different demographic. The same demographic. A different set of primary unmet needs.

Unilever acquired Dollar Shave Club for $1 billion. The over-served segment pattern is one of Strategyn's most replicable JTBD findings. When a market leader keeps innovating on features a large segment doesn't value, a simpler product targeting that segment's actual job can capture significant share at a fraction of the R&D cost.

Pros

• Over-served segment identification is a directly applicable disruption pattern for new market entrants
• $1 billion acquisition price is a clear documented outcome
• The Strategyn framing (same demographic, different unmet needs) is the precise practitioner takeaway

Cons

• Dollar Shave Club's growth also benefited significantly from its direct-to-consumer model and marketing voice, separate from the job insight
• The over-served framing requires accurate data on which features customers actually value, which is hard to verify without formal ODI surveys
• Commodity categories with low switching costs make the pattern easier to enter but harder to defend

Method used

Over-served segment identification via Christensen's disruptive innovation model applied to JTBD.

11. Zoom

Solving the reliability failure of an incumbent category

Video conferencing existed before Zoom. Skype, WebEx, and GoToMeeting were all competing in the same category. None of them had solved reliability at scale.

Zoom's JTBD: "Connect remote workers face-to-face reliably, on any device, with minimal setup." The functional job was identical to every competing product. The outcome metric most underserved was reliability: calls dropping, audio sync failing, bandwidth crashes on slower connections.

Zoom's HD audio-video architecture prioritized that one outcome metric above all others.

The emotional job (making distributed teams feel present rather than isolated) drove virtual backgrounds, gallery view, and reactions. Each addressed the "feeling like I'm in the same room" job rather than a competitive checklist against Skype.

Zoom saw 354% customer growth following COVID-19. Daily meeting participants surpassed 300 million by April 2020. COVID didn't create the job; it made the job urgent for the majority of professionals who had never experienced reliable video conferencing.

Pros

• Demonstrates how identifying the single most underserved outcome metric within an existing job is enough to disrupt an established category
• 354% growth and 300 million daily participants are independently verifiable
• The emotional job (presence vs. isolation) maps directly to distributed team software design decisions

Cons

• Zoom's 2020–2021 growth peak created retention challenges as offices reopened, complicating long-term analysis
• Reliability as a differentiator eroded once competitors improved; Zoom now competes primarily on integration and enterprise features
• COVID timing makes clean causal attribution to JTBD insight difficult

Method used

Outcome metric identification within an existing functional job (reliability gap analysis). Zoom blog documents the growth data.

12. Meta's JTBD Pod Structure

Jobs as the unit of organizational design

Most JTBD examples describe product discovery. Meta's application describes organizational design.

u/TheShortAzn in r/ProductManagement (February 2025, score: 15): "At Meta, in my org, we do JTBD hybrid. Each job is a pod, and each pod has eng, product, design, UXR, DS... Don't make your JTBD complicated to start with." (r/ProductManagement)

The implication: the job statement isn't just a research artifact. It becomes the ownership boundary for a cross-functional team. Each pod owns one job, holds one measurable outcome, and contains all the disciplines needed to work on that job.

The pod's success metric is "job done better," not "features shipped."

This structure solves the cross-functional alignment problem that makes JTBD hard to operationalize at scale. Instead of translating a job statement into requirements, sprints, and handoffs where the job's meaning gets diluted, the job becomes the team's identity and accountability frame.

u/Flys_Lo in r/ProductManagement: "JTBD I think is an essential framework as part of your strategy... understanding the 'unconventional' competitors you may have by how your customers are solving for them." (r/ProductManagement, May 2025)

Pros

• JTBD applied to org design rather than product research: a dimension rarely covered in writing
• Named company (Meta) with a named Reddit practitioner and working permalink
• Outcome metrics ("decrease checkout time") are immediately measurable at the pod level

Cons

• This is a Reddit practitioner report, not an official Meta case study; scope and generalizability are uncertain
• Pod org structure requires significant design investment and potential team restructuring
• Job-based pods multiply boundary complexity when products serve multiple interdependent jobs, as most platforms do

Method used

Job-as-pod cross-functional team structure. r/ProductManagement discussion is the primary source.

How to Write Your Own JTBD Statement

Four statement formats exist across the four main JTBD schools. Choose based on what you need the statement to do:

• Verb-first / ODI (Ulwick): For measurable, scorable job statements. Format: [Action verb] + [object] + [contextual clarifier]. Example: "Restore blood flow to an artery." Best for technical or B2B teams running ODI surveys.
• ODI outcome statement (Strategyn): For quantifying which part of the job is underserved. Format: Minimize/maximize + [metric] + when [context]. Example: "Minimize the time it takes to set blade depth on a circular saw." Best for opportunity scoring across a large job landscape.
• Job Story (Intercom): For UX and product design contexts where the circumstance matters. Format: When [situation], I want to [motivation], so I can [expected outcome]. Example: "When I'm driving to work alone, I want something slow-sipping and filling, so I can arrive without stopping for breakfast." This is the most common format in UX practice.
• Progress narrative (Christensen): For research framing, executive communication, and initial job discovery. Focus on circumstance and desired progress, not product capabilities. Example: "Get through a boring commute without hunger or mess."

The same commuter job written in all four formats:

Common JTBD Mistakes to Avoid

The examples above illustrate what works. These five anti-patterns explain why the method fails when applied incorrectly.

Job too precise: "Fill out the expense report form" describes a UI step, not a market segment. "Account for all business spending without delaying project work" defines a market. If your job statement only applies to one screen in your product, it's a use case.

Job too broad: "Hire an app to run my business" doesn't guide any product decision. A real job statement should exclude products that don't do this job. If 50 different products qualify, the statement is too broad.

Solution language in the statement: "Hire a design system with dark mode and responsive tokens" describes a product. "Hire a design system that lets UI teams maintain consistent components across products" describes the job.

"Bitching ain't switching": Bob Moesta: "Just because people [complain] about something doesn't mean they're going to do anything about it." (Lenny's Podcast) Basecamp users said they'd leave without Gantt charts.

They didn't leave. JTBD interviews focus on what people did, not what they said they would do.

Treating JTBD as a UX flow tool: u/contralle on Reddit (r/ProductManagement, Oct 2021):

JTBD is really helpful for getting to the heart of a complex problem with multiple intertwined stakeholders... I think it is helpful for describing technology-agnostic problems that someone needs to solve in the course of their work, NOT for laying out the specific steps someone would take in your product.

Teams that use JTBD to map product flows end up mapping UI steps, not jobs.

Emerging Trends in Jobs to Be Done

1. JTBD for AI agent evaluation: Strategyn (May 2026) on AI purchasing agents: "When an AI agent evaluates your platform on behalf of a buyer, it doesn't read your positioning statement. It evaluates your product against the job it needs to do." (LinkedIn) Job-based product architecture is becoming more durable as AI agents replace human buyers in initial vendor evaluation.
2. JTBD as long-horizon market stability test: Strategyn (May 2026) tracked three technologies (CDs, MP3s, Spotify) serving one stable job across 20 years: "The underlying market is the Job. Products come and go. Technologies come and go." (LinkedIn) Companies that define their market by job rather than product category show more durable positioning across technology transitions.
3. Job-per-pod org design adoption: Meta's pod structure (documented above) is gaining attention in product-management communities as practitioners look to make JTBD operational rather than purely a research-phase input. The pattern aligns cross-functional teams around measurable outcomes rather than feature backlogs.