Persona Documents vs. a Randomized Concept Test: Which One Answers Your Question
On this page
A persona document tells a marketing or insights team who the audience is. It does not tell the team what happens when message A runs against message B, or which price a buyer actually picks over another. Those are two different jobs, and choosing the wrong tool for the job is how a campaign ships on an assumption that was never tested against an alternative.
Two starting points for understanding an audience
A persona document organizes what a team knows about a customer type, drawing on interviews, surveys, or other data. Persona Institute's current description says its workflow combines a client's existing analytics, CRM, and survey data with other research datasets. Confirm the input data and how each profile trait is supported before relying on the persona brief.
A randomized concept test starts from specified alternatives and a measured response. The team defines messages, prices, features, or positioning options, then estimates the contrast under its design. The result may show a meaningful difference or remain inconclusive; it does not automatically reveal a psychological mechanism.
What can't a persona document tell you?
A persona document is a description, not an experiment. It can summarize what interviewees said they wanted last quarter. It cannot show a team what a specific new headline does against a specific alternative headline, because no comparison ran. A team that treats a persona's stated preferences as a stand-in for that missing comparison is making a causal claim, "this message will work because this persona would like it," without ever having tested causality.
Comparing the two approaches
| Research-grounded persona document | Randomized concept test | |
|---|---|---|
| Starting material | Existing research and customer data | Specified alternatives and a measured response |
| Primary output | Structured buyer profile and supporting evidence | Estimated effects on the tested response, with uncertainty where supported |
| Answers "who is this person" | Yes | Indirectly, as context |
| Compares specified alternatives experimentally | No, a document alone does not | Yes; may find no clear difference |
| Requires past interviews | Depends on the underlying research workflow | No, though interviews can inform the setup |
| Human evidence | Check the underlying research and assumptions | Use human respondents or a matched human validation study |
How does Subconscious run a controlled comparison against a simulated market?
Subconscious uses randomized choice designs with generated responses to estimate how specified attributes change choices within the simulated task. Report the endpoint, population, effect estimates, and uncertainty, including a no-clear-winner result. A choice-task estimate is different from conversion in a live A/B test. Teams can inspect the method before selecting the evidence needed for a campaign decision.
A recruited human study can test the same alternatives and causal question. Align the instrument, population, outcome, and analysis, and document differences. A live test may be needed when the intended endpoint is actual conversion rather than stated choice.
When is an interview-derived persona document still the right call?
Choose a persona document when the team needs to organize and communicate existing buyer research. Keep the source material and unresolved assumptions attached to the profile. A controlled comparison adds evidence about a defined contrast; it does not replace having talked to customers.
Making the choice
If the question concerns buyer context, inspect the research behind the persona. If it concerns a proposed message, price, or concept, compare alternatives under an appropriate design. Let uncertainty and the minimum useful effect inform the decision; a winner is not guaranteed. Review the research process, past comparisons, or scope a study.
