- State - the facts of the situation, split into what is visible and what must be discovered
- A persona - the simulated person the situation revolves around
- Outputs - the decisions and artifacts the operator is expected to produce
- Criteria - the definition of what good looks like, written down before anyone runs the scenario
Decision tasks
Case material in, a decision and its rationale out. The simplest shape, and the fastest to build.
Conversations
The facts are held by a persona. The operator has to earn them before they can decide anything.
Journeys
The same client over simulated weeks or months. Early choices change what later sessions look like.
Which shape fits your problem?
Who runs it is a separate question
Scenario shape says nothing about who sits in the operator seat. Any shape can be run by:- Your people - to capture how your experts handle it, or to measure a team at scale through cohorts
- An AI agent - to benchmark a model, a prompt, or your own chatbot against the same criteria your people are measured on, in automated runs
Variants
A scenario can have variants: child scenarios that inherit everything from a parent and override specific fields. Use variants to create difficulty levels (the same case with a more guarded persona) or alternative angles (the same client, a different presenting problem) without rebuilding the scenario.Next
Start with a decision task
The simplest shape, explained with a worked example
Scenario anatomy
The shared building blocks: personas, state, briefing, outputs, criteria