Plan the scene before recording. It is usually easier to prepare the right material than to repair an accidental disclosure in the edit.
Decide what the scene must explain
Write the action the viewer needs to understand: “Open an enquiry, assign an owner and show the next task.” Then list the screens needed to explain it.
You may not need a full desktop recording. A tighter capture can make the workflow easier to follow and reduce unrelated information in view.
If you use a demo account or fictional records, say so beside the recording. It can explain the product without pretending to be a customer’s actual activity or results.
Make a scene and data map
This example is fictional.
| Scene | Data needed | Preparation |
|---|---|---|
| Enquiry list | A few representative records | Use clearly labelled sample names |
| Enquiry detail | Owner and next-action fields | Remove unrelated messages and commercial notes |
| Task view | One follow-up task | Use a fictional date and assignee |
| Transition between screens | No additional data | Close notifications and unrelated browser tabs |
Ask the customer which records and screens they are permitted to show. Keep the source recording and the public export within the agreed handling arrangements.
Prepare for movement
Sensitive material can appear for a fraction of a second in a menu, notification or loading state. A crop that works on the first screen may fail after a panel opens.
Rehearse the clicks. If the scene requires a live search, consider whether the results could reveal information outside the agreed example. Prepare a safer demonstration path where possible.
When editing is necessary, inspect the redaction through the complete movement. TechSmith’s blur guide illustrates editing techniques; a blur effect by itself is not a complete privacy assessment.
Review the finished export
Watch the actual file at normal speed and pause at transitions. Check:
- Names, email addresses and profile pictures.
- Sidebars, tabs and notification banners.
- Account identifiers, URLs and document titles.
- Amounts, customer notes and attached files.
- Subtitles or narration that might repeat removed information.
Review at the size and crop intended for publication. Also check whether a thumbnail or preview frame exposes something the main edit hides.
Preserve the explanation
Removing private information should not make the workflow misleading. If the values are illustrative, label them. If a cut omits a waiting period, avoid implying that the action completed instantly.
The final reviewer should be able to explain what is real product behaviour, what is sample data and what customer material is approved for use.
For the broader assignment, use the testimonial video production brief. This scene-level plan gives the editor the concrete instructions that a general promise to “hide private data” cannot supply.