A persona is a fictional character that represents a target user group. Designers build personas from research: interviews, surveys, analytics, and observation. Instead of designing for an abstract audience, the team designs for a specific person with a name, a job, a routine, and frustrations. The persona is not a real customer. It is a composite, a stand-in that keeps the team grounded in real needs.

A useful persona includes goals, behaviors, pain points, and context of use. A project might have three or four personas covering different user types. One might be a busy parent using a mobile app in short bursts. Another might be a power user who wants keyboard shortcuts. When a debate breaks out about a feature, the team can ask which persona it serves. That question often settles the argument faster than opinion.

What goes into a persona

• Name, age, occupation, and daily routine.
• Goals and motivations.
• Frustrations and barriers.
• Technical comfort and device habits.

Personas go stale. Audiences change, and research ages. Teams that treat them as permanent fixtures risk designing for a user who no longer exists.