Who this is for: Teams choosing realistic interface states for a software explanation.
What to prepare
- Primary viewer question
- Observed empty, pending and error screens
- Supported correction steps
- Confirmed retry result
Give the interruption a learning job
An empty state teaches where to begin. A loading state distinguishes work in progress from completion. A recoverable error teaches a correction. These are different lessons, so choose the one that supports the film’s stated purpose.
Capture the actual message, available controls and next state. A generic spinner or invented error box may look familiar while contradicting the real interface. Record whether the state blocks the entire task or only one field.
Illustrative selection: adding a first sample file
For a fictional asset library, the primary question is “How do I add my first file?” The following selection keeps the starting condition and confirmation clear without turning the film into a complete support manual.
- Keep empty library: the “Add file” action explains how the task begins. Show the instruction and destination folder.
- Keep observed processing: the filename remains visible while uploading. Identify any shortened waiting in the edit.
- Keep completed item: the saved file appears in the chosen folder and can be inspected.
- Move unsupported-format recovery to a separate training cut unless the intended audience specifically needs that lesson.
- Exclude an unrelated connection failure: it does not explain this selected first-file path.
When an error is the lesson, finish the recovery
A separate illustrative recovery cut could show an actual unsupported-format message, the user choosing a permitted sample file and the successful retry. Use the product’s documented allowed format instead of inventing a file restriction.
Keep the error’s cause legible. An alarm animation without a readable message teaches nothing. The correction should address that cause, and the final state should prove that the same task is now complete.
Preserve truthful timing and scope
Do not use a loading state as the final success screen. If completion cannot be verified, end with a precise pending label. Similarly, showing one handled error does not prove the product handles all failures.
For a short introductory version, link to recovery material through the surrounding page. For training, budget time to read the error, perform the correction and inspect the retry. Remove decorative scenes before shortening those beats.
Review checklist
- Each interruption serves the stated lesson.
- Messages and controls match supplied evidence.
- Pending and completed states are distinct.
- Any recovery ends with the original task verified.