
Audience research
Part of Audience research for social listening starts with the decision, not the data
Social listening personas without invented names, quotes or personalities
Create evidence-based social listening personas for England without fictional names, quotations or traits, using traceable decisions and research limits.
- Define the decision, population, England boundary and evidence period.
- Use a plain functional label only when evidence shows recurring work.
- Tie each statement to its source and keep differences visible.
- Remove identifying detail and record how the material is handled.
- Show dates, sample, confidence and gaps alongside the description.
- Set clear triggers for review, revision or retirement.
Fix the question and boundary
Start with the decision the listening work must inform, then identify who commissions, operates or uses the findings. Set the evidence dates, population and exclusion rules before reading posts or grouping observations. This keeps a functional description within the limits of the question it is meant to serve.
England can refer to a role based there, responsibility for English operations, or a UK commissioner buying centrally; these are different boundaries. Choose and state the relevant one. The decision-led research approach can help fix the question, while the England audience rule makes the geographic scope explicit.
Name a pattern, not a character
Use a functional label, such as monthly insight commissioner, only when evidence points to recurring work or decisions. Keep it plain and role-based. It should help colleagues recognise the group without suggesting the research discovered a named individual, personal history or personality.
Persona record fields
- Population and England definition
- Inclusion and exclusion criteria
- Studies, dates and achieved samples
- Recurring decision and required evidence
- Current process, constraints and hand-offs
- Supporting and contradictory observations
- Confidence and next research question
Alongside the label, record the included population, boundary, exclusions, study dates and achieved sample, then specify recurring decisions, evidence needed, current process and constraints. Keep the source trail and counterexamples visible. Do not turn these separate fields into a fictional biography or one polished account.
Keep every statement traceable
Build statements from coded source units, with a route back to source material within the study's access and retention controls. Interviews, consented recordings, surveys, procurement records or public material may contribute only when they fit the defined research scope and handling arrangements.
Separate direct observations from interpretations and possible actions. Checking source posts before briefing a director is an observed action; reading that as a need for traceability is an interpretation. Mark the reasoning between them in the record. Present neither as a quotation or as something known to be true of everyone in the group.
If the material indicates different alert rhythms, record the variation and consider whether it supports separate patterns or leaves the grouping uncertain. Do not smooth disagreement into a typical account. Preserve the distinction between observations and tentative readings, so that the evidence does not appear more consistent than it is.
Reduce the chance of identification
A role description can point to a person even without a name. Check whether an unusual combination of duties, process and context could identify a participant. Retain details that serve the research purpose, and remove or generalise those that add identification risk without helping explain the decision.
Apply data minimisation by keeping only detail needed for the research purpose. Record collection context, purpose, source material, retention and access controls, and where a correction, deletion or objection request goes. Consult lawful basis guidance as part of the handling review; general guidance cannot settle a study-specific interpretation.
Keep wider handling questions, including access requests, the right to restrict processing, data portability, automated decision making, controller responsibility, joint controllers, processor terms and breach notification, with the relevant owner rather than adding them as persona traits. The data protection review can help frame that handling check.
Put uncertainty beside the description
Place evidence dates, achieved sample, confidence and known gaps beside the functional description. Treat the summary as an index into the underlying material, not proof that every buyer behaves alike. Readers should be able to see what the evidence supports and where it stops.
State the open question and any unresolved disagreement beside the confidence assessment. If supporting material is missing, mark the description as an untested question rather than a settled account. Keep the evidence period visible whenever the summary informs a decision, so readers can judge whether the material remains relevant.
Before using the description in a decision, run the quality checks against its source trail, boundary and unresolved differences. A clean presentation cannot repair weak or incomplete material. Link the underlying study method and make the next research question clear.
Set a point for review
State what evidence or change would prompt review, revision or retirement. Revisit the description when fresh research challenges its defining pattern, the role or buying process changes, or the England boundary no longer fits. Make the trigger specific enough for a colleague to apply to later evidence.
Update the record when evidence changes instead of smoothing disagreement into the existing account. Keep the description provisional while its pattern remains uncertain, and note what further research could resolve that uncertainty. Record the reason for each change beside the evidence period, so later readers can follow the decision.



