User Personas

What Is This?

Overview

User Personas is a structured skill for transforming raw research data into detailed, actionable user profiles that represent the core segments of your audience. Rather than relying on assumptions or generic archetypes, this skill processes survey responses, interview notes, and behavioral data to produce three refined personas, each grounded in real evidence. Each persona includes jobs-to-be-done (JTBD) frameworks, documented pain points, identified gains, and unexpected insights that surface patterns researchers might otherwise overlook.

The skill follows a systematic approach to persona construction, ensuring that each profile captures meaningful differences across your user base rather than producing superficial variations of the same archetype. By anchoring every persona attribute to source data, teams receive profiles that hold up under scrutiny during product reviews, stakeholder presentations, and design critiques. The output is structured for immediate use in product roadmaps, UX design briefs, and marketing strategy documents.

Unexpected insights are a deliberate component of this skill. Beyond standard demographic and behavioral attributes, the skill surfaces contradictions, edge behaviors, and motivations that standard persona templates tend to flatten or ignore. These insights frequently become the most valuable inputs for product differentiation and feature prioritization.

Who Should Use This

• Product managers who need to segment users before writing feature specifications or prioritizing a backlog
• UX researchers who want to translate interview and survey data into shareable, team-ready deliverables
• Designers building user journey maps or service blueprints who require grounded audience profiles
• Startup founders validating product-market fit by understanding who their early adopters actually are
• Marketing strategists developing messaging frameworks and channel strategies for distinct audience segments
• Growth teams analyzing behavioral cohorts to identify friction points and conversion opportunities

Why Use It?

Problems It Solves

• Research data sits in spreadsheets and interview transcripts without being translated into usable product inputs
• Teams build features based on assumed user needs rather than documented evidence, leading to low adoption
• Personas created without a consistent framework become outdated quickly and lack credibility with stakeholders
• User diversity gets collapsed into a single generic profile, causing product decisions to serve no segment particularly well
• Insights from qualitative research are lost between research cycles because they are never formalized into reference documents

Core Highlights

• Generates exactly three personas to balance coverage with focus, avoiding the trap of too many profiles
• Each persona includes a full JTBD statement structured around functional, emotional, and social dimensions
• Pain points are ranked by severity and frequency, not listed as flat inventories
• Gains are tied to specific product interactions rather than abstract aspirations
• Unexpected insights section captures behavioral contradictions and non-obvious motivations
• Output format is compatible with Notion, Confluence, and standard design documentation tools
• Personas are traceable back to source data, supporting research credibility in stakeholder reviews

How to Use It?

Basic Usage

To invoke this skill, provide your research data as structured input. A minimal invocation looks like this:

Skill: user-personas
Input:
  - survey_responses: survey_export.csv
  - interview_notes: user_interviews_q2.md
  - sample_size: 47
  - product_context: "B2B project management tool for remote teams"

The skill processes the input and returns three persona documents in markdown format, each containing name, demographic summary, JTBD statement, pain points, gains, and the unexpected insights section.

Specific Scenarios

When building personas from survey data alone, include response distributions and open-text fields. The skill uses frequency analysis on closed responses and thematic clustering on open text to identify distinct segments before constructing profiles.

When segmenting users for a product pivot, provide both current user data and target audience research. The skill will flag where existing personas diverge from target profiles, giving product teams a clear gap analysis alongside the persona output.

Real-World Examples

A SaaS company used this skill after conducting 30 user interviews for a document collaboration tool. The output identified a power-user segment whose primary JTBD was audit compliance rather than collaboration speed, a finding that redirected the Q3 roadmap toward version history and access controls.

A consumer app team applied the skill to post-launch survey data and discovered that their assumed primary persona, a young professional, was actually the third most active segment. The unexpected insights section flagged retirees as the highest-engagement cohort, prompting a redesign of the onboarding flow.

Important Notes

Requirements

• A minimum dataset of 20 research participants is recommended for statistically meaningful segmentation
• Input data must include at least one qualitative source, such as interview notes or open-text survey responses
• Product context must be provided so persona attributes are scoped to relevant behaviors and motivations