Audience research
Six checks before publishing social media training buyer personas
Six checks before publishing social media training buyer personas in England: evidence label, small groups, buyer disagreement, blanks and retirement.
A buyer persona is ready to publish only when readers can see what it rests on and nobody in it can be identified. Social media training buyer personas summarise buying roles; they are not characters. Six checks separate a card that can go out from one that needs more work.
What to take away
- Date each card, name its author and attach the cases behind it.
- Label a pattern "observed in this sample", never "typical in England".
- Check whether sector, region, seniority and an incident together point to one person.
- Show buyer disagreement as separate requirements, not one smoothed story.
- If no consented fieldwork exists, publish the research questions and leave the persona blank.
- Retire a card when the role, the course decision or the evidence changes.
Check one: state what the card rests on
A card without its evidence reads as fact. Date it, name its author and attach a source table showing cases, coding rules and excluded evidence. The reader should be able to trace each statement on the card back to a case, or see that it has none.
The ONS explains that the difference between a sample statistic and the population value is caused by sampling error and non-sampling errors. A small interview set carries both. Say "observed in this sample" and name how many were invited, eligible and included.
Check two: look for people hiding in the detail
Combining sector, region, seniority and a distinctive incident may identify a participant even after removing a name. Store the identity key separately, minimise quotations and aggregate any detail the course decision does not need. Ask of every field whether the decision would change without it.
Research agreement, UK GDPR lawful basis and later sales contact remain separate decisions, as data protection for training explains. The ICO states that you must have a lawful basis to use personal information. A named UK privacy adviser and research-ethics reviewer should check the actual use before the card goes live.
Check three: keep the buyers disagreeing
Course purchases rarely have one voice. A single persona that satisfies everyone has been smoothed. Report each requirement under the role that holds it, and keep the conflict visible. The table shows the pattern for three roles at a purchase.
| Role | Requirement it may raise | How to show it on the card |
|---|---|---|
| Line manager | Consistent work samples | Own row, with the cases that support it |
| Procurement | Comparable scope between offers | Own row, linked to supplier checks |
| Learner | Accessible delivery | Own row, with access requirements recorded |
Do not merge the rows to make a shorter card. A reader choosing a course needs to see where roles pull apart before a quote is requested. If the fieldwork shows no disagreement, say so and name the cases.
Check four: cut fields the decision cannot use
The GOV.UK guide to planning a research round recommends linking research objectives to the decision that follows. Apply that to every field. If preferred social networks or hobbies cannot change the course decision, do not collect them, and do not add a made-up name, age or motive.
Learner cards deserve the same test. A card might describe "staff who prepare social posts but cannot approve claims or publishing" only if fieldwork supports that boundary. It must cite the cases and keep contrary examples. The audience research method sits upstream of this step, and is where those cases are gathered.
Check five: leave the card blank when evidence is missing
An empty card is honest. If no consented fieldwork exists, publish the research questions and leave the persona blank. Do not fill gaps with salary, budget or audience size unless the figure comes from consented evidence and is necessary for the decision.
A blank card also shows what to collect next. List the decision it should inform, the role it covers and the cases still missing. For a missing budget, ask the budget approver instead of estimating. That turns a gap into a plan, and it stops a placeholder from being quoted later as if it were a finding.
Check six: set the date the card stops being valid
Retire a card when the role, the course decision or the evidence changes. Record the review trigger on the card itself, next to the author and date, so that nobody has to guess whether it is current.
Take it down, or mark it withdrawn, rather than letting it drift. A withdrawn card can point to the newer evidence, such as the demand signals that replaced it, and to the observable tasks in the target audience definition.
Before you act
- Date the card and name its author.
- Attach the source table, coding rules and excluded evidence.
- Test every field for identifying small groups.
- Give each buyer role its own requirement row.
- Remove any field the decision cannot use.
- Record the review trigger that retires the card.
Common questions
Should a published persona carry a name and budget?
No. Add a name, portrait, quotation, salary or budget only when it comes from consented evidence and is necessary. Without that, publish the role, the decision it controls, the task evidence behind it, important variation and what remains unknown.
How do I stop a participant being identified?
Store the identity key separately, minimise quotations and aggregate details the decision does not need. Check whether sector, region, seniority and a distinctive incident together could point to one person, and have a privacy adviser review the actual use.
What if no fieldwork has been done yet?
Publish the research questions and leave the persona blank. Label any later pattern "observed in this sample" rather than "typical in England", and date the card so readers can see how recent the evidence is.
