​
The Library

The Library is your organization’s collection of reusable definitions. You define each item once, then link it into as many scenarios as need it. Managing the library requires Admin access.

​
What lives in the library

Documents or records an operator should produce during a scenario, such as summary notes, action plans, or referral letters. See Outputs.
Choices an operator should make, such as approve or deny a claim, or escalate to a specialist. See Outputs.
Structured criteria that grade the quality of a session, with named criteria and scoring levels. See Defining good.
The words your domain uses, defined once so personas and scoring use them the same way in every scenario.
What is in and out of bounds for operators in your domain, such as actions they must hand off rather than take themselves.
Named collections of how your organization expects work to be done, attachable to any scenario that should measure against them.
The two components a persona is built from. An identity is who the persona is; a personality is how they behave. See Personas.

​
Inline or linked

Scenario outputs can be defined two ways:
  • Linked from the library for definitions used in more than one scenario.
  • Inline on a single scenario for one-offs that will never be reused.
Default to linking. Define inline only when you are certain the definition is specific to one scenario.

​
Why linking matters

A linked definition is the same definition everywhere it appears. That gives you two things:
  1. Consistency. Every scenario that links a rubric or decision definition evaluates against identical criteria. No drift between copies.
  2. Comparability. When ten scenarios share the same linked definitions, you can compare results across them. Scores against the same criteria mean the same thing.
Inline definitions give you neither, because each one exists in exactly one scenario.

​
Where to go next

Outputs

How artifacts and decisions work inside a scenario.

Defining good

How to write criteria worth scoring against.