For a long time, customer segmentation seemed straightforward.

Industry.

Company size.

Job title.

Location.

Age.

These categories are easy to collect and even easier to put into a spreadsheet.

But while working on products, I’ve found that these labels often tell us less than we expect.

Two customers can have the same job title, work in the same industry, and belong to companies of similar size, yet need completely different things from the product.

That’s where problem-based segmentation becomes useful.

Instead of asking:

“Who is this customer?”

We ask:

“What problem are they trying to solve?”

That shift can change how we prioritize, design, and position a product.

What Is Problem-Based Segmentation?

Problem-based segmentation groups customers according to the problem or job they’re trying to accomplish rather than their demographic or firmographic characteristics.

Imagine an assessment platform.

One customer might use it to reduce hiring time.

Another might use it to improve candidate quality.

Another might use it for leadership development.

They may all use the same platform.

They may even use many of the same features.

But the problems they’re solving are different.

And that difference matters.

Why Traditional Segmentation Can Mislead You

Traditional segmentation isn’t useless.

Company size can influence purchasing processes.

Industry can influence regulatory requirements.

Role can influence workflows.

But these characteristics don’t necessarily tell you why someone needs your product.

I’ve seen two enterprise customers have completely different priorities despite looking almost identical from a firmographic perspective.

Meanwhile, two smaller customers in different industries may have almost identical problems.

If we group only by who they are, we can miss the reason they bought the product in the first place.

Start With the Customer’s Job

The easiest way to identify problem-based segments is to listen to how customers describe their work.

Instead of asking:

“What features do you want?”

Ask:

“What are you trying to accomplish?”

Then dig deeper.

What makes this difficult today?

How are you solving it currently?

How often does the problem occur?

What happens if you don’t solve it?

What would a successful outcome look like?

These questions reveal the underlying problem instead of simply collecting feature requests.

Different Problems Can Have Different Value

Not every customer problem deserves the same priority.

Suppose ten customers ask for the same feature.

At first glance, it looks like an obvious roadmap priority.

But imagine five of them are trying to solve a minor inconvenience, while the other five are trying to eliminate a process that costs them hundreds of hours every year.

The feature request is identical.

The value of solving the underlying problem isn’t.

Problem-based segmentation helps you see that difference.

It Changes How You Prioritize

This is where I find problem-based segmentation particularly useful.

Instead of saying:

“This feature is requested by 30 customers.”

We can ask:

“Which important customer problems does this feature address?”

That creates a much better prioritization conversation.

A feature that solves a high-impact problem for a smaller but strategically important segment may deserve more attention than a feature that addresses a low-impact problem across a larger audience.

It’s about importance, not just volume.

It Also Improves Product Positioning

Problem-based segments can make positioning much sharper.

Instead of saying:

“Our platform helps businesses manage assessments.”

You can speak directly to a specific problem:

“Reduce the time your team spends screening candidates.”

Or:

“Standardize leadership assessments across your organization.”

The product hasn’t changed.

The message has become more relevant.

Customers recognize themselves in the problem.

Don’t Create a Segment for Every Problem

There’s a risk of going too far.

If every slightly different problem becomes its own segment, segmentation becomes impossible to manage.

A useful segment should be meaningful enough to influence a product decision.

If two customers have slightly different problems but need the same product experience, separating them may not add much value.

The best segments are actionable.

Combine Problems With Behaviour

Problem-based segmentation becomes even more powerful when combined with actual product behaviour.

For example:

Problem: Reduce manual work
Behaviour: Uses automation heavily

versus:

Problem: Reduce manual work
Behaviour: Uses the product infrequently

The underlying problem is similar, but the customer’s relationship with the product is different.

That can lead to very different product opportunities.

Final Thought

I’ve come to believe that the most useful customer segments aren’t always the easiest ones to define.

Age is easy.

Industry is easy.

Company size is easy.

Understanding the problem someone is trying to solve requires more work.

But that effort can lead to much better product decisions.

Because customers don’t buy products because they belong to a particular demographic.

They buy because something is difficult, expensive, frustrating, risky, or important enough that they want it solved.

So when you’re deciding who your product is really for, don’t stop at:

“Who are they?”

Ask the more important question:

“What problem brought them here?”

That answer may tell you far more about your product’s true market than any demographic profile ever could.