User Persona Creation

用户画像创建

Overview

概述

User personas synthesize research into realistic user profiles that guide design, development, and marketing decisions.

用户画像将研究内容整合为真实的用户档案，为设计、开发和营销决策提供指导。

When to Use

适用场景

Starting product design
Feature prioritization
Marketing messaging
User research synthesis
Team alignment on users
Journey mapping
Success metrics definition

启动产品设计时
功能优先级排序
营销信息制定
用户研究内容整合
团队对用户认知对齐
旅程地图绘制
成功指标定义

Instructions

操作步骤

1. Research & Data Collection

1. 研究与数据收集

python

undefined

python

undefined

Gather data for persona development

class PersonaResearch: def conduct_interviews(self, target_sample_size=12): """Interview target users""" interview_guide = { 'demographics': [ 'Age, gender, location', 'Job title, industry, company size', 'Experience level, education', 'Salary range, purchasing power' ], 'goals': [ 'What are you trying to achieve?', 'What's most important to you?', 'What does success look like?' ], 'pain_points': [ 'What frustrates you about current solutions?', 'What takes too long or is complicated?', 'What prevents you from achieving goals?' ], 'behaviors': [ 'How do you currently solve this problem?', 'What tools do you use?', 'How do you learn about new solutions?' ], 'preferences': [ 'How do you prefer to communicate?', 'What communication channels do you use?', 'When are you most responsive?' ] }

    return {
        'sample_size': target_sample_size,
        'interview_guide': interview_guide,
        'output': 'Interview transcripts, notes, recordings'
    }

def analyze_survey_data(self, survey_data):
    """Synthesize survey responses"""
    return {
        'demographics': self.segment_demographics(survey_data),
        'pain_points': self.extract_pain_points(survey_data),
        'goals': self.identify_goals(survey_data),
        'needs': self.map_needs(survey_data),
        'frequency_distribution': self.calculate_frequencies(survey_data)
    }

def analyze_user_data(self):
    """Use product analytics data"""
    return {
        'feature_usage': 'Which features are most used',
        'user_segments': 'Behavioral groupings',
        'conversion_paths': 'How users achieve goals',
        'churn_patterns': 'Why users leave',
        'usage_frequency': 'Active vs inactive users'
    }

def synthesize_data(self, interview_data, survey_data, usage_data):
    """Combine all data sources"""
    return {
        'primary_personas': self.identify_primary_personas(interview_data),
        'secondary_personas': self.identify_secondary_personas(survey_data),
        'persona_groups': self.cluster_similar_users(usage_data),
        'confidence_level': 'Based on data sources and sample size'
    }

undefined

class PersonaResearch: def conduct_interviews(self, target_sample_size=12): """Interview target users""" interview_guide = { 'demographics': [ 'Age, gender, location', 'Job title, industry, company size', 'Experience level, education', 'Salary range, purchasing power' ], 'goals': [ 'What are you trying to achieve?', 'What's most important to you?', 'What does success look like?' ], 'pain_points': [ 'What frustrates you about current solutions?', 'What takes too long or is complicated?', 'What prevents you from achieving goals?' ], 'behaviors': [ 'How do you currently solve this problem?', 'What tools do you use?', 'How do you learn about new solutions?' ], 'preferences': [ 'How do you prefer to communicate?', 'What communication channels do you use?', 'When are you most responsive?' ] }

    return {
        'sample_size': target_sample_size,
        'interview_guide': interview_guide,
        'output': 'Interview transcripts, notes, recordings'
    }

def analyze_survey_data(self, survey_data):
    """Synthesize survey responses"""
    return {
        'demographics': self.segment_demographics(survey_data),
        'pain_points': self.extract_pain_points(survey_data),
        'goals': self.identify_goals(survey_data),
        'needs': self.map_needs(survey_data),
        'frequency_distribution': self.calculate_frequencies(survey_data)
    }

def analyze_user_data(self):
    """Use product analytics data"""
    return {
        'feature_usage': 'Which features are most used',
        'user_segments': 'Behavioral groupings',
        'conversion_paths': 'How users achieve goals',
        'churn_patterns': 'Why users leave',
        'usage_frequency': 'Active vs inactive users'
    }

def synthesize_data(self, interview_data, survey_data, usage_data):
    """Combine all data sources"""
    return {
        'primary_personas': self.identify_primary_personas(interview_data),
        'secondary_personas': self.identify_secondary_personas(survey_data),
        'persona_groups': self.cluster_similar_users(usage_data),
        'confidence_level': 'Based on data sources and sample size'
    }

undefined

2. Persona Template

2. 用户画像模板

yaml

User Persona: Premium SaaS Buyer

---

yaml

User Persona: Premium SaaS Buyer

---

Demographics

Name: Sarah Chen Age: 34 Location: San Francisco, CA Job Title: VP Product Management Company: Series B SaaS startup (50 employees) Experience: 8 years in product management Education: MBA from Stanford, BS in Computer Science Income: $180K salary + 0.5% equity

Professional Context

职业背景

Industry: B2B SaaS (Project Management) Company Size: 50-200 employees Budget Authority: Can approve purchases up to $50K Buying Process: 60% solo decisions, 40% committee Evaluation Time: 4-6 weeks average

Goals & Motivations

目标与动机

Primary Goals:

Improve team productivity by 25%
Reduce project delivery time by 30%
Increase visibility into project status
Improve team collaboration across remote locations

Success Definition:

Team using tool daily
20% reduction in status meetings
Faster decision-making
Higher team satisfaction

Primary Goals:

Improve team productivity by 25%
Reduce project delivery time by 30%
Increase visibility into project status
Improve team collaboration across remote locations

Success Definition:

Team using tool daily
20% reduction in status meetings
Faster decision-making
Higher team satisfaction

Pain Points

痛点

Current Challenges:

Existing tool is slow and outdated
Poor mobile experience
Limited reporting capabilities
Difficult to customize for company needs
Vendor is unresponsive to feature requests

Frustrations:

Wasting time in status update meetings
Lack of real-time visibility into project health
Can't easily identify bottlenecks
Integration with other tools is difficult

Current Challenges:

Existing tool is slow and outdated
Poor mobile experience
Limited reporting capabilities
Difficult to customize for company needs
Vendor is unresponsive to feature requests

Frustrations:

Wasting time in status update meetings
Lack of real-time visibility into project health
Can't easily identify bottlenecks
Integration with other tools is difficult

Behaviors & Preferences

行为与偏好

Daily Tools:

Slack: Constant communication
Google Workspace: Document collaboration
Jira: Technical work tracking
Spreadsheets: Status reporting (workaround)

Work Patterns:

Typically works 8am-6pm Pacific
Checks email every 15 minutes
In meetings 50% of day
Works 20% of time outside office hours

Information Gathering:

Reads G2/Capterra reviews: High trust
Asks for peer recommendations: Very influential
Requests demos: Hands-on evaluation
Wants to see case studies: Similar companies

Decision Drivers:

ROI and measurable impact: 40%
User adoption potential: 30%
Ease of implementation: 20%
Price: 10%

Daily Tools:

Slack: Constant communication
Google Workspace: Document collaboration
Jira: Technical work tracking
Spreadsheets: Status reporting (workaround)

Work Patterns:

Typically works 8am-6pm Pacific
Checks email every 15 minutes
In meetings 50% of day
Works 20% of time outside office hours

Information Gathering:

Reads G2/Capterra reviews: High trust
Asks for peer recommendations: Very influential
Requests demos: Hands-on evaluation
Wants to see case studies: Similar companies

Decision Drivers:

ROI and measurable impact: 40%
User adoption potential: 30%
Ease of implementation: 20%
Price: 10%

Technology Comfort

技术适配度

Tech Savviness: High (uses 15+ tools daily) Mobile Usage: 40% of work on mobile Prefers: Intuitive UI, minimal training Adoption Speed: Fast (new tools in 1-2 weeks) Integration Importance: Very high

Customer Journey

用户旅程

Awareness: Product recommendations from peers Consideration: Reviews, demos, talk to customers Decision: Cost-benefit analysis, team input Onboarding: Expects self-service + minimal support Ongoing: Wants regular feature updates, responsive support

Communication Preferences

沟通偏好

Prefers: Email and Slack (avoid calls) Response Time: 4-24 hours typical Best Time: Tuesday-Thursday mornings Frequency: Weekly updates during evaluation Format: Data-driven, executive summaries preferred

Key Quotes

核心引用

"I need something that my team will actually use, not something I have to force them to adopt."

"Show me the data on time savings, not just promises."

"Our tool should work as hard as we do - seamlessly across all our devices and workflows."

"I need something that my team will actually use, not something I have to force them to adopt."

"Show me the data on time savings, not just promises."

"Our tool should work as hard as we do - seamlessly across all our devices and workflows."

Persona Importance

画像重要性

Primary Persona: YES (key decision maker) Frequency in User Base: 35% of customers Influence: High (recommends to peers) Revenue Impact: $30K ARR average

Marketing & Sales Strategy

营销与销售策略

Messaging:

Emphasize productivity gains and ROI
Highlight ease of adoption
Show mobile-first experience
Demonstrate integrations

Sales Approach:

Provide customer references (similar companies)
Offer flexible demo (self-service + guided)
Focus on time-to-value
Provide ROI calculator

Success Metrics:

50% adoption within 2 months
Net Promoter Score >50
Upsell to higher tier within 6 months

undefined

Messaging:

Emphasize productivity gains and ROI
Highlight ease of adoption
Show mobile-first experience
Demonstrate integrations

Sales Approach:

Provide customer references (similar companies)
Offer flexible demo (self-service + guided)
Focus on time-to-value
Provide ROI calculator

Success Metrics:

50% adoption within 2 months
Net Promoter Score >50
Upsell to higher tier within 6 months

undefined

3. Multiple Personas

3. 多用户画像体系

javascript

// Create persona set for comprehensive coverage

class PersonaFramework {
  createPersonaSet(research_data) {
    return {
      primary_personas: [
        {
          name: 'Sarah (VP Product)',
          percentage: '35%',
          influence: 'High',
          role: 'Decision maker'
        },
        {
          name: 'Mike (Team Lead)',
          percentage: '40%',
          influence: 'High',
          role: 'Daily user, key influencer'
        },
        {
          name: 'Lisa (Admin)',
          percentage: '25%',
          influence: 'Medium',
          role: 'Setup and management'
        }
      ],
      secondary_personas: [
        {
          name: 'John (Executive)',
          percentage: '10%',
          influence: 'Medium',
          role: 'Budget approval'
        }
      ],
      anti_personas: [
        {
          name: 'Enterprise IT Director',
          reason: 'Not target market, different needs',
          avoid: 'Marketing to large enterprise buyers'
        }
      ]
    };
  }

  validatePersonas(personas) {
    return {
      coverage: personas.reduce((sum, p) => sum + p.percentage, 0),
      primary_count: personas.filter(p => p.influence === 'High').length,
      recommendations: [
        'Personas cover 100% of target market',
        'Focus on 2-3 primary personas',
        'Plan for secondary use cases',
        'Define clear anti-personas'
      ]
    };
  }

  createPersonaMap(personas) {
    return {
      influence_x_axis: 'Low → High',
      adoption_y_axis: 'Slow → Fast',
      sarah_vp: { influence: 'High', adoption: 'Fast' },
      mike_lead: { influence: 'Very High', adoption: 'Very Fast' },
      lisa_admin: { influence: 'Medium', adoption: 'Medium' },
      john_executive: { influence: 'Very High', adoption: 'Slow' },
      strategy: 'Focus on Mike (influencer), design for Sarah (buyer), support Lisa (user)'
    };
  }
}

javascript

// Create persona set for comprehensive coverage

class PersonaFramework {
  createPersonaSet(research_data) {
    return {
      primary_personas: [
        {
          name: 'Sarah (VP Product)',
          percentage: '35%',
          influence: 'High',
          role: 'Decision maker'
        },
        {
          name: 'Mike (Team Lead)',
          percentage: '40%',
          influence: 'High',
          role: 'Daily user, key influencer'
        },
        {
          name: 'Lisa (Admin)',
          percentage: '25%',
          influence: 'Medium',
          role: 'Setup and management'
        }
      ],
      secondary_personas: [
        {
          name: 'John (Executive)',
          percentage: '10%',
          influence: 'Medium',
          role: 'Budget approval'
        }
      ],
      anti_personas: [
        {
          name: 'Enterprise IT Director',
          reason: 'Not target market, different needs',
          avoid: 'Marketing to large enterprise buyers'
        }
      ]
    };
  }

  validatePersonas(personas) {
    return {
      coverage: personas.reduce((sum, p) => sum + p.percentage, 0),
      primary_count: personas.filter(p => p.influence === 'High').length,
      recommendations: [
        'Personas cover 100% of target market',
        'Focus on 2-3 primary personas',
        'Plan for secondary use cases',
        'Define clear anti-personas'
      ]
    };
  }

  createPersonaMap(personas) {
    return {
      influence_x_axis: 'Low → High',
      adoption_y_axis: 'Slow → Fast',
      sarah_vp: { influence: 'High', adoption: 'Fast' },
      mike_lead: { influence: 'Very High', adoption: 'Very Fast' },
      lisa_admin: { influence: 'Medium', adoption: 'Medium' },
      john_executive: { influence: 'Very High', adoption: 'Slow' },
      strategy: 'Focus on Mike (influencer), design for Sarah (buyer), support Lisa (user)'
    };
  }
}

4. Using Personas

4. 用户画像的应用

yaml

Applying Personas to Product Decisions:

---

yaml

Applying Personas to Product Decisions:

---

Feature Prioritization

功能优先级排序

Feature: Offline Mobile Access Sarah's Need: Medium (works with wifi) Mike's Need: Very High (field work, poor connectivity) Lisa's Need: Low (office based) Decision: PRIORITIZE (high-value user needs it)

Feature: Advanced Reporting Sarah's Need: Very High (executive visibility) Mike's Need: Low (not his responsibility) Lisa's Need: Medium (setup reporting) Decision: PRIORITIZE (key buyer needs it)

Feature: Bulk Import Sarah's Need: Medium (initial setup) Mike's Need: Low (day-to-day use) Lisa's Need: Very High (admin task) Decision: PRIORITIZE (admin enablement)

Feature: Offline Mobile Access Sarah's Need: Medium (works with wifi) Mike's Need: Very High (field work, poor connectivity) Lisa's Need: Low (office based) Decision: PRIORITIZE (high-value user needs it)

Feature: Advanced Reporting Sarah's Need: Very High (executive visibility) Mike's Need: Low (not his responsibility) Lisa's Need: Medium (setup reporting) Decision: PRIORITIZE (key buyer needs it)

Feature: Bulk Import Sarah's Need: Medium (initial setup) Mike's Need: Low (day-to-day use) Lisa's Need: Very High (admin task) Decision: PRIORITIZE (admin enablement)

Journey Mapping

旅程地图绘制

Sarah's Evaluation Journey:

Becomes aware (peer recommendation) → Email request
Reads reviews (G2, Capterra) → Schedule demo
Watches demo → Reviews case studies
Wants reference → Talks to 2 customers
Creates RFP → Evaluates pricing
Gets team input → Makes decision → Timeline: 6-8 weeks

Mike's Adoption Journey:

Learns about tool → Demo from Sarah
Gets access → Starts with 1 project
Learns through hands-on → Gradually adopts
Becomes power user → Recommends to others → Timeline: 4 weeks

Sarah's Evaluation Journey:

Becomes aware (peer recommendation) → Email request
Reads reviews (G2, Capterra) → Schedule demo
Watches demo → Reviews case studies
Wants reference → Talks to 2 customers
Creates RFP → Evaluates pricing
Gets team input → Makes decision → Timeline: 6-8 weeks

Mike's Adoption Journey:

Learns about tool → Demo from Sarah
Gets access → Starts with 1 project
Learns through hands-on → Gradually adopts
Becomes power user → Recommends to others → Timeline: 4 weeks

Marketing Message by Persona

分画像营销信息

For Sarah (VP Product): Headline: "Increase project delivery speed by 30%" Focus: ROI, team productivity, visibility Channel: LinkedIn, industry publications CTA: "See ROI calculator"

For Mike (Team Lead): Headline: "Work faster, stress less" Focus: Ease of use, mobile, collaboration Channel: Twitter, Slack communities CTA: "Try free 30-day trial"

For Lisa (Admin): Headline: "Setup in 1 day, not 1 month" Focus: Easy administration, integrations Channel: Admin webinars CTA: "Download admin guide"

undefined

For Sarah (VP Product): Headline: "Increase project delivery speed by 30%" Focus: ROI, team productivity, visibility Channel: LinkedIn, industry publications CTA: "See ROI calculator"

For Mike (Team Lead): Headline: "Work faster, stress less" Focus: Ease of use, mobile, collaboration Channel: Twitter, Slack communities CTA: "Try free 30-day trial"

For Lisa (Admin): Headline: "Setup in 1 day, not 1 month" Focus: Easy administration, integrations Channel: Admin webinars CTA: "Download admin guide"

undefined

Best Practices

最佳实践

✅ DO

✅ 要做

Base personas on real research, not assumptions
Include 2-3 primary personas
Make personas specific and detailed
Include direct user quotes
Update personas based on new data
Share personas across organization
Use personas for all product decisions
Include both goals and pain points
Create personas for different user types
Document research sources

基于真实研究创建画像，而非假设
包含2-3个核心用户画像
让画像具体且详细
加入用户直接引用的话语
根据新数据更新画像
在整个组织内共享画像
在所有产品决策中使用画像
同时包含目标和痛点
为不同用户类型创建画像
记录研究来源

❌ DON'T

❌ 不要做

Create personas without research
Create too many personas (>4 primary)
Make personas too generic
Ignore data in favor of assumptions
Create personas, then forget them
Use personas only for design
Make personas unrealistically perfect
Ignore secondary users
Keep personas locked away
Never update personas

无研究依据创建画像
创建过多核心画像（超过4个）
让画像过于通用
忽视数据，仅凭假设
创建画像后弃之不用
仅在设计环节使用画像
让画像完美得不真实
忽视次要用户
将画像保密不共享
从不更新画像

User Persona Tips

用户画像技巧

Use real quotes from interviews
Include both job and personal details
Show clear motivations and pain points
Make personas memorable and shareable
Print and post personas in team space
Reference personas in design discussions

使用访谈中的真实用户引用
同时包含工作和个人细节
清晰展示动机和痛点
让画像易于记忆和分享
打印画像并张贴在团队办公区
在设计讨论中参考画像

user-persona-creation

Original

Translation

User Persona Creation

用户画像创建

Overview

概述

When to Use

适用场景

Instructions

操作步骤

1. Research & Data Collection

1. 研究与数据收集

Gather data for persona development

Gather data for persona development

2. Persona Template

2. 用户画像模板

Demographics

Demographics

Professional Context

职业背景

Goals & Motivations

目标与动机

Pain Points

痛点

Behaviors & Preferences

行为与偏好

Technology Comfort

技术适配度

Customer Journey

用户旅程

Communication Preferences

沟通偏好

Key Quotes

核心引用

Persona Importance

画像重要性

Marketing & Sales Strategy

营销与销售策略

3. Multiple Personas

3. 多用户画像体系

4. Using Personas

4. 用户画像的应用

Feature Prioritization

功能优先级排序

Journey Mapping

旅程地图绘制

Marketing Message by Persona

分画像营销信息

Best Practices

最佳实践

✅ DO

✅ 要做

❌ DON'T

❌ 不要做

User Persona Tips

用户画像技巧