How to use jobs-to-be-done interviews to identify unmet needs in mature product categories

Mature product categories present a specific challenge for product teams: the obvious problems have been solved. Competitors offer similar capabilities, customers have established habits, and incremental improvements yield diminishing returns. In these conditions, traditional feature-driven research tends to confirm what everyone in the market already knows.

Jobs-to-be-done (JTBD) interviews offer a way out of this trap. Instead of asking customers what they want from your product, JTBD interviews investigate what customers are fundamentally trying to accomplish—and where they still struggle, compensate, or settle for "good enough." In mature categories, this shift in perspective is often the difference between building another parity feature and finding a genuine opening in the market.

Why mature categories demand a different research approach

When a product category is young, unmet needs are everywhere. Customers are vocal about what's missing because the gaps are large and obvious. Surveys, feature requests, and usability tests all surface useful opportunities.

As a category matures, this changes. The most visible needs have been addressed. Customer feedback begins to cluster around minor refinements—faster performance, cleaner UI, lower price. Teams working from this kind of input tend to make products that are slightly better at the same things, which is rarely a path to meaningful differentiation.

The needs that remain unmet in mature categories are typically harder to see for three reasons:

Customers have adapted. People build workarounds, combine multiple tools, or simply lower their expectations. They stop articulating the need because they've accepted the limitation as normal.

The job extends beyond the product. Products in a mature category tend to address the core task well but neglect the steps before and after. Customers may struggle with preparation, decision-making, coordination, or follow-through—none of which show up in a feature satisfaction survey.

Emotional and social dimensions are invisible in typical research. Customers in mature categories often have functional needs met but still feel anxious, uncertain, or frustrated. These emotional jobs rarely surface unless you ask the right questions in the right way.

JTBD interviews are designed to surface all three types of hidden needs.

The core mechanics of a JTBD interview

A JTBD interview is a structured conversation that reconstructs the story of how someone came to adopt, switch to, or stop using a solution. The focus is not on the product itself but on the forces that drove the person's behavior.

Start with a specific event

Every JTBD interview anchors on a real event: the moment the person decided to seek a new solution, made a purchase, switched from one tool to another, or abandoned something they were using. This is not a hypothetical. You are asking someone to walk you through something that actually happened.

Starting with a concrete event prevents the conversation from drifting into abstract preferences or aspirational statements. When someone says "I generally prefer simple tools," that's an opinion. When someone says "I was in the middle of preparing a quarterly report and I realized I'd spent 40 minutes just trying to get the data into the right format," that's a job struggling to get done.

Map the timeline

From the anchoring event, work backward and forward. You want to understand:

• First thought — When did the person first realize their current approach wasn't working? What triggered that realization?
• Passive looking — Did they start noticing alternatives without actively searching? What made certain options stand out?
• Active search — When did they start deliberately evaluating options? What criteria mattered?
• Decision — What finally pushed them to act? What nearly stopped them?
• Consumption and evaluation — After adopting the new solution, how did they judge whether it was working? What surprised them?

This timeline reveals the full context of the job—not just what the person ended up using, but the chain of events, emotions, and trade-offs that led them there.

Listen for the four forces

JTBD theory describes four forces that shape every switching decision:

1. Push — Dissatisfaction with the current situation ("This takes too long," "I keep making errors")
2. Pull — Attraction to a new solution ("I saw a demo that looked promising")
3. Anxiety — Fear about the new solution ("What if it's harder to learn?" "What if I lose my data?")
4. Habit — Attachment to the current way ("I already know how to do it this way," "My team is used to this")

In mature categories, forces three and four—anxiety and habit—often dominate. Customers may recognize that better options exist but feel the switching cost isn't worth it. Understanding the specific nature of that anxiety and habit reveals opportunities to reduce friction and make a genuinely compelling case for change.

Adapting JTBD interviews for mature categories

While the basic structure of a JTBD interview applies across contexts, mature categories require specific adjustments to surface the needs that matter most.

Recruit people at the edges

In a mature category, mainstream users are often the most adapted. They've settled into routines and may not register their workarounds as problems. Instead, focus your recruiting on:

• Recent switchers — People who recently changed solutions, even within the same category. Their decision is fresh, and they can articulate what drove the change.
• Non-consumers — People who should logically be using a product in this category but aren't. Understanding why they've opted out can reveal jobs the category fails to address entirely.
• Heavy compensators — People who use the product but supplement it with spreadsheets, sticky notes, manual processes, or other tools. The compensation behavior points directly to unmet needs.
• Churned customers — People who tried and left. Their departure story often contains the clearest articulation of what the category gets wrong.

Probe the surrounding job, not just the core task

Products in mature categories tend to nail the core task. A project management tool manages tasks. An email client sends email. A CRM stores contacts. Asking customers about these core functions will mostly confirm what you already know.

Instead, explore what happens around the core task:

• What does the person need to do before they can use the product effectively? (Data preparation, decision-making about how to structure their work, getting buy-in from others)
• What do they need to do after the core task is complete? (Sharing results, reporting, transitioning to the next step in their workflow)
• Who else is affected by the outcome, and how? (Stakeholders who consume the output, teams who depend on the decision)

These surrounding steps are often where the most significant unmet needs live because they fall outside what any product in the category considers its responsibility.

Ask about outcomes, not features

When probing for unmet needs, frame your questions around outcomes rather than capabilities. Instead of "What features are you missing?" ask:

• "When you finish this task, how do you know it went well?"
• "What would need to be true for you to feel confident in the result?"
• "What's the most time-consuming part of getting from start to finish?"
• "Where do you feel the most uncertainty?"

These questions surface the criteria customers use to evaluate success. When you find an outcome that matters to customers but that no product in the category supports well, you've identified an unmet need with real differentiation potential.

Analyzing JTBD interview data for unmet needs

Conducting interviews is only half the work. The real value comes from synthesizing what you've heard into a clear picture of where the market is underserving customers.

Identify distinct jobs

After completing your interviews, organize what you've heard into distinct jobs—the goals customers are trying to accomplish, stated independently of any product. A job statement typically follows the format: [verb] + [object] + [contextual qualifier]. For example: "Determine which customer segments are growing fastest so I can allocate resources for next quarter."

In mature categories, you'll likely find that the main job is well understood but adjacent or smaller jobs have been neglected. These secondary jobs are often where the opportunity lies.

Map desired outcomes to current satisfaction

For each job, list the outcomes customers described as important. Then assess how well current solutions in the category deliver on each outcome. The outcomes that are highly important but poorly satisfied represent genuine unmet needs.

This is sometimes called opportunity scoring, and it provides a structured way to prioritize which needs to address. An outcome that every customer mentions but no product handles well is a stronger signal than an outcome that one customer cares deeply about.

Look for patterns in workarounds

Workarounds are physical evidence of unmet needs. When multiple customers describe similar compensating behaviors—exporting data to spreadsheets, sending follow-up emails to confirm something worked, maintaining a separate document to track context—you're looking at a need the market has not addressed.

Document these workarounds in detail. The specific steps customers take to compensate reveal not just what is missing but how they think the solution should work. This is design-relevant insight that goes directly from research to product decisions.

Tools like Dovetail can help here by letting you tag and organize interview transcripts around jobs, outcomes, and workarounds. When you're working across 20 or more interviews, the ability to quickly surface every instance of a particular workaround or outcome makes the difference between anecdotal impressions and reliable patterns.

Turning unmet needs into product direction

Identifying unmet needs is valuable only if it changes what you build. Here's how to connect JTBD findings to product strategy in a mature category.

Separate the job from the solution space

One of the most common mistakes after JTBD research is jumping directly from a job statement to a specific feature. Resist this. The job statement defines the target; the solution could take many forms. Share the job map and unmet needs with your design and engineering teams and let them explore multiple approaches before converging.

Prioritize by opportunity size and strategic fit

Not every unmet need is worth pursuing. Evaluate each one against:

• How many customers experience this need? A need shared across segments is more defensible than one limited to a niche.
• How poorly is the need currently served? A need that is completely unaddressed offers more differentiation than one that competitors handle adequately.
• Does addressing this need align with your strengths? An unmet need that plays to your team's capabilities or your platform's architecture is more realistic to pursue.

Validate before building

JTBD interviews generate hypotheses about what customers need. Before committing significant development resources, validate those hypotheses. Show customers prototypes or mockups that address the identified need and observe whether it resonates. Run concept tests. Look for evidence that customers would actually change their behavior—switch products, pay more, consolidate tools—based on the new capability.

This validation step is especially important in mature categories where customers are skeptical of claims. They've seen many products promise differentiation and deliver incrementalism.

Common mistakes in JTBD research for mature categories

Interviewing only satisfied current customers. These users are the least likely to reveal unmet needs because they've made peace with the product's limitations. Broaden your recruiting.

Asking leading questions about your own product. JTBD interviews should be product-agnostic. If you steer the conversation toward your product's specific features, you'll get feedback on your product rather than insight into the job.

Stopping at functional needs. In mature categories, functional parity is common. The emotional and social dimensions of the job—feeling confident, looking competent, reducing risk—often hold the most untapped opportunity.

Treating the research as a one-time exercise. Jobs and outcomes evolve as markets, technology, and customer contexts change. JTBD research should be revisited periodically, especially when you notice shifts in competitive dynamics or customer behavior.

Building a lasting practice

JTBD interviews are most powerful when they become a regular part of how your team understands customers, not a one-off project. Establishing a research repository where interview data is organized by jobs, outcomes, and evidence of unmet needs makes each new study build on the last.

Dovetail is designed to support this kind of cumulative research practice—giving teams a shared space to store transcripts, tag insights by theme, and trace product decisions back to the customer evidence that informed them. In mature categories where differentiation depends on depth of understanding rather than speed of execution, this kind of structured insight work compounds over time.

The products that find new space in crowded markets are rarely the ones with the longest feature list. They're the ones that understood a job their competitors overlooked—and built for it with precision.

Standard user interviews often focus on opinions about existing products, feature preferences, or general satisfaction. JTBD interviews shift the focus to the underlying goal the person is trying to accomplish and the full context surrounding that goal—what triggered the need, what alternatives they considered, what trade-offs they accepted, and what outcomes they used to judge success. This reframing helps researchers see beyond the current product landscape and identify needs that no existing solution addresses well.

In mature categories, most competitors have converged on similar feature sets, making it difficult to differentiate through incremental improvements. JTBD interviews are valuable here because they look past the product entirely and focus on the job the customer is hiring a solution to do. This often reveals needs that the entire category has overlooked—needs related to emotional or social dimensions, upstream preparation steps, or downstream consequences that current products ignore. These overlooked needs represent genuine opportunities for differentiation.

There is no universal number, but most practitioners find that patterns begin to emerge after 10–15 interviews and reach saturation around 20–30, depending on the complexity of the job and the diversity of the customer base. The goal is not statistical representativeness but thematic saturation—the point at which additional interviews stop revealing new jobs, outcomes, or struggles. Interviewing across different customer segments or usage contexts typically surfaces a wider range of unmet needs with fewer total interviews.