user-segmentation

Segment an existing user base into behaviour- and needs-based groups from feedback and usage data.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/MilUX-Ltd/footing --skill user-segmentation-milux-ltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-segmentation
Source: https://github.com/MilUX-Ltd/footing/tree/main/footing/template/Skills/pm-skills/user-segmentation
Command: npx skills add https://github.com/MilUX-Ltd/footing --skill user-segmentation-milux-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often treat their users as one homogeneous group or segment them by superficial traits like job title, which hides the distinct groups with different behaviours, needs, and pains inside the user base. This Skill turns raw feedback and usage data into a grounded segmentation model. ## Core Features & Use Cases - Behaviour and needs clustering: Extracts usage modes, journeys, jobs-to-be-done, and pains from feedback, interviews, support tickets, usage logs, and surveys, then clusters them into at least three distinct, non-overlapping segments. - Structured segment profiles: Produces for each segment a name, size estimate, behaviour description, motivations, unmet needs, current fit assessment, improvement opportunities, and an invest/maintain/de-prioritise recommendation. - Use Case: A product team with hundreds of mixed survey responses and support tickets uses this Skill to discover that their users split into four groups with very different workflows, then prioritises the roadmap toward the highest-value segment. ## Quick Start Analyse the attached user feedback and usage data and segment our user base into distinct behaviour- and needs-based groups with a profile for each.

Frequently Asked Questions about user-segmentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I segment users from feedback and usage data?▼

Prepare your feedback, interviews, support tickets, usage logs, and surveys, then extract behaviours and needs, cluster them into distinct non-overlapping groups, and validate each segment for coherence and actionability. Characterise each segment with representative user quotes.

What is the difference between user segmentation and market segmentation?▼

User segmentation divides an existing user base by behaviour and need, while market segmentation maps the customer market by purpose. User segments should sit inside customer-side purpose segments so the two models stay compatible.

Should user segments be based on demographics or job titles?▼

No. Segment on the job each user group is doing and the conditions they do it under, not on job title or department. Users judge a product on the experience of using it in their real day-to-day work.

How many user segments should a segmentation model have?▼

Produce a minimum of three distinct, non-overlapping segments. Each segment needs a name, estimated size, behaviour profile, needs and pains, current fit assessment, and a prioritisation call of invest, maintain, or de-prioritise.

What are the limitations of behaviour-based user segmentation?▼

Segments can be thin or unreliable when the underlying data is sparse, so segments with limited supporting data should be explicitly flagged. The method also depends on having real feedback or usage data rather than assumptions.