Why the Jobs-to-Be-Done Framework Breaks Down in Global Markets

The Jobs-to-Be-Done (JTBD) framework is one of the most useful tools in a product marketer’s kit. It reframes strategy around what customers are actually trying to accomplish, not just what they say they want. In domestic markets, it works well. Take it international, and it starts breaking in ways most teams don’t anticipate.

I’ve worked on international projects where JTBD-driven strategies that performed well in one market completely missed in another: same product, same framework, very different results. The framework wasn’t wrong. The assumption that the same ‘job’ exists across cultures was.

This piece explains where JTBD fails in global contexts, why it happens, and how to adapt it so it actually works across markets. If you’re building a multilingual strategy or entering a new region, this is the gap most frameworks don’t address.

What is the Jobs-to-Be-Done Framework?

JTBD is a framework that focuses on understanding the underlying goal a customer is trying to achieve when they use a product or service: the ‘job’ they’re hiring it for. Rather than focusing on product features or demographics, it asks: what progress is the customer trying to make? This makes it useful for product positioning, marketing strategy, and international expansion planning.

What the JTBD Framework Does

JTBD reframes customer behavior around the outcome they’re trying to achieve, aka the ‘job’ they’re hiring a product to do. The question isn’t ‘what features do customers want?‘ It’s ‘what are they trying to accomplish, and what gets in the way?‘

The McDonald’s milkshake example is the clearest illustration of this. McDonald’s wanted to increase milkshake sales and surveyed customers about flavors and sizes. Sales didn’t move. When Clayton Christensen applied JTBD thinking, he found that most milkshakes were sold before 8:30am, to solo customers who drove off immediately.

The job wasn’t ‘I want a milkshake.’ It was ‘I have a long commute, I need something that keeps me full and occupied, and it needs to work with one hand on the wheel.‘ That insight, milkshakes competing with bananas and bagels, not other milkshakes, led to changes that increased sales sevenfold.

The power of JTBD is in that reframe. But it only works if you correctly identify the job. And in international markets, the job is rarely the same.

Where JTBD Breaks Down Across Borders

The framework assumes that customers in your target market are trying to accomplish a similar job to customers in your home market. That assumption holds when contexts are similar. It collapses when they aren’t.

Cultural Differences Redefine the Job

Two people in different markets can have fundamentally different jobs for the same product category not because the product is different, but because their context is.

Take privacy. In Western markets, data privacy is a primary concern. A customer using a productivity app is partly using it to not expose their data. In many Asian markets, the emphasis shifts toward connectivity and shared access. The job of ‘staying productive‘ might include easy sharing with a team or family, which in a Western market would raise privacy flags.

The same applies to health products. Western markets often hire supplements and wellness products for specific, measurable outcomes: lose weight, build muscle, improve sleep. Markets influenced by traditional Chinese medicine frame the job differently: around balance, prevention, and long-term well-being. A product positioned around fast results can actively underperform in a market where the job is holistic health maintenance.

Family and social dynamics shift the job too. In individualistic cultures, products get hired for personal efficiency. In collectivist cultures, the job often has a communal dimension: does this help my family, my community, does it fit how we operate together? A product that ignores this hires itself out of the running before the customer even evaluates features.

Language Doesn’t Just Translate. It Transforms

Inaccurate translation doesn’t just create awkward phrasing. It completely misrepresents the job the product is supposed to do.

Coca-Cola’s early entry into China is the obvious case. A direct phonetic translation of ‘Coca-Cola’ (蝌蚪啃蜡 – ko-kä-kö-la) produced characters that translated roughly to ‘bite the wax tadpole‘ in certain dialects. The brand eventually settled on characters meaning ‘happiness in the mouth‘, a phrase that actually maps to the job Coca-Cola is hired for in any market.

Pepsi’s Taiwan slogan ‘Come Alive with the Pepsi Generation’ was translated in a way that read as ‘Pepsi will bring your ancestors back from the dead.’ The job — energy, vitality, belonging to something exciting — was entirely lost. What remained caused offense.

We tend to consider these just as translation errors. But in reality, they’re JTBD failures: the job the product was supposed to do became unrecognizable in the target market.

Socioeconomic Conditions Change What the Job Even Is

In markets with limited purchasing power or infrastructure, the primary job is often fundamentally different from what you’ve built your product around.

Nokia understood this when designing the Nokia 1100 for emerging markets. In high-income markets, customers hire phones to stay connected, access apps, and signal status. In low-income emerging markets, the job was durability, affordability, and basic reliability: a phone that survives harsh conditions and holds a charge. The Nokia 1100 became one of the best-selling phones in history because it matched the actual job, not the job Nokia was used to solving.

Google’s Internet Saathi program in rural India took the same thinking further. The job wasn’t ‘browse the internet.’ It was ‘gain digital literacy in a community with no infrastructure for it.’ That required hiring local women as intermediaries, not building a better app.

Legal and Regulatory Environments Constrain the Job

Sometimes the job customers want done is legally restricted in your target market. This forces an adaptation that goes beyond localization: it changes what the product can actually be hired for.

Microsoft’s GDPR compliance work in Europe is a clear example. Features that relied on broad data collection had to be restructured. The job customers hired Microsoft’s cloud services for (efficient, connected, data-rich workflows) still existed, but the way the product could deliver on it changed significantly. Data residency options and compliance tools weren’t customer requests; they were prerequisites for remaining hirable in that market.

How the Same Job Changes by Market: A Comparison

This table shows how a single product category can have fundamentally different jobs across markets and what that means for strategy.

Unilever ran both of those detergent strategies simultaneously: Wheel for rural markets, Surf Excel for urban ones. The product category was identical. The job was not. That’s JTBD applied correctly in a global context.

How to Adapt JTBD for International Markets

The framework doesn’t need to be replaced: it needs to be re-grounded in each market’s specific context before you apply it. Here’s how I approach it.

Start with Local Research, Not Translated Research

The most common mistake is designing research instruments in one language and translating them for other markets. You end up asking the right questions in the wrong way, and the answers reflect the translation artifacts, not the actual customer context.

Localized research means designing the instrument for the target market from scratch: language, framing, examples, and all. Work with researchers who are native speakers with domain expertise, not generalist translators. Field studies in-market are worth far more than remote surveys.

Map the Job to the Cultural and Economic Context

Before defining the job in a new market, map the variables that shape it:

Pilot Before You Scale

Running a small, representative pilot in each new market is significantly cheaper than a failed launch. Test the job hypothesis with a narrow audience before committing to full localization. The job you assumed customers had and the job they actually have often diverge in ways that only show up when real people use the product in context.

Airbnb’s Japan expansion is a good example. The platform’s standard model ran into the cultural specifics of omotenashi (Japanese hospitality) and local regulations on short-term rentals. Adapting through local expertise and phased rollout let Airbnb recalibrate before scaling, rather than after a public stumble.

Treat Each Market’s Job as a Starting Point, Not a Variation

Stop treating international markets as variations on your home market and start treating each one as its own JTBD problem to solve. The job in Germany might share some surface features with the job in the US, but the drivers, constraints, and success criteria are different enough to warrant separate research and separate strategy.

P&G’s Pampers launch in China is the clearest example here. Research revealed that Chinese parents prioritized cognitive development over Western parents’ typical focus on comfort and convenience. The job wasn’t ‘keep my baby dry‘. Tt was ‘support my baby’s development.’ That single reframe changed the entire marketing strategy, and it worked because it came from real local research, not assumed overlap with existing markets.

JTBD and Multilingual SEO: The Connection Most Teams Miss

The same principle applies to international SEO, and it’s one of the areas where I see the most avoidable waste.

A direct keyword translation is the SEO equivalent of the Pepsi slogan error. The words are technically correct but the job the search query represents (the intent, the urgency, the context) gets lost. Someone in Germany searching for a B2B software tool is using different vocabulary, different search patterns, and operating in a different decision-making context than someone in the US searching for the same product.

Effective multilingual SEO runs JTBD analysis by locale, not by language. What job is this person trying to do when they type this query? What does success look like for them? What cultural or contextual factors shape how they phrase the search?

That analysis changes your keyword strategy, your content structure, and your calls to action — not just the words on the page.

The Framework Works If You Listen to the Market

JTBD is not the problem. The problem is applying it from the outside in and assuming you know what job customers need done before you’ve done the research in that specific context.

International markets don’t care about your home market insights. They have their own context, their own constraints, and their own version of the job. The companies that succeed globally — Unilever in India, Nokia in emerging markets, P&G in China — did so because they rebuilt the JTBD analysis from the ground up in each market, rather than exporting the answer they already had.

If you’re building a global strategy or entering a new market and want to work through how JTBD applies to your specific situation, let’s talk.