Who this is for: Product and support teams teaching existing users.
What to prepare
- Complete verified task sequence
- Role and setup requirements
- Checkpoint evidence
- Relevant exception and recovery states
- Confirmed final result
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative brief: create a 60-second training sequence for submitting a sample review request in a fictional workspace. State contributor access, prepared sample assets and an available reviewer as prerequisites. Show required fields, recipient selection, the actual preview or inspection step, submission and confirmed request status. End with the saved identifier and selected reviewer. Keep approval as a later task. Include a missing-reviewer correction only if the supplied product evidence supports it and the timing remains readable; otherwise provide a separate recovery lesson.
Define a repeatable task
Suitable inputs include the complete observed workflow, role rules, required fields, actual error messages and the final-state evidence. Choose a task a viewer can recognize and repeat, such as submitting a request or locating a missing item.
A promotional montage, obsolete interface captures or a prototype without implemented behavior cannot serve as current operational training without clear qualification. Resolve missing product facts before presenting a sequence as instructions.
Use checkpoints for longer work
Group actions around meaningful states: prepared input, checked recipient, inspected preview and verified submission. Each checkpoint should have a visible condition that tells the learner whether they are ready to continue.
Do not divide a task into equal time blocks merely for visual rhythm. A consequential permission choice may need more explanation than several routine keystrokes. Compress repetition while keeping required decisions and commitments.
Teach one relevant exception
Choose an exception that helps the intended learner complete the same task. A missing reviewer can be shown through the actual validation message, corrected selection and successful retry. An unrelated network failure may deserve a separate troubleshooting video.
Avoid inventing a universal fix. When a request is missing because a filter excludes it, show the filter diagnosis before clearing it. Other causes, such as permissions or deletion, require different evidence and advice.
Verify the finish and maintain it
The final screen should show the same object with the promised resulting state. Submission is not approval; a pending job is not a completed output. Use precise labels so learners know when their responsibility ends and another role’s work begins.
Record the product version, source assets and verification owner. Review the training after changes to controls, permissions or required fields. The illustrative brief here is a planning asset, not a tested training program or evidence of learner performance.
Review checklist
- Required decisions are not hidden by editing.
- Each checkpoint has an observable condition.
- Any exception has a supported correction and retry.
- The final state matches the task’s actual completion boundary.