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

When a product category has been around for years—decades, even—it can feel like every meaningful problem has already been solved. Email clients, project management tools, CRM platforms, banking apps: these markets are full of well-funded competitors offering broadly similar feature sets. Differentiation seems impossible.

Yet customers in mature categories still switch products. They still complain. They still build workarounds with spreadsheets, sticky notes, and extra tools bolted onto their primary solution. These behaviors are evidence that unmet needs persist, even when the market appears saturated.

Jobs-to-be-done (JTBD) interviews are one of the most reliable ways to find those needs. This article explains how to plan, conduct, and analyze JTBD interviews specifically for mature product categories where the challenge is not inventing a new market but finding the gaps that incumbents have missed.

Why mature categories still have unmet needs

The assumption that a saturated market has no room left is usually wrong. It confuses "many competitors" with "all needs served." In practice, several forces create persistent gaps.

Feature parity masks outcome gaps. Competitors copy each other's features, which creates surface-level similarity. But two products can offer the same feature and deliver very different outcomes. A file-sharing tool might offer version history, but if finding the right version takes five minutes of scrolling, the job of "making sure I'm working on the latest document" is poorly served despite the feature existing.

Incumbent incentives favor existing customers. Large players in mature markets optimize for retention of their biggest accounts. This creates blind spots around emerging use cases, smaller customer segments, and jobs that span product boundaries.

Jobs evolve faster than products. The circumstances surrounding a job change over time—remote work shifts collaboration needs, regulatory changes alter compliance jobs, new integrations change the ecosystem a product sits within. Products that were well-fitted to the job five years ago may be subtly misaligned today.

Emotional and social dimensions get ignored. Most mature-category roadmaps focus on functional performance. The emotional side of the job—feeling confident in a decision, avoiding embarrassment in front of a team, reducing anxiety about a deadline—often goes unaddressed because it is harder to measure and ship.

JTBD interviews surface all of these gaps because they focus on what customers are trying to accomplish, not on the product they are using.

A brief primer on jobs-to-be-done

The JTBD framework starts with a simple premise: people don't buy products for the product's sake. They "hire" products to make progress in a specific situation. The "job" is the progress the person is trying to make, defined independently of any solution.

A job has functional, emotional, and social dimensions. It exists within a specific context—a set of circumstances that shape what good performance looks like. And it can be decomposed into a job map: a sequence of steps from beginning to end, each of which has desired outcomes the customer uses to evaluate how well the job is going.

In mature categories, the power of this framing is that it forces you to look past the product and examine the job itself. When you do, you almost always find steps or outcomes that no existing product handles well.

Planning JTBD interviews for a saturated market

Effective JTBD research in a mature category requires deliberate decisions about who to interview, what event to focus on, and how to structure the conversation.

Selecting participants

In mature markets, the most valuable interview subjects are people who have recently done one of three things:

• Switched products. Someone who moved from one competitor to another made an active decision that something about their old solution was insufficient. Their switching story reveals which unmet needs had enough force to overcome the inertia of staying.

• Adopted a workaround. People who use a combination of tools—a spreadsheet alongside their project management tool, a personal Slack channel to supplement the official one—are compensating for a gap. Workarounds are unmet needs made visible.

• Abandoned the category entirely. In some cases, people stop using a type of product and revert to a manual process or a different category of tool. These non-consumers reveal jobs that the entire category fails to serve.

Aim for 12–20 interviews. Recruit across different company sizes, industries, and roles if your product serves a broad market. The variation in context is what surfaces needs that a narrow sample would miss.

Choosing the right "job" scope

Before interviewing, define the job at the right altitude. Too broad ("manage my work") and the conversation will be unfocused. Too narrow ("sort my task list by due date") and you are back to evaluating features.

A useful test: the job should be something a customer would recognize as a meaningful goal they are trying to accomplish, independent of your product. "Make sure my team is working on the right priorities this week" is a well-scoped job. "Use the Kanban board" is not—it describes a solution, not a job.

In saturated categories, it often helps to define two or three candidate jobs and test them in your first few interviews. You will quickly learn which framing produces the richest stories.

Structuring the interview guide

JTBD interviews follow a "switch interview" or "timeline interview" format. You are reconstructing a specific, real event—not asking for abstract preferences.

Core sections of the interview:

1. First thought. When did you first start thinking about finding a different way to do this? What was happening in your life or work?

2. Passive looking. What did you do after that first thought? Who did you talk to? What did you search for?

3. Active looking. When did it become a real priority? What triggered the shift from "thinking about it" to "actively doing something about it"?

4. Decision and hiring. What did you ultimately decide to do? What other options were you considering? What tipped you toward this choice?

5. Outcome and evaluation. After you made the change, how did it go? What was better? What was the same or worse? Did anything surprise you?

Throughout, probe for specifics. "You mentioned it was frustrating—can you walk me through exactly what happened?" and "What would it have looked like if that had gone perfectly?" are questions that consistently produce insight.

Conducting the interviews

Listen for the job, not the product

The interviewer's discipline is to keep the conversation anchored to the situation and the desired progress, not to the product. When a participant says "I wish the tool had a better dashboard," respond with: "Help me understand what you were trying to figure out when you went to the dashboard." The answer to that question is the job; the dashboard is just one possible solution.

Capture desired outcomes explicitly

A desired outcome is a measurable statement of how the customer evaluates success at a particular step of the job. The format is: direction of improvement + metric + context.

For example: "Minimize the time it takes to figure out which tasks are blocked" or "Reduce the likelihood that a stakeholder sees outdated information."

As you interview, actively translate what participants describe into outcome statements. You do not need to use this language with the participant—it is an analytical layer you apply during or after the conversation.

Document workarounds and compensating behaviors

In mature categories, workarounds are gold. Every time a participant describes something they do outside the primary product—sending a follow-up email to confirm a status, copying data into a spreadsheet, screenshotting a report for a meeting—note it carefully. Each workaround corresponds to a job step or outcome that the current solution does not adequately serve.

Track emotional energy

Pay attention to where the participant's energy shifts during the story. Frustration, relief, pride, anxiety—these emotional markers point to the moments in the job that matter most. In saturated markets, emotional dimensions are frequently the most underserved because competitors focus on functional parity.

Analyzing JTBD data to find unmet needs

After completing your interviews, analysis proceeds in three phases.

Build the job map

Synthesize all interviews into a single job map: the sequence of steps a person goes through from the moment they first recognize the need to the point where they evaluate the outcome. Typical job maps have 8–15 steps.

Each step should be solution-agnostic. "Review team progress" is a job step. "Open the project dashboard" is a product action. Keep the map at the job level.

List desired outcomes per step

Under each step, compile the desired outcomes that participants described. Remove duplicates, standardize the language, and check that each outcome follows the direction + metric + context format. A mature-category job map often produces 50–100 distinct desired outcomes.

Identify importance and satisfaction gaps

The most powerful part of the JTBD framework for mature categories is what happens next. You can take the list of desired outcomes and survey a broader population, asking two questions for each outcome:

1. How important is this outcome to you? (Scale of 1–5)
2. How satisfied are you with how well current solutions deliver this outcome? (Scale of 1–5)

Outcomes that score high on importance and low on satisfaction are underserved. These are your unmet needs—and in a saturated market, they represent the most defensible opportunities for differentiation.

This approach, sometimes called opportunity scoring or outcome-driven innovation, transforms qualitative interview data into a prioritized, quantitative map of where the market is underserved.

Tools like Dovetail can help throughout this process. Transcribing and tagging interview data in a shared repository makes it far easier to synthesize job steps and outcomes across multiple interviews, especially when working with a team. Having all your qualitative data in one place also makes it simpler to return to source material when building the subsequent survey or validating findings with stakeholders.

Common mistakes in mature-category JTBD research

Anchoring to your own product

The most frequent error is framing questions around your product rather than the job. If your interview guide references specific features or screens, you will get feedback about those features—not insight into the broader job. Stay product-agnostic until the analysis phase.

Interviewing only your current customers

Your current customers have, by definition, decided that your product is adequate enough to keep using. They may not represent the segments where unmet needs are most acute. Include switchers, workaround users, and non-consumers in your sample.

Treating all outcomes as equal

Not every unmet need is an opportunity. Some outcomes are underserved but unimportant. Others are important but already well-served. The opportunity lies at the intersection of high importance and low satisfaction. Without measuring both dimensions, you risk building features that solve real problems no one cares enough about to switch for.

Stopping at the interview

Interviews are generative. They surface candidates for unmet needs. But validating those needs—confirming that they are widespread and underserved across a meaningful segment—requires quantitative follow-up. The interview-to-survey pipeline is what gives JTBD its strategic power, especially in categories where intuition alone is unreliable because so many needs appear "already met."

Turning unmet needs into product strategy

Once you have a ranked list of underserved outcomes, product strategy becomes more concrete:

• Prioritize outcomes, not features. Frame your roadmap in terms of which underserved outcomes you intend to improve, then explore multiple possible solutions for each.

• Look for outcome clusters. Several underserved outcomes that fall within the same job step may point to a single high-impact feature or experience redesign.

• Segment by job context. Different customer segments may experience the same job but with different importance weightings. A small team and an enterprise team both "keep projects on track," but the outcomes they care most about differ. Segmenting by outcome priority can reveal niches within a saturated market that no incumbent specifically serves.

• Communicate in outcome language. Marketing in mature categories tends to describe features. If you know which outcomes are underserved, you can speak directly to those outcomes in positioning and messaging—which resonates far more than another feature comparison chart.

Making JTBD research a repeatable practice

In a mature market, unmet needs are not static. As competitors adjust, as customer contexts shift, and as technology evolves, the landscape of underserved outcomes changes. The teams that build a lasting advantage are the ones who treat JTBD research as an ongoing practice rather than a one-time project.

This means maintaining a research repository where interview transcripts, job maps, outcome lists, and survey results accumulate over time. Dovetail is designed for exactly this kind of longitudinal qualitative research—centralizing insights so that the understanding you build in one research cycle is available to inform the next, and accessible to product, design, and strategy teams who need it.

Mature, saturated categories are not dead ends. They are markets where customer needs have been partially met by many players and fully met by none. JTBD interviews give you the tools to find precisely where the gaps are, measure their size, and act on them with confidence.

Most practitioners find that 12–20 interviews with people who have recently switched products or adopted workarounds reveal the majority of underserved needs in a given job. Saturation—the point where new interviews stop producing new job steps or desired outcomes—typically occurs between interviews 15 and 20. However, in highly segmented markets you may need separate rounds for distinct user populations, since different segments often prioritize different parts of the job.

Standard user interviews typically ask people about their preferences, opinions, and experiences with a specific product. JTBD interviews focus instead on the underlying goal the person is trying to accomplish, independent of any particular solution. The interviewer traces the full timeline of a real event—from the first thought that triggered action through the final outcome—to understand what progress the person was trying to make. This shift in focus surfaces needs that product-centric interviews often miss because the conversation is not anchored to existing features.

JTBD interviews are effective for both. In mature categories, breakthroughs are rare and most competitive advantage comes from serving existing jobs measurably better on dimensions that incumbents overlook. JTBD data helps teams prioritize incremental improvements by quantifying which desired outcomes are most important to customers yet least well satisfied by current solutions. This makes the framework particularly well-suited to saturated markets where the opportunity often lies in execution gaps rather than entirely new jobs.