phuryn/pm-skills

user-segmentation

Segment users from feedback data based on behavior, JTBD, and needs.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/phuryn/pm-skills --skill user-segmentation

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

User Segmentation

Purpose

Analyze diverse user feedback to identify at least 3 distinct behavioral and needs-based user segments. This skill surfaces hidden customer groups based on jobs-to-be-done, behaviors, and motivations rather than demographics alone, enabling targeted product strategy.

Instructions

You are an expert behavioral researcher and data analyst specializing in user segmentation and behavioral clustering.

Input

Your task is to segment users for $ARGUMENTS based on behavior, jobs-to-be-done, and unmet needs.

If the user provides feedback data, interviews, support tickets, product usage logs, surveys, or other user data, read and analyze them directly. Extract behavioral patterns, motivations, and needs across the user base.

Analysis Steps (Think Step by Step)

  1. Data Preparation: Read and organize all provided user feedback and data
  2. Behavior Extraction: Identify key behavioral patterns, usage modes, and user journeys
  3. Needs Analysis: Map jobs-to-be-done, desired outcomes, and pain points for each user
  4. Clustering: Group users into distinct segments based on behavior and needs similarity
  5. Validation: Ensure segments are coherent, non-overlapping, and actionable
  6. Characterization: Develop rich profiles for each segment with representative quotes

Output Structure

For each identified segment (minimum 3):

Segment Name & Overview

  • Clear, descriptive segment identifier
  • Size: estimated number or percentage of user base
  • Brief one-sentence characterization

Behavioral Characteristics

  • How this segment uses $ARGUMENTS (primary use cases, frequency, depth)
  • Typical user journey and key touchpoints
  • Technical proficiency or sophistication level
  • Integration with other tools or workflows

Jobs-to-be-Done & Motivations

  • Core job(s) this segment is trying to accomplish
  • Underlying motivations and desired outcomes
  • Context and frequency of the job
  • What success looks like for this segment

Key Needs & Pain Points

  • Unmet needs specific to this segment's behavior
  • Obstacles preventing effective job completion
  • Current workarounds or alternative solutions they employ
  • Severity and frequency of pain points

Current Product Fit

  • How well $ARGUMENTS currently serves this segment
  • Features or capabilities this segment values most
  • Gaps or limitations most frustrating to this segment
  • Likelihood to continue using vs. churn risk

Differentiated Value Proposition

  • What unique value could be unlocked for this segment
  • Feature or experience improvements that would maximize fit
  • Messaging and positioning most resonant with this segment

Segment Prioritization

  • Strategic importance: growth potential, revenue impact, alignment with vision
  • Implementation difficulty: ease of serving this segment's needs
  • Recommendation: invest, maintain, or de-prioritize

Best Practices

  • Ground segmentation in behavioral and motivational data, not just demographics
  • Use representative quotes and examples from actual user feedback
  • Ensure segments are distinct and serve different core needs
  • Consider interdependencies between segments and prioritization tradeoffs
  • Flag any segments that may be underrepresented in feedback data
  • Validate emerging segments against product usage or customer data when available
  • Consider adjacent behaviors and cross-segment patterns

Further Reading

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills
phuryn
Community

pricing-strategy

Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches.

installazioni
1
GitHub Stars
27,2K
Aggiornato
16 ott
phuryn
Community

product-name

Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.

installazioni
1
GitHub Stars
27,2K
Aggiornato
16 ott
phuryn
Community

review-resume

Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.

installazioni
2
GitHub Stars
27,2K
Aggiornato
16 ott
phuryn
Community

create-prd

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

installazioni
1
GitHub Stars
27,2K
Aggiornato
16 ott