PM Gym

User Segmentation

Slice a huge, fuzzy audience into groups you can actually build for

"Everyone" is not a target audience. Segmentation is how product teams split a crowd of users into meaningful groups — so features, pricing, and messaging can fit real people instead of an imaginary average.

Step-by-step lessons

From Chaos to Clarity

Three short lessons on how product teams group massive crowds into high-opportunity segments — no jargon required.

1

Users vs. Customers

A classic beginner mistake: assuming the person using the product is the same person paying for it. Often they're not — and they want completely different things.

Everyday example — dog food

Who eats the dog food? The dog (the user). Who chooses the brand and pays for it? The owner (the customer). The dog cares about taste; the owner cares about price, healthy ingredients, and not lugging a heavy bag. That's why dog-food ads talk about your pet's shiny coat and your peace of mind — they're selling to the owner about the dog. Miss this split and you might build a product the user loves but the buyer won't pay for, or vice versa.

Uses it

The User

Interacts with the product daily. Cares about ease, speed, and getting their task done.

Pays for it

The Customer

Holds the budget and makes the buying decision. Cares about price, safety, and value for money.

Quick check

Sarah enters her billing details to upgrade the family plan so her 6-year-old son Leo can safely stream dinosaur audio stories on his iPad. Who is who?

2

The Four Ways to Slice an Audience

There are four standard lenses for splitting an audience into segments. Each answers a different question:

Everyday example — sorting party guests

Imagine describing the people at a big party four different ways. Demographics: "mostly 20-to-40-year-olds." Geographics: "half came from across town, half are neighbors." Psychographics: "the adventurous, outgoing crowd." Behavioral: "the ones who actually got up and danced all night." For a product team, that last lens — what people actually do — is usually the most useful, because someone might call themselves a party animal but stand by the wall all night. Actions reveal more than labels.

The Who

Demographics

Fixed facts about people: age, income, job title, industry.

The Where

Geographics

Location: country, city size, climate, urban vs. rural.

The Why

Psychographics

Inner world: values, lifestyle, attitudes, identity.

The How

Behavioral

What people actually do: usage frequency, features touched, purchase patterns.

A rule worth remembering

Marketing teams lean on demographics to plan ad spend. Product teams live in behavioral data — because what people say about themselves in surveys rarely matches what the usage logs show they actually do.

Quick check

In a fitness app you find a clean cluster of users who log in five times a week, connect external devices, and average 45-minute sessions. Which slicing method is this?

3

Needs-Based Segmentation

The most powerful slicing method groups people not by who they are or what they do, but by the problem they share. This is where segmentation meets the Jobs-to-be-Done mindset.

Everyday example — the hardware store

A smart hardware store doesn't really care whether you're young or old, rich or poor. It groups you by the project you walked in for: "fixing a leaky tap," "building a deck," "painting a room." A retired grandmother and a 25-year-old flat-sharer fixing the same leak need the exact same aisle. Grouping by shared need — not shared traits — points you straight at what to build (or stock), which is why it's the product manager's most powerful lens.

The milkshake principle, again

When researchers helped a restaurant sell more milkshakes, sorting customers by income or age revealed nothing. Grouping by situation revealed a hidden segment: people buying milkshakes at 7 AM.

Their shared need: a boring 30-minute commute, one free hand, and a stomach that should stay full until noon. Age and income were irrelevant.

The opportunity appeared only when the grouping was based on shared needs, not shared traits.

The interview tactic: 5 Whys

In user conversations, ask "why?" repeatedly to move past surface complaints and uncover the deeper progress people are seeking.

Review the concepts

Segmentation Flashcards

Five cards covering the vocabulary and quality checks. Click to flip.

Terminology Card 1 of 5

The User

Click to flip

Tip: say the answer out loud before flipping.

Explanation

In practice

1 / 5
Apply what you learned

Practice Scenarios

15 situations that test whether you can slice an audience in ways that actually guide product decisions — user vs. customer, the right lens, MECE segments, and choosing a target. Pick the strongest move, then read why the others miss.

Scenario 1

You're designing a wearable health tracker for senior citizens. The senior wears it; their adult child pays the subscription and monitors the dashboard.

How should you classify them — and what follows from it?

Scenario 2

You manage a workplace tool like Slack and need to decide next quarter's feature priorities.

Which segmentation will guide those decisions best?

Scenario 3

A teammate proposes splitting your audience into two segments: 'young users' and 'power users'.

What's wrong with this scheme?

Scenario 4

You're a small startup with limited resources and five plausible customer segments, all somewhat attractive. Leadership wants to serve all five at once.

What's the wiser segmentation-driven strategy?

Scenario 5

A survey says 80% of users "care deeply about privacy." But your usage logs show almost no one changes the default privacy settings or reads the policy.

Which signal should a product team trust for segmentation, and why?

Scenario 6

A B2B PM segments purely by company size (SMB, mid-market, enterprise) and assumes everyone within each tier wants the same thing.

What's the limitation?

Scenario 7

Your team defines a segment as "users who would benefit from our advanced analytics." When you try to build a campaign for them, no one can pull a list.

Which segment-quality test does this fail?

Scenario 8

Analysis reveals a genuinely distinct, well-defined segment with a unique need — but it contains only 40 users, and building for them would take months.

Which test fails, and what does it mean?

Scenario 9

A design team creates one 'average user' by blending all segments together: someone who is 38, uses the app 3x a week, and wants both simplicity and power features.

What's the danger of designing for this 'average'?

Scenario 10

In a kids' education app, the child uses it, a parent pays, and a teacher recommends it to the whole class.

How does segmentation handle three parties?

Scenario 11

Two behavioral segments emerge: 'power users' (daily, deep feature use) and 'dormant users' (signed up, barely return). A PM wants to build advanced features to please the power users.

What should segmentation prompt you to consider first?

Scenario 12

A marketer proposes segments: "Millennials," "People who like coffee," and "Users in cold climates." Your PM instinct says something's off.

What's structurally wrong with this set?

Scenario 13

You discover a needs-based segment — "users who need to collaborate with clients outside their company" — that cuts across every age, region, and company size.

Why is this often more valuable than a demographic segment?

Scenario 14

A dating app's user (the single person swiping) and its 'customer' (also the single person, who pays for premium) are the same individual. A teammate says "so the user/customer split is useless here."

Is that right?

Scenario 15

Your team has clean, MECE, measurable segments. Leadership asks: "Great — so which one do we actually target first?"

What factors should decide the target segment?

Lock it in

Guess the Term

Read the clues and name the concept. The fewer clues you need, the more points you score.

Round 1 Score 0
Keep it handy

Segmentation Quick Reference

The methods and the quality checklist on one screen.

Which Method for What

D

Demographics

Best for sizing markets and planning marketing budgets.

B

Behavioral

Best for feature priorities and early churn warnings — actions don't lie.

N

Needs-based

Best for defining core features and finding unserved market gaps.

Is Your Segment Any Good?

A useful segment passes all three checks (and segments together should be MECE — no overlaps, no gaps):

1

Measurable

Can you actually query your data to find these people?

2

Actionable

Could you build something specifically for them?

3

Substantial

Is the group big enough to justify the effort?

Segmenting vs. Targeting

Slicing the crowd is step one; choosing who to serve is step two.

Segmentation

Splitting the whole audience into meaningful groups.

Targeting

Choosing which segment(s) to actually serve.

Beachhead

The one segment you dominate first, then expand from — vital for small teams.

Pick on

Size × value × fit × winnability — not raw headcount alone.

Common Mistakes

Where segmentation goes wrong.

The "average user"

Blending segments creates a person who doesn't exist. Design for real groups.

Mixing lenses

"Millennials + coffee lovers + cold climates" overlap. Use one consistent lens.

Trusting stated over revealed

What people say ≠ what logs show. Segment on behavior.

Traits over needs

Age/size rarely predict what to build. Prefer shared-need segments.

Notification