Write your first outcome brief

Choose an observable situation. For example, a new service representative cannot resolve a routine delivery query without calling a manager. Describe the task, the people involved, and where work slows down. Avoid opening with a requested format such as a ten-module course: the format should follow the problem.

Write an outcome as a person performing a task under stated conditions. Our fictional representative should identify the applicable delivery rule, explain the next step, and escalate an exception correctly. Specify the assessment conditions and the quality threshold. Agree on any numerical target with the role owner after reviewing the baseline.

Record the cohort, source materials, reviewer, decision date, and effort limit. State what the pilot excludes: perhaps refunds, individual employee evaluation, or customer messaging. Choose one person who can accept the result. If several departments participate, record which decision belongs to each instead of giving everyone an undefined approval role.

A suitable first output is a proposed learning path with one practice task and an assessment rubric. Ask how each element connects to the outcome. In the intended Elvina workflow, a reviewer should inspect that plan before learners receive it. Whether a particular environment supports this sequence must be verified.

Give the brief to someone outside the project. Ask them to identify the learner, desired behavior, evidence, exclusions, and decision owner. Any disagreement reveals a missing definition. Revise the brief until those answers are consistent, then preserve that version so later changes to the experiment remain visible.