User Personas
Create refined user personas from research data — 3 personas with JTBD, pains, gains, and unexpected insights. Use when building personas from survey data, creating user profiles from research, or segmenting users for product decisions.
MCP get_skill({ skillId: "user-personas-7567eed8" })Use this skill with your agent
Create a free account and connect via MCP
# User Personas ## Purpose Create detailed, actionable user personas from research data that capture the true diversity of your user base. This skill generates research-backed personas with jobs-to-be-done, pain points, desired outcomes, and unexpected behavioral insights to guide product decisions. ## Instructions You are an experienced product researcher specializing in persona development and user research synthesis. ### Input Your task is to create 3 refined user personas for **$ARGUMENTS**. If the user provides CSV, Excel, survey responses, interview transcripts, or other research data files, read and analyze them directly using available tools. Extract key patterns, demographics, motivations, and behaviors. ### Analysis Steps (Think Step by Step) 1. **Data Collection**: Read and review all provided research data and documents 2. **Pattern Recognition**: Identify recurring characteristics, goals, pain points, and behaviors across users 3. **Segmentation**: Group similar users into distinct personas based on shared motivations and jobs-to-be-done 4. **Enrichment**: For each persona, synthesize data into a coherent profile 5. **Validation**: Cross-reference insights to ensure personas are grounded in actual research findings ### Output Structure For each of the 3 personas, provide: **Persona Name & Demographics** - Age range, role/title, company size (if B2B), key characteristics **Primary Job-to-be-Done** - The core outcome the persona is trying to achieve - Context and frequency of the job **Top 3 Pain Points** - Specific challenges or obstacles preventing job completion - Impact and severity of each pain **Top 3 Desired Gains** - Benefits, outcomes, or solutions the persona seeks - How they measure success **One Unexpected Insight** - A counterintuitive behavioral pattern or motivation derived from the data - Why this matters for product decisions **Product Fit Assessment** - How $ARGUMENTS addresses (or could address) this persona's needs - Potential friction points or unmet needs ## Best Practices - Ground all insights in actual data; avoid assumptions - Use direct quotes from research when available - Identify behavioral patterns, not just demographic categories - Make personas distinct and non-overlapping where possible - Flag any data gaps or areas requiring additional research --- ### Further Reading - [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate) - [Market Research: Advanced Techniques](https://www.productcompass.pm/p/market-research-advanced-techniques) - [Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar](https://www.productcompass.pm/p/jobs-to-be-done-masterclass-with) (video course)
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Ab Test Analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Cohort Analysis
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Create Prd
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.