What is a persona in UX design?
A persona is a fictional but research-grounded representation of a significant user type. Created from patterns identified across multiple user research sessions, a persona synthesizes the behaviors, goals, motivations, pain points, and context of a recurring user type into a named, described character that the design team can refer to when making decisions. Personas are not demographic profiles and are not based on assumptions about who users are. They are abstractions of real behavioral patterns observed in real users during research.
How are personas created effectively?
Effective personas are built from research, not speculation. User interviews, contextual observations, and usability studies produce data about how users actually behave and what they actually need. Affinity mapping and other synthesis methods identify patterns across multiple users. Where multiple users share significant behavioral patterns, goals, and context, those patterns can be synthesized into a persona. The key is that the persona represents observed patterns, not assumptions. A persona created without research is not a design tool, it is a projection of the team's existing beliefs about users.
How do personas differ from jobs to be done?
Personas describe who the user is: their context, goals, behaviors, and pain points. Jobs to be done describes what the user is trying to accomplish in a specific situation, regardless of who they are. Both frameworks are useful but serve different purposes. Personas help teams build empathy for users and evaluate design decisions from a user's perspective. JTBD helps teams focus on the specific progress users are trying to make and the circumstances that drive that need. A single persona may have many different jobs depending on context, and the same job may be shared across many different personas.