Don’t Group Users by Who They Are.  Group Them By What They're Trying to Do.

If your segmentation model doesn't change what you build, how you onboard, or how you design the experience, then it's not really segmentation. It's labeling.

And labeling is what most demographic segments are. "SMB Fintech." "Enterprise HR Leaders." "Millennial Prosumers." They fill slides. They sound strategic. They produce no meaningful design decisions.

Should the onboarding be different for these segments? Should the empty state change? Should the first-run experience be shorter, safer, more guided? Those questions need answers. Demographic segments can't provide them.

Job-based segmentation can. Because it groups people by the thing that actually determines what they need from the experience: what they're trying to accomplish, in what situation, with what forces working for and against them.

One Person, Five Jobs, Five Different Experiences

Spotify has over 600 million users. Segmenting them by age, location, or subscription tier tells you almost nothing about what any of them need from the product at any given moment.

Because the same person hires Spotify for completely different jobs throughout a single day — and each job has different experience requirements.

6:45 AM, getting ready. The job is "fill the silence with something familiar while I wake up." Low attention. Low stakes. The experience requirement: surface something comfortable fast, no decisions required. Autoplay. A Daily Mix. The last thing this person needs is a browse screen.

8:15 AM, commuting. The job is "make this commute feel shorter and less miserable." Moderate attention, but hands aren't free. The experience requirement: minimal interaction, no visual dependence, long uninterrupted playback. A podcast. Your Daily Drive. Controls need to work through headphone buttons and car systems.

10:30 AM, deep work. The job is "block out the open office and stay in flow for the next two hours." High attention on something else entirely. The experience requirement: invisible. No surprises, no jarring transitions, no notifications. A Focus playlist. Lo-fi beats. The product needs to disappear completely.

5:45 PM, at the gym. The job is "match my energy level and keep my intensity up." Physical activity, high arousal, phone in a pocket or armband. The experience requirement: high-energy music that matches pace, no interruptions to momentum, controls accessible without looking at the screen.

9:00 PM, on the couch. The job is "discover something new that fits my mood right now." Low energy, browsing mindset, open to exploration. The experience requirement: surface interesting options, make discovery feel effortless, reward curiosity without overwhelming.

Same person. Same subscription. Five different jobs. Five different sets of experience requirements. Five different definitions of what "good" means.

Spotify knows this. Their internal research team built what they call "listening modes" — studying how users interact with the product differently depending on context. They used eye-tracking glasses to observe people listening while commuting, studying, cooking, and exercising.

What they found wasn't different types of users. It was different types of moments, each with different attention levels, different interaction needs, and different definitions of value.

That's job-based segmentation in practice: grouping by what someone is trying to accomplish in a specific situation, not by who they are on paper.

Job-Based Segments

A job-based segment isn't a persona with different labels. It has four elements, and all four are necessary to produce design decisions.

The progress they're trying to make. Not tasks. Progress. Not "listen to music" but "block out distractions and stay in flow." Not "create a report" but "walk into the meeting with a defensible narrative." The progress statement is what connects the segment to what the experience needs to deliver.

The situation that triggered action. What happened that made this job active right now? For Spotify's commute job, the trigger is leaving the house. For a B2B tool, the trigger might be a missed deadline, a new boss, or a competitor's output that made theirs look amateur. The situation is what turns a latent job into an active one, and it determines how much urgency the user brings.

The context constraints. Time pressure. Stakes. Social exposure. Physical environment. Whether they're alone or performing in front of colleagues. Whether they have thirty minutes or three. Context changes what "good" looks like for the same underlying need.

The force profile. Where do push, pull, habit, and anxiety sit for this person at this moment? This is what turns the segment from a description into a design input. A user with high anxiety needs safety signals and reversibility. A user with a strong habit toward the old way needs reduced switching cost and familiar patterns. A user with weak pull needs the value demonstrated concretely, not claimed.

Job-Based Segments Change What You Design

Understanding the job doesn't just change what you build — it changes how the experience needs to feel for each segment.

Looking at UX through a JTBD lens - aka ****JTBDUX - evaluates experiences through a set of questions that apply to any product: does the experience speak the language of the job the user is trying to do, or does it speak the product's internal language? Does it show the user they're making progress, or does it  leave them guessing?

Apply these questions to Spotify's discovery listener and the answers flip: the product needs to surface and engage. Show options. Reward curiosity. Make browsing feel effortless. Progress means "I found something I love."

Same product. Completely different design priorities, driven by which job segment you're designing for.

Onboarding strategies diverge by segment. A user with a high-intensity job — their problem is urgent, the cost of not solving it is visible — will push through rough onboarding if you deliver relief fast. A user with a low-intensity job — curious, not desperate — will abandon at the first sign of effort.

Same interface. Completely different tolerance for friction. The job segment tells you how much onboarding the user will endure — and how fast you need to deliver the first win.

Retention analysis becomes legible. Track retention by demographic segment and you get mush. Every demographic group contains multiple jobs. Track by job segment and patterns emerge: one job re-hires weekly and sticks for months. Another is a one-time burst that disappears. Another shows strong activation but collapses right before commitment — a classic anxiety spike.

Now you're not "optimizing retention." You're diagnosing which force is broken for which job.

The Force Profile as a Design Input

The force profile is what turns job-based segmentation from a research exercise into something that directly shapes the experience. When you know the forces for a specific job segment, you know what the experience needs to do:

• If push is low, the user isn't desperate. They're browsing. The experience needs to be effortless and immediately clear about what progress it enables — because they have no urgency carrying them through friction.
• If pull is weak, the value isn't vivid. The experience needs to show progress concretely. Show the output. Show the before and after. Make the better future tangible.
• If habit with the old way is strong, the experience needs to reduce switching costs. Import their data. Mirror familiar patterns. Meet them where they are instead of asking them to learn a new mental model from scratch.
• If anxiety is high, the experience needs safety signals. Reversibility. Preview before commit. Transparency about what happens next. Proof that other people in their situation made the switch successfully.

The segment doesn't just tell you who you're designing for. It tells you what the experience needs to feel like for that person in that moment.

Spotify doesn't serve "millennials who like music." It serves a person who needs invisible background audio at 10:30 AM and active discovery at 9:00 PM — and it designs different experiences for each. That's why the same product can feel essential in five different moments of the same day.

The question isn't "Who is our user?" It's "What is this person trying to do right now — and does our experience help them do it?"

That's the only segmentation question that changes what you build.