Toybird Labs BlogBelow is a fictional interface exercise, not a measured usability test. Both “Immediate notifications” and “Weekly summary” start on. The goal is to turn off immediate notifications while leaving the weekly summary on.
Write what the audience should learn first
The outcome is not “I clicked a switch.” It is “Immediate notifications are off; the weekly summary remains on.” Naming the result stops the presenter from showing several unrelated settings just because they are nearby.
| Time | Say | Do | Attention cue |
|---|---|---|---|
| 0–5 seconds | “We will stop immediate notifications but keep the weekly summary.” | Leave both controls visible | No extra highlight yet |
| 5–10 seconds | “This is the immediate-notifications control.” | Position the pointer at that label/control | Brief pointer highlight |
| 10–16 seconds | “These two settings are separate.” | Show the two-row area without changing either | A short range highlight if helpful |
| 16–22 seconds | “I am turning only this one off.” | Click the immediate-notifications switch once | Keep the action visible; avoid unnecessary movement |
| 22–30 seconds | “Immediate is now off; weekly is still on.” | Pause on the final state | Let the result, not another animation, be the focus |
Practice in this article
Illustrative exercise, not the application interface.
The timings are an editorial rehearsal target. They are not a measured optimum or an app performance claim.
Use a point for a point, and a range for a relationship
A pointer highlight can answer “which button?” A range can answer “which rows belong to this explanation?” Neither replaces readable labels, suitable zoom or a sentence explaining the purpose. Highlighting the whole screen when only one switch matters can make the target less clear.
Pointer Cue can provide temporary pointer and range emphasis on Mac. Use the gesture configured in the installed release. Do not add persistent drawings when the explanation only needs a momentary marker; equally, choose a drawing tool when an arrow or annotation must remain for later reference.
Rehearse without assuming the audience saw the click
After the operation, state the resulting status and hold it briefly. Saying “as you can see” is less informative than naming the two final states. A viewer joining late or using a small screen can then reconnect the action with its purpose.
Run the same script once without extra cues and once with a pointer/range cue. Compare whether the target and final state can be identified, not how many visual effects appear. This exercise helps you choose where a cue is useful; it is not evidence that one version is universally better.
Check the receiving view, not only your own monitor
Before a real remote demonstration, use harmless content and check the participant's view at the intended resolution and sharing mode. Cursor size, small text and subtle lines may not remain equally clear after capture and transmission. The supplied product demonstration illustrates local actions, not a receiver-side compression test.
Keep the software demonstration distinct from this worksheet
A product clip showing a website can explain how temporary highlighting looks. It is not the execution record for the fictional notification settings above. Likewise, a pre-release clip should not be used to promise features or entitlement rules in the current release.
Turn the script into your next demo
Replace the two fictional settings with one real, non-sensitive task. Write its before and after states, select one point where a marker adds information, and practise the pause after the change. Use Pointer Cue where a temporary cue supports the sentence. Leave it quiet where the interface result already makes the meaning clear.