MarketingFramework / modelModelAccessible

Unmet need analytics

How can unmet need analytics support strategic choice or positioning?

AccessibleStrategicIndividual2 min read

Contents

Unmet need analytics is the process of uncovering whether there are any unmet needs around your product or service or within your market that you could meet to increase customer satisfaction and revenue.

Unmet need analytics identifies important customer outcomes that current products, services or market alternatives do not satisfy well. It turns evidence about frustrations, compromises and workarounds into opportunities for product improvement or innovation.

When to use it

Customer expectations, technologies and competitive alternatives change, so reassess needs at least annually in stable markets and more frequently where change is rapid. Use the method when developing a new offer, revising an existing one or investigating declining satisfaction or adoption.

It helps answer questions such as:

Which valuable opportunities are underserved?

Are customers receiving the outcomes and benefits they expected?

Which needs remain poorly served by our offer and by alternatives?

Origins

Unmet need analysis has no single inventor. It developed through market research, needs-based segmentation, lead-user research, voice-of-the-customer methods and innovation practice. These traditions share a central principle: study the outcome people are trying to achieve and the limitations of current solutions before deciding what product to build.

What it is

The analysis looks for a meaningful gap between a desired customer outcome and current satisfaction with that outcome. The gap becomes an opportunity only when the need is important, sufficiently widespread or strategically valuable, and feasible for the organisation to address.

Why it matters

Products succeed by helping people make progress that matters to them. Building from an internal idea without confirming a need creates a high risk of producing features that customers will not value. A disciplined view of unmet needs gives product development a customer-grounded direction.

The method also separates a request from the need behind it. Customers may propose a feature because it is the solution they can imagine; the deeper outcome may be achievable in a simpler or more distinctive way.

How to use it

Define the customer group and situation first. Gather qualitative evidence through Qualitative Surveys, Focus Groups, interviews (Interviews) and direct observation. Ask about goals, current alternatives, moments of frustration, workarounds and consequences—not only requested features.

Combine that evidence with search behaviour, support contacts, returns, reviews and product-usage data. Google Trends can reveal changing interest, though search frequency does not by itself prove an unmet need. Convert suitable material using Text Capture and use Text Analytics to identify recurring themes.

Translate observations into outcome statements, then measure importance and current satisfaction with a broader relevant sample. Prioritise outcomes that are highly important and poorly satisfied. Before investing, test whether a proposed concept improves the outcome, whether customers will adopt or pay for it, and whether the opportunity fits the organisation’s capabilities.

Practical example

Sony’s Walkman illustrates how an existing capability can be redirected toward an overlooked use. In 1979, Sony already sold the Pressman, a portable recorder intended for journalists. Honorary chairman Masaru Ibuka saw an employee using a similar device to listen to music and wanted a lighter way to enjoy music while travelling. He and chairman Akio Morita asked the tape-recording division to create a smaller version.

The team removed the recording function, added stereo circuitry, a headphone connection and lightweight earphones. The resulting Walkman served the need for personal music on the move and eventually sold more than 150 million units. The example shows that unmet needs may be discovered by observing unconventional use of an existing product, then simplifying the offer around that use.

Top practical tip

Combine what customers say with what they do. Interviews reveal motives and language; reviews, support records, search patterns and workarounds reveal recurring friction. Convergence across methods is stronger than a single loud request.

Top pitfall

Do not equate every complaint or feature request with a viable market opportunity. Confirm the underlying outcome, its importance, current satisfaction, prevalence, willingness to change and economic feasibility before committing development resources.