User Persona Template for User Research

Three to five is the practical range for most products. One primary persona represents your core user. Two to three secondary personas cover important adjacent segments. Beyond five, the personas become hard to remember and stop influencing decisions.

A segment is a data-driven grouping based on attributes or behavior (e.g., "users who signed up in the last 30 days and completed onboarding"). A persona is a narrative archetype built from research that represents a segment. Segments tell you who exists in your data. Personas tell you why they behave the way they do.

Test them against new research. After creating a persona, interview 3-5 more users from that segment. If their goals, pain points, and behaviors match the persona, you are on track. If they diverge significantly, revise. You can also share personas with customer-facing teams (sales, support) and ask: "Does this match the people you talk to every day?"

Include demographics only when they affect product behavior. A user's age matters if it correlates with technology comfort level. Location matters if it affects regulatory requirements or language preferences. If the demographic detail does not change how you would design the product, leave it out.

Personas describe who your user is. Jobs-to-be-Done describe what they are trying to accomplish. The two frameworks complement each other. A persona provides context (role, frustrations, tools) that makes JTBD statements more actionable. Use the persona to understand the person, and JTBD to understand the problem they are hiring your product to solve.