Customer personas turn researched needs and behavior into website content decisions
A customer persona describes people with similar needs and behavior. Recording the situation behind an inquiry and the information used to decide helps you choose what belongs in service descriptions, pricing, examples, and contact guidance. GOV.UK lists personas as a way to communicate patterns in user needs and behavior. (GOV.UK user-needs research)
Imagined ages and occupations alone provide little basis for writing a page. For customers commissioning a website, useful details include who will update it, the intended launch date, costs being compared, and available copy or photographs.
Record evidence and assumptions from customer behavior
Use inquiry records and interviews to understand the situation, alternatives, and decision criteria. Mark an internally imagined profile as an assumption and keep it distinct from observed behavior.
Ask about an actual decision process
Ask recent customers or people currently evaluating a service what prompted their search, which alternatives they considered, what they read, and what influenced their decision. A discussion of preferred colors alone leaves those questions unresolved.
Inquiry records, search terms, and page-use data can suggest questions for interviews. GOV.UK recommends combining existing evidence, interviews, and observation, and treating opinions unsupported by user evidence as assumptions to investigate. (GOV.UK user-needs research)
Separate observations from interpretations in the record
Keep the source, research date, observed behavior, and your interpretation in separate fields. GOV.UK's research-analysis guidance distinguishes observations from findings and their implications. (GOV.UK research analysis)
| Field | What to record |
|---|
| Situation | What prompted an inquiry or evaluation |
| Problem | Difficulties with the current approach |
| Behavior | Search channels, alternatives, and information consulted |
| Decision material | Costs, timing, and support actually compared |
| Evidence and open questions | Sources, established findings, and questions to investigate |
These are example fields for customer understanding. Keep information that helps make a content decision, with evidence taking precedence over invented names or portraits.
Turn decision material into page content
Translate the record into factual service information and guidance. In a hypothetical small-shop website project, the update owner and ongoing cost might be important decision criteria.
Explain service scope and costs
For a customer responsible for updating prices, explain who edits which content. To support cost comparisons, publish setup costs, recurring charges, and prices for additional work. All statements must reflect the service actually offered.
| Example customer finding | Example information to publish |
|---|
| A shop employee updates prices | Editable content and update steps |
| The customer compares monthly costs | Recurring charges and billable additional work |
| Few photographs are available | Required media and any photography support |
| Calls are impractical during opening hours | Contact options and response hours |
Verify each hypothetical finding through research before using it in copy. See A one-page website structure for the overall content sequence.
Put requested information near the relevant fields and explain what follows submission. Offer useful actions for different stages of evaluation, such as reading details, comparing costs, or making an inquiry. A single fixed profile can omit people who need different forms of support.
When customers have substantially different goals or requests, provide distinct service explanations or guidance. Choose the number of personas according to differences that affect content and the process.
Validate the published explanation through tasks and questions
Observe people finding prices, determining service scope, or choosing a contact method. Record where they stop and what they ask, then revise the relevant wording or placement. GOV.UK's moderated usability-testing method uses concrete tasks to uncover language and layout problems. (GOV.UK usability testing)
Update the evidence and profiles when you introduce a service or receive different kinds of inquiries. When measuring response changes, also record traffic-source and price changes so interpretation accounts for other influences.
Use research findings to revise the page and use subsequent questions and observed actions to improve the explanation.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To build a website that presents the decision material found through customer research, give SpreadSite a try!
Build a website with SpreadSite →
