User Segmentation

What Is This?

Overview

User segmentation is the process of dividing a user base into distinct groups based on shared behaviors, motivations, needs, and jobs-to-be-done (JTBD). Rather than treating all users as a single homogeneous audience, this skill analyzes feedback data to surface hidden customer groups that behave differently, want different outcomes, and require different product responses. The result is a structured segmentation model that product teams can act on immediately.

This skill draws on qualitative and quantitative feedback sources, including survey responses, support tickets, interview transcripts, and usage logs. It applies behavioral clustering and JTBD frameworks to identify at least three distinct user segments, each defined by a consistent pattern of goals, pain points, and decision-making criteria. The output gives teams a shared language for discussing their users with precision.

The segmentation model produced by this skill is not a static persona document. It is a working analytical framework that connects user behavior to product decisions, prioritization, and messaging strategy.

Who Should Use This

• Product managers who need to prioritize features for specific user groups rather than a generic average user
• UX researchers analyzing large volumes of mixed feedback that appear contradictory without segmentation context
• Growth and marketing teams building targeted acquisition or retention campaigns based on behavioral profiles
• Designers who need to understand the distinct workflows and mental models of different user types before making interface decisions
• Startup founders validating whether their product serves one coherent audience or multiple distinct ones
• Customer success teams mapping support patterns to underlying user needs and segment-specific friction points

Why Use It?

Problems It Solves

• Conflicting feedback from different user types gets averaged out, leading to product decisions that satisfy no one fully. Segmentation separates these signals so each group is heard accurately.
• Teams build features for an imagined average user who does not actually exist in the data, wasting development cycles on low-impact work.
• Roadmap prioritization becomes political rather than evidence-based when there is no shared model of who the users are and what they need.
• Messaging and onboarding flows fail to convert because they address the wrong job-to-be-done for a given user type.
• Support and success teams cannot scale their responses efficiently without knowing which segment a user belongs to and what that implies about their needs.

Core Highlights

• Identifies a minimum of three distinct user segments from raw feedback data
• Applies jobs-to-be-done framing to define each segment by motivation, not just demographics
• Surfaces behavioral patterns that distinguish segments from one another
• Produces segment profiles with named characteristics, goals, and friction points
• Connects segment definitions to actionable product and messaging implications
• Works with qualitative data, quantitative data, or a combination of both
• Reduces noise in feedback analysis by attributing signals to specific user groups
• Provides a reusable segmentation model that can be updated as new data arrives

How to Use It?

Basic Usage

Provide the skill with a body of user feedback. This can be raw text, structured survey exports, or a combined dataset. A minimal invocation looks like this:

Input: [paste user feedback data or upload transcript file]
Task: Segment users based on behavior, JTBD, and needs.
Output format: At least 3 named segments with profiles.

The skill will parse the input, identify recurring behavioral and motivational patterns, and return a structured segmentation report.

Specific Scenarios

Scenario 1: Analyzing survey responses after a product launch. Export open-ended survey responses to a CSV file and pass the text column to the skill. It will cluster responses by underlying job-to-be-done and return distinct segments with representative quotes.

Scenario 2: Processing support ticket archives. Feed a batch of support tickets into the skill with a note about the product context. The skill identifies which user types generate which complaint patterns, producing segments defined by friction rather than demographics.

Real-World Examples

A B2B SaaS team discovers through segmentation that their user base contains three groups: power users automating workflows, occasional users completing one-off tasks, and administrators managing access. Each group needs a different onboarding path.

A consumer app team finds that feedback about "too complicated" comes entirely from one segment, while another segment actively requests more advanced controls. Without segmentation, these signals cancel each other out.