Screen-sharing mistakes usually happen in transitions: opening a file picker, switching browser profiles, searching from the address bar, or responding to a question that changes the demo path. A useful checklist prepares for those transitions instead of polishing only the first screen.
One minute: define the audience boundary
Write down the applications the audience actually needs to see. For a product demo, that may be Chrome, Terminal, and a code editor. For support, it may be the customer’s app plus a knowledge base.
Everything else starts outside the boundary. An allowlist is easier to reason about than a long list of things you hope to remember hiding.
One minute: separate browser identities
Check which Chrome profile owns every window you expect to use. Work and personal profiles can have identical-looking windows while carrying different accounts, autocomplete, bookmarks, and history.
If your sharing setup cannot distinguish profiles, close the personal profile completely. If you use the ScreenK9 companion, leave personal and uncertain profiles classified as Personal or Unclassified.
One minute: test the transitions
Rehearse the risky moves:
- Cmd+Tab to every app you may need.
- Open the file chooser once.
- Create a new browser tab and focus the address bar.
- Follow one link that opens a new window.
- Trigger the menu or panel you plan to explain.
Watch the actual audience preview while doing this. A static screenshot of the opening state is not enough.
One minute: remove ambient surfaces
Notifications, the menu bar, Dock badges, desktop icons, and recent-file lists can expose context without revealing a whole private application. Hide or filter them for the audience surface.
Do not confuse notification Focus with complete protection. It reduces one class of interruption; it does not stop an accidental app switch or browser-profile mistake.
One minute: verify the share target
Name the exact target before you click Share. In ScreenK9, it is ScreenK9 — Audience View. In a one-window workflow, it is the named application window—not “Entire Screen” and not a similarly titled control window.
Ask a colleague to confirm the first frame on important calls. For recordings, capture ten seconds, replay it, and only then begin the real take.
Keep a recovery move
Decide what the audience should see if something becomes uncertain. A neutral holding slide or a protected placeholder is better than freezing the last potentially sensitive frame.
That recovery move is part of the privacy system. It gives you a safe state to return to while you fix a permission, reopen a work window, or re-establish the correct browser profile.