Who this is for: Teams producing form-completion training.
What to prepare
- Actual validation evidence
- Invalid and corrected states
- Saved result
- All required-field context
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Show the task
Display the sample request form with Quantity labeled and other required fields accounted for.
On screen:Submit the sample request
- 02
5–10s
Enter the invalid value
Enter 0 in Quantity and trigger validation through the actual observed action.
On screen:Quantity: 0
- 03
10–16s
Read the feedback
Hold the exact supplied validation message beside the field; the illustrative wording is Enter a quantity greater than zero.
On screen:Check the quantity requirement
- 04
16–21s
Correct the cause
Replace 0 with 3 while preserving unrelated entries.
On screen:Quantity: 3
- 05
21–26s
Retry the submission
Perform the real submit action and show actual pending or confirmation feedback.
On screen:Submit the corrected request
- 06
26–30s
Verify the result
Hold the saved sample record with quantity 3 and a stable identifier.
On screen:Submission confirmed · Quantity 3
Make it your own
- Validation rule and values
- Replace invalid zero and corrected three together using a harmless observed rule.
- Exact feedback
- Use the real validation wording and the action that triggers it.
- Saved result
- Supply confirmation and a matching created record with the corrected value.
Prepare validation facts
Capture the actual invalid condition, message and trigger. Do not assume positive integers are required unless the product confirms it. Replace the example consistently when a different field rule is used.
Adapt the error
For a missing reviewer, show the empty selection and choose a valid role. For a date issue, retain the exact accepted format. A 15-second cut may omit general context but must preserve feedback, correction and confirmation.
Review recovery completion
Clearing a red border does not prove the form was submitted. Inspect the created object after retry and confirm that other fields retained their real values. Do not invent an error just to make a shipping-product demo more dramatic; a hypothetical teaching example must stay labeled.
Review checklist
- The shown correction resolves the shown cause.
- Feedback has a readable hold.
- The final state proves successful submission.