Product User Segment Definitions

Segment definitions the whole product team trusts: clear assignment rules, sized and profiled groups, scheduled refreshes, segment-level metrics and the calls on which users to build for first.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Product User Segment Definitions, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🧩 Product Management

Product User Segment Definitions

Defining distinct user segments from behaviour and needs so the product team can prioritise and measure work for each group separately.

  1. Inventory of segment definitions already in use
  2. Decisions the segmentation must serve
  3. Choosing the unit of segmentation
  4. Shortlist of candidate segmentation variables
  5. Data availability audit for segment attributes
  6. First-draft behavioural segments from usage data
  7. Needs-based segment hypotheses from existing research
  8. Segment sizing and value baseline
  9. Assignment rules and tie-breakers
  10. One-page profiles for each segment
  11. Segment dictionary as the single source of truth
  12. Scheduled refresh of segment membership
  13. Monthly segment metrics review
  14. Segment migration and drift watch
  15. Quarterly roadmap allocation by segment
  16. Segment label on research notes and tickets
  17. Segment quotas for research recruiting
  18. Annual segmentation review and re-cut
  19. Versioned change log for segment definitions
  20. Segment data quality checks
  21. Segmentation approaches compared
  22. Cluster analysis basics for product managers
  23. Comparing retention curves across segments
  24. Mix shift and Simpson's paradox in segment metrics
  25. Writing segment rules as queries and filters
  26. Sample sizes and confidence for small segments
  27. Personas versus segments in practice
  28. Presenting segments so stakeholders use them
  29. Merging or retiring overlapping segments
  30. Choosing the primary segment to serve next
  31. Segment-specific success measures for roadmap items
  32. Splitting a catch-all segment by behaviour
  33. Standard segment breakdown in launch readouts
  34. Reconciling product segments with sales and marketing tiers
  35. Choosing where segment logic lives
  36. Sizing an underserved segment opportunity
  37. Naming the segments you will not build for
  38. Segmentation readout to the leadership team
  39. Segment boundary workshop with design and engineering
  40. Segment brief for annual planning
  41. Company-wide segment dashboard launch
  42. Segment mix section for the quarterly business review
  43. Inheriting a segmentation as a new product manager
  44. Segmenting an early product with few users
  45. Merging segmentations after an acquisition
  46. Segment ownership across product teams
  47. Separating buyer and user segments in business software
  48. Predictive propensity scores within segments
  49. Lifetime value and cost to serve by segment
  50. Privacy and fairness review of segment attributes

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Inventory of segment definitions already in use

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most product teams already live with four or five competing segmentations: sales tiers by employee count, marketing personas, finance's plan types and whatever cohort filters an analyst saved last year.

First tasks

  • Search the analytics tool for saved cohorts and segment filters
  • Ask the sales, marketing and finance leads which customer groupings they report on
  • Record each definition's rule, owner and data source in one sheet
  • Mark every pair of definitions that classify the same account differently

Decisions the segmentation must serve

Segments built without a stated purpose end up as interesting charts that change nothing. Writing down the three to five product decisions the segmentation must inform, such as roadmap allocation, onboarding variants or which group a feature's success is judged on, gives every later choice of variable and boundary a test it can pass or fail.

First tasks

  • List product decisions from the last two quarters that lacked a clear segment view
  • Write each decision the segmentation must serve as one question
  • Name the decision owner beside each question
  • Agree the purpose statement with the product lead

Choosing the unit of segmentation

A business product can segment by individual user, by workspace or by paying account, and each gives different answers: one account can hold an admin power user and forty occasional viewers. Choosing the unit deliberately, and saying how the other levels roll up, prevents the same customer appearing in three segments depending on who ran the query.

First tasks

  • Write down how many users a typical account holds and the range
  • Test two candidate units against each decision in the purpose statement
  • Draft the roll-up rule between users and accounts
  • Review the chosen unit with the data engineer who will build it

Make it yours.

Install Product User Segment Definitions, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.