The persona is the simulated person the operator interacts with: the injured worker on the phone, the loan applicant across the desk, the customer on their fourth call about the same problem. The operator asks questions, builds trust, and makes decisions, and the persona responds in character. Personas matter most in conversation scenarios and journey simulations, where the persona holds the information the operator needs. Decision tasks give all inputs up front, so they use personas lightly or not at all.

​
Two building blocks

Every persona is assembled from two components defined at the organization level. Both are reusable: build them once, attach them to as many scenarios as you like.

Identity

Who they are. Name, age, gender, occupation, education, cultural background, living context, and voice.

Personality

How they behave. Communication style, behavioral patterns, situational anchoring, and conversational modifiers.
Separating the two means you can mix and match. The same guarded, slow-to-trust personality can play a warehouse worker in one scenario and a small business owner in another. The same identity can appear cooperative in an easy scenario and defensive in a hard one.

​
Identity

Identity is the factual sketch of a person:

​
Personality

Personality is how the persona carries themselves in conversation:
  • Communication style - how verbose they are, how direct, how much emotion they show
  • Behavioral patterns - habits that recur across the conversation, like deflecting hard questions or circling back to a worry
  • Situational anchoring - how the current situation shapes their behavior, such as a normally chatty person turning short because they are in pain
  • Conversational modifiers - adjustments layered on top, like impatience after a long wait

​
Response dynamics

A persona is not a script. It reacts to what the operator does. Behavior, mood, and willingness to share all shift in response to the operator’s approach during the session. An operator who listens, acknowledges concerns, and asks thoughtful questions gets a persona who relaxes and opens up. An operator who rushes, interrupts, or fires off checklist questions gets a persona who closes down or pushes back. Two operators running the same scenario have genuinely different conversations, because the persona is responding to each of them, not reciting lines. This is what makes a session worth scoring. The conversation reflects the operator’s actual skill, and the report shows how that skill measured against the criteria the scenario defines.
How readily the persona discloses information is configured separately, through reveal triggers and revelation mechanics on the persona’s state. See Known and hidden state.

​
What the persona knows

The persona holds two kinds of information, covered in detail on the state page:
  • Known state - facts the persona knows about themselves and reveals selectively
  • Hidden state - facts the persona genuinely cannot know, like test results they have not seen
The persona never blurts out hidden state, because they do not have it. Surfacing it is the operator’s job.

​
Next steps

Known and hidden state

What the persona knows, what they cannot know, and how disclosure is controlled.

Briefing and opening

What the operator sees before the session and who speaks first.