Jobs-to-be-Done Examples: 8 Real Companies (2026)

The best way to learn Jobs-to-be-Done is not to define it again — it's to see the framework applied to products you already use. Below are eight worked Jobs-to-be-Done examples from real companies, each mapped to the job the product is actually hired for, followed by a template for turning any of them into a JTBD statement for your own product. If you want the theory first, start with our JTBD framework explained guide; this page is the examples.

The reason examples matter more than definitions here is that JTBD's whole point is a reframe: customers don't buy products, they hire them for a job. You only feel that reframe when you watch a familiar product stop being "a language app" and start being "a way to feel productive for five minutes." That shift — from product category to job — is the entire skill.

Want to run JTBD on your own product? Framework for iPhone & iPad walks you through the situation, motivation, and outcome for each job with AI-assisted prompts. Free to start.

The three types of jobs every example has

Before the examples, the one distinction that makes them readable. Every job a customer hires a product for sits in one of three layers — and strong products serve all three at once.

Job layer	What it is	The question it answers
Functional	The practical task to get done	"What am I literally trying to accomplish?"
Emotional	How the customer wants to feel	"How do I want this to make me feel — or stop feeling?"
Social	How the customer wants to be perceived	"What does using this say about me to others?"

The classic mistake in reading a JTBD example is stopping at the functional layer. "People hire Instagram to share photos" is the functional job and it explains almost nothing. The emotional job (feel like my life is interesting) and the social job (be seen as someone with taste) are what actually drove the growth. Keep all three in view for every example below.

The Three-Layer Job Map: 8 real companies

Here is the citable version — eight products you know, each decomposed into its functional, emotional, and social job. Read down any column to see a pattern; read across any row to see why a single product beats competitors that only serve one layer.

Company	Functional job	Emotional job	Social job
Duolingo	Practice a language in spare minutes	Feel productive, not guilty, about downtime	Be seen as someone who's "learning Spanish"
Netflix	Fill unstructured free time with something watchable	Stop the anxiety of "what do I even put on"	Have something to talk about tomorrow
Slack	Keep team communication in one searchable place	Feel on top of work, not buried in email	Look responsive and organized to the team
Uber	Get from A to B without owning a car	Remove the anxiety of hailing, waiting, haggling	Signal you can afford convenience
Spotify	Have the right music for any moment	Match or shift my mood on demand	Show identity through playlists and Wrapped
Notion	Store notes, docs, and tasks in one system	Feel like my "second brain" isn't leaking	Be the person with the beautiful workspace
LinkedIn	Find a job or a hire	Feel career-secure and in-demand	Be seen as a credible professional
ChatGPT	Get a usable draft or answer fast	Feel capable at things I'm not expert in	Appear more productive than my peers

I call this the Three-Layer Job Map — the discipline of never accepting a one-line "they hire it to X" example until all three layers are named. It's the fastest way to spot which layer your own product is under-serving. Most products win on functional and lose on emotional or social; the map makes that gap visible in one row.

Worked example: what Duolingo is really hired for (Q1 2026)

The single most instructive JTBD example right now is Duolingo, because its own numbers prove the point. In its Q1 2026 results, daily active users grew 21% year over year to 56.5 million — the first quarter in company history above 55 million — while revenue rose 27% to $292 million (Duolingo 10-Q, Q1 2026).

Here's the tell. If people hired Duolingo to become fluent, its retention would track course completion — and course completion is famously low. It doesn't. Retention tracks the streak. The functional job ("learn Spanish") is real but weak; the durable job is emotional and behavioral: feel productive during idle minutes without the guilt of scrolling, and don't break the chain.

Everything in the product is built for that real job, not the stated one:

Feature	Stated job it serves	Real job it serves
Daily streak counter	Track learning progress	Create loss-aversion so skipping a day hurts
Streak Freeze	Forgive a missed lesson	Remove the anxiety that one slip ruins the habit
Leaderboards / leagues	Motivate practice	Add a social job — being seen keeping up
Push notifications	Remind you to study	Re-trigger the habit loop at the same time daily

Third-party case studies estimate the Streak Freeze feature alone cut churn by about 21% for at-risk users, and that users who reach a 7-day streak are roughly 3.6× more likely to stay engaged (Trophy — Duolingo gamification case study, 2026). Those are habit-formation numbers, not education numbers. A team that ran a JTBD interview and heard "I want to feel like I did something with my commute" would build exactly this product. A team that believed the functional job would keep adding grammar features and wonder why nobody finished the course.

The lesson that generalizes: when a product's retention doesn't match its stated purpose, the real job is hiding one layer down. Find it and you find the roadmap.

How to write a JTBD statement from an example

Examples are only useful if you can convert one into a statement for your own product. Use the canonical template:

When [situation], I want to [motivation], so I can [expected outcome].

Watch it fill for three of the examples above:

• Duolingo — When I have a few idle minutes and feel like I'm wasting them, I want to do something that feels productive, so I can end the day without guilt.
• Slack — When a decision is scattered across email threads and DMs, I want one searchable place my whole team can see, so I can stop re-explaining context.
• Uber — When I need to get somewhere and don't want to drive or wait, I want a ride to arrive on demand, so I can stop worrying about the logistics of getting there.

The test for your own statement is falsifiability: five real customers should be able to confirm or reject it. "When I'm busy, I want to be productive, so I can succeed" passes no test — it could never be wrong, so it's not a job. For the full interview structure that produces these statements, see the JTBD framework explained walkthrough.

B2B examples work differently: stack the jobs

Consumer examples have one hero job. B2B examples have a stack, because the buyer is a committee and each member hires the product for a different job. Collapsing them into the end user's job is the most common way B2B JTBD analysis goes wrong.

Take Figma as a worked B2B example:

Buyer role	The job they hire Figma for	Layer
Designer (end user)	Design without version chaos or file handoffs	Functional
Design lead	Keep the whole team working on one live canvas	Functional + emotional
Procurement / IT	SSO, audit logs, and a defensible security posture	Functional (compliance)
VP who signs off	Look like they backed the modern, safe standard	Social

A B2B pitch that only speaks to the designer's job loses the deal in procurement; one that only speaks to compliance never gets the designers to adopt it. This is why B2B JTBD work maps every role's job before writing a single feature. It's also where JTBD hands off to other artifacts — once the jobs are clear, see JTBD vs personas for who to build for and JTBD vs user stories for how to spec it.

Common mistakes when copying a JTBD example

Borrowing an example is smart; borrowing it wrong is the fast path to a roadmap that misses. The three failures below account for most of it.

Mistake	Why it happens	Fix
Stopping at the functional job	It's the easiest layer to name and feels "objective"	Force the emotional and social layers — that's where growth lives
Copying the example's solution, not its job	Duolingo's streak worked, so every app bolts on a streak	Extract the job (fight guilt over idle time), then design your solution for it
Writing an unfalsifiable statement	Generic feels safe and applies to everyone	If five customers couldn't reject it, it's a slogan, not a job

For a fuller worked case, our JTBD applied to Instagram Stories example runs the same three-layer analysis on a single feature launch.

Sources

• The Motley Fool — "Duolingo (DUOL) Q1 2026 Earnings Call Transcript"
• StockTitan — "Duolingo (NASDAQ: DUOL) 10-Q, Q1 2026 quarterly earnings report"
• Trophy — "Duolingo Gamification Strategy: A Full Case Study (2026)"
• Harvard Business School Online — "The Jobs to Be Done Framework & Real-World Examples"

Related

• Jobs-to-be-Done framework explained — the definition, the interview structure, and the statement template
• JTBD vs personas — which lens to use when
• JTBD vs user stories — how JTBD hands off to specs
• JTBD applied to Instagram Stories — a single-feature worked example