A persona can have a name, photograph and convincing biography while contributing almost nothing to a product decision. Knowing that a fictional buyer enjoys travel does not necessarily explain how they compare prices or handle a delayed order.

Original visual from the article archive about personas, scenarios and goals.View full image
Original visual from the article archive about personas, scenarios and goals.

The test I would apply is straightforward: if this detail changed, would the interface need to change? If the answer is consistently no, the team may be documenting a character rather than a useful model of behavior.

Look for differences that affect the work

Consider a hypothetical purchasing tool. One person places the same replenishment order every week. Another compares unfamiliar items for occasional projects. Their job titles might be identical, but their behavior suggests different needs: quick reordering for the first, comparison and detailed specifications for the second.

Even these patterns should remain open to challenge. The regular buyer can encounter an unfamiliar product, and the occasional buyer can repeat an order. A persona should help a team anticipate situations without assigning people to permanent boxes.

Show where the description came from

Attach important claims to interview notes, observations or other evidence. “Usually needs approval above a spending limit” is useful if supported and relevant. “Values convenience” is too broad to discriminate between design alternatives.

An assumption-based sketch can help plan research, but label it accordingly. Stakeholder agreement can tell you that a description feels plausible inside the organization. It does not validate the behavior of customers outside it.

Use it at the point of a decision

Suppose the team proposes opening every session on a large product catalog. For repeat purchasing, recent orders may be a better entry point. For unfamiliar purchases, the catalog may be useful. The persona helps expose the tension; it does not automatically settle which audience should receive priority.

That prioritization still needs business context, task frequency and evidence of unmet needs. A set of attractive profiles cannot supply those decisions on its own.

If a persona never appears in discussions about navigation, content or functionality, ask whether a simpler scenario description would be more useful. Keep the model only while it helps explain behavior and make choices. Updating its photograph is not the same as updating its assumptions.