A useful persona is not a fictional biography with a stock photo. Use this worksheet to organize evidence from conversations, inquiries, support questions, research, and site behavior. Complete one worksheet per meaningful decision context. The same person may behave differently when exploring options, comparing providers, and asking for support.
1. Define the decision.
What is the person trying to decide? State the choice in plain language. “Which provider can handle our multi-location website?” is more actionable than “buy digital services.”
What triggered the search? Name the change, problem, or opportunity that made the issue matter now. If you do not know, mark it as a question to research.
What alternatives are being considered? Include doing nothing, handling it in-house, changing process, and other categories of provider when those are real options.
2. Describe the person’s role and constraints.
Role in the decision: Are they the user, researcher, budget holder, approver, or implementer? More than one person may be involved.
What they already know: Identify familiar terms and likely gaps. A page for an expert can use different detail from one for a first-time buyer.
Constraints: Note time, budget process, access, policy, technical environment, or approval needs only when supported by research. Avoid attaching constraints to a demographic stereotype.
3. Capture their real questions.
List the questions you hear before someone contacts the business. Put the most consequential first. Typical categories include fit, scope, process, price, risk, timing, and what happens after purchase or launch.
For each question, record its source: customer interview, sales call, support ticket, search query, form response, or an assumption that still needs testing. That distinction keeps a plausible guess from becoming a claimed customer fact.
4. Identify trust and friction.
What would help them trust the answer? This may be a clear process, current terms, a relevant demonstration, an approved project example, or a person they can speak with. Use evidence you actually have permission to show.
Where might they hesitate? Perhaps the offer sounds broader than their need, the price model is unclear, the form asks too much, or a technical term hides a dependency. Write the barrier in the customer’s words when possible.
What should not be promised? Record any limitation, exception, or qualification that the page must make clear.
5. Map the content path.
First useful page: Which page should answer their opening question?
Next page: What do they need after that: a service explanation, comparison, process, example, FAQ, or contact route?
Appropriate action: What can they reasonably do at this stage? Reading a guide may be right for early exploration. An inquiry may fit once scope and trust are clearer.
Use the path to improve information architecture and content strategy. It should not become an excuse to create a separate SEO page for every slight persona variation.
6. Check the worksheet against people.
Show the draft to someone who handles real customer conversations. Which questions are missing? Which assumptions sound unlike the people they meet? Then test page copy or a prototype with people who match the decision context. Update the worksheet when behavior contradicts it.
A persona is useful when it helps the team make a better content or design choice. It is not useful because it has a memorable invented name.
Put the insight to work.
Choose one page and ask whether it answers this persona’s first important question. If it does not, revise the page or the route leading to it.