Use roles rather than fictional biographies
A persona should help someone make a better marketing or sales choice. A name, stock photograph and invented hobby rarely explain why a technical evaluator needs implementation evidence or why a finance leader challenges a business case. Include personal details only when reliable evidence shows that they affect the decision.
Begin with a real buying situation and map the roles that influence it. The person who experiences the problem may not control budget, security approval or implementation. One individual can also occupy several roles in a smaller organization. Do not assume the organization chart tells you who actually shapes the decision.
Write a decision-oriented persona
| Field | Question to answer |
|---|---|
| Responsibility | What outcome or risk does this person own? |
| Trigger | What event makes the problem relevant now? |
| Evaluation | What must they establish before supporting a change? |
| Evidence | Which proof can they inspect or take to colleagues? |
| Objection | What practical concern could stop the decision? |
| Next step | What action is reasonable at this point? |
Distinguish evidence from assumptions in each field. A useful draft may contain several unknowns. Marking them is better than filling them with confident language copied from an internal workshop.
Research a recent decision
Interview people about a purchase, rejection or delayed project. Ask how the issue arose, who joined the discussion, which evidence mattered and what created friction. Compare their account with available opportunity records or observed interactions. Journey research emphasizes grounding a map in actual customer evidence.
For a hypothetical software purchase, an operations user might need confidence that a workflow improves, an IT evaluator might need implementation details, and a budget owner might need a credible value case. These are prompts to investigate, not universal facts about those job titles.
Turn the persona into content choices
Connect each evidence need to a useful asset or conversation. A checklist may help a first evaluation; a detailed migration plan may be necessary later. If two personas always receive identical information and next steps, consider whether they need separate profiles. If one profile combines incompatible decision needs, split by buying role or situation.
Maintain a living record
Record the source, date and context behind each important statement. Revisit personas when the product, segment or buying process changes. The test is whether the profile improves relevance and decision support, not whether it looks complete in a presentation.