Persona Approach

User personas are semi-fictional characters that represent different areas of a target audience, user base or stakeholder group. The three components of a persona are Demographics, Psycho-graphics, and Behavioral Patterns

Slideshow!

View the information on this page in a slideshow format! Useful for classrooms and all other group settings.

Learning Objectives

Identify Target Users: define methods for identifying stakeholders in order to develop representative personas.
Segment User Data: develop techniques for segmenting user data into categories that inform personal creation and distinguish user archetypes.
Create Realistic Personas: develop skills for crafting detailed personas— including demographics, motivations, emotions, experiences, etc.
Align Personas with Project Goals: ensure personas align with objectives.
Measure Impact of Personas: assess the effectiveness of personas in enhancing project outcomes and achieving user satisfaction.

Characteristics

The Project Management Book of Knowledge describes the term “personas” as, “An archetype user representing a set of similar end users described with their goals, motivations, and representative personal characteristics”.
- User personas are semi-fictional characters that represent different areas of a target audience, user base or stakeholder group
The Three Core Components of Personas:
- Demographics (age, gender, occupation, etc.)
- Psychographics (motivations, goals, pain points)
- Behavioral Patterns (how they use the product, habits, preferences)

Benefits

User-Centered Design
- project goals and outcomes are aligned with the needs and preferences of the end users
Resource Allocation
- resources can be allocated more efficiently to areas that have the most impact on user satisfaction.
Enhanced Communication
- common language and understanding among team members

Drawbacks

Complexity
- creating and maintaining personas can be time-consuming and complex, especially for large and diverse user bases
Stereotyping
- oversimplification of user groups, which can result in overlooking unique individual needs
Costly
- conducting user research to develop accurate personas can be expensive

Example

Spotify’s Listening Personas
- Research and Data Gathering
  - Spotify collected data on user behavior (listening habits, playlist creation, etc.) through analytics, surveys, and user feedback
- Define Personas:
  - Created personas like “Casual Listener,” “Music Enthusiast,” and “Party Host” based on distinct user patterns and needs
- Develop User Scenarios:
  - Developed scenarios for each persona, detailing how they interact with the app, what features they use, and their goals (e.g., finding new music or creating social playlists)
- Design and Prioritize Features:
  - Tailored features (like personalized recommendations, playlist creation tools, and social sharing) to meet the specific needs of each persona
- Test with Real Users:
  - Conducted user testing and feedback sessions to validate the personas and ensure that the design solutions align with their preferences and behaviors
- Iterate and Improve:
  - Continuously refined the design based on ongoing data and feedback to ensure the user experience remained relevant and effective for all personas

How Can We utilize this approach?

The persona approach can be a highly effective tool for a project planning team to ensure that a project is driven by user-centric considerations. Though we have presented our prototype to a group of students, it may be beneficial to utilize the personas approach as a way to gauge how potential real-life project managers may interact with and interpret our prototype. Overall, the persona approach aids in feature prioritization, facilitates communication and collaboration among team members, and supports the identification and mitigation of potential project risks!