> ## Documentation Index > Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt > Use this file to discover all available pages before exploring further. # Customer personas > Create practical customer personas, keep only the details that matter, and link them to the journeys where they change real decisions. The same journey can look very different to a buyer, an admin, and an end user. Personas help your team stay clear about whose problem a journey is describing and whose needs should shape the decision. ## What a persona should change A persona is useful only if it changes how the team reads the journey. Use personas to answer questions like: * Who is this journey really for? * Who feels this friction first? * Who approves the solution? * Who succeeds or fails if nothing changes? If the persona does not affect interpretation, prioritization, or the solution, it is probably too vague or not needed. ## When to create one Create a persona when a different role changes the journey in a meaningful way. Common cases: * one person buys and another sets the product up * the admin has setup friction but end users do not * one customer type cares about speed while another cares about control Do not create a new persona for every minor variation. Keep the set small enough that the team can remember and use it. ## How personas work in Custory Personas live at the workspace level so you can reuse them across journeys. That matters because the same customer role often appears in onboarding, activation, retention, and support journeys. One shared persona is usually better than maintaining slightly different copies in each map. Link a persona to a journey when it changes how the team should interpret that flow. ## What to include Custory supports detailed persona fields such as: * bio * role * role in journey * primary job-to-be-done * buying influence * budget or income * location * goals * frustrations * motivations * tech savviness * devices * tools and apps Do not fill fields just because they exist. Keep the details that help your team make better decisions. Good fields usually explain: * what this person is trying to get done * what slows them down * what they care about when evaluating success ## Example personas ### First-time workspace admin This person wants fast setup, low risk, and enough clarity to become the internal champion. Useful fields: * Role: operations manager * Role in journey: team admin * Goal: get the team to first value without engineering help * Frustration: too many setup choices too early ### Founder evaluating ROI This person wants confidence that the product is worth team time and budget. Useful fields: * Role: founder * Role in journey: buyer or approver * Goal: see practical value fast * Frustration: tools that create more process than clarity ## How to use personas well Start by creating only the personas that clearly change how the team reads the journey. Then: 1. Link the persona to the journeys where it matters. 2. Use it when writing touchpoints, insights, and opportunities. 3. Revise it when the team learns something more specific about that role. If a persona stops affecting decisions, simplify it or remove it. ## AI support Custory AI can help you: * draft a new persona * tighten generic wording * expand goals, frustrations, and motivations * suggest which persona fits the current journey Use AI to speed up the draft, then trim the persona until it sounds like a real customer your team actually recognizes. ## Persona mistakes to avoid If the persona looks complete but does not alter product or journey decisions, it is not doing enough work. Split personas only when the role, goals, or decision logic really differ. Extra detail becomes stale quickly. Keep the fields the team will actually use in reviews and prioritization. ## Next step Read [the touchpoints section in Items](/items#touchpoints) if you want to see how personas affect specific customer moments. Read [Journeys](/journeys) for where personas become useful in the full map.