Build Actionable User Personas from Data

This skill builds user personas grounded in real research data, covering demographics, psychographics, behavioral patterns, goals/motivations, pain points, and context of use. It integrates multiple data sources (interviews, surveys, analytics, support tickets, market research, A/B test results) and produces a full persona template (quick profile with quote, background, goals with success metrics, pain points with current workarounds, behavioral usage patterns, decision-making process, primary/edge-case scenarios, and influence/environment). It applies a validation checklist (15-20+ interviews, representing 15%+ of the user base, measurable goals, clear differentiation), a quantitative foundation (demographic splits grounded in actual user data covering 80%+ of users, session length, feature adoption rates, and conversion funnels tied to business metrics), Jobs-to-be-Done framing (functional/emotional/social job per persona), a persona prioritization matrix (impact vs. volume), dynamic elements (maturity stages, seasonal variation, life-stage evolution), and cross-functional activation guidance (product, design, marketing, sales, support) plus a quarterly maintenance cadence.

Use this skill when developing or refreshing user personas - synthesizing interview and analytics data into a persona template, validating a persona against the research-sufficiency checklist, framing a persona's functional/emotional/social jobs-to-be-done, prioritizing personas on an impact-versus-volume matrix, or distributing personas cross-functionally to product, design, marketing, sales, and support.

It does not cover the underlying user research methodology (interview scripts, survey design) in depth - it is focused specifically on synthesizing existing research into actionable, validated persona artifacts. Common pitfalls it explicitly warns against: generic surface-level demographics without behavioral insight, building a persona without substantial user research behind it, treating personas as static rather than updating them as the product and market evolve, maintaining too many personas (cap at 3-5 primary) which dilutes focus, letting current product features bias what the persona becomes, and setting persona priority by internal team politics rather than data.

Inputs are typically qualitative interview data and quantitative usage/survey data. Outputs include a structured persona document, for example the goals and pain points sections:

### Goals & Motivations
### Primary Goals
1. [Specific goal with measurable outcome]
2. [Secondary goal]
3. [Aspirational goal]

### Success Metrics
- [How they measure success]
- [Key performance indicators they care about]

### Pain Points & Challenges
### Current Frustrations
1. **[Pain Point Category]**: [Specific description and impact]
2. **[Pain Point Category]**: [Specific description and impact]

Other outputs include a validation checklist (interview count, user-base representation percentage, measurable goals), a Jobs-to-be-Done breakdown (functional/emotional/social job), a persona prioritization matrix (high/low impact vs. high/low volume), one-page persona summary cards, and a cross-functional usage guide mapping personas to product/design/marketing/sales/support activities.

Product managers and UX researchers building or refreshing user personas who need data-grounded, validated, and cross-functionally actionable personas rather than generic demographic sketches.