Plan a two-minute screen walkthrough around one task the viewer can complete, not a tour of everything your business offers. Choose a visible finish line, show only the steps needed to reach it, and reserve time to confirm success. For a solo creator or small business, this keeps the recording manageable and gives the video a specific purpose wherever you publish it.
Choose a task small enough to demonstrate
Start with this sentence: “After watching, the viewer can…” Finish it with an action and an observable result. “Understand our services” is too broad. “Find the service enquiry form and submit a request” gives you a route to demonstrate. If the task requires explaining several unfamiliar concepts first, narrow the task or use a longer format.
Example: a freelance designer wants a walkthrough showing prospective clients how to send a project enquiry. The viewer needs to find the form, understand what information to prepare and recognise the confirmation screen. They do not need a tour of the designer’s portfolio, a full explanation of pricing or an account of every possible project type.
Give each part of the two minutes a job
Use a rough timing budget before writing narration. It is a planning tool, not a requirement to speak continuously. Leave room for the viewer to locate controls and notice changes. For the enquiry example, this outline allocates the full two minutes:
- 0–15 seconds: State the task and show the starting page. Mention any information the viewer should have ready.
- 15–35 seconds: Open the enquiry form and identify the fields that need explanation.
- 35–85 seconds: Demonstrate the essential entries using explicitly fictional project details.
- 85–105 seconds: Submit in a safe demonstration environment and show the confirmation state.
- 105–120 seconds: Recap what has been completed and explain the immediate action.
Do not force a complicated process into this budget by speeding up every action. Remove optional branches first. If an important warning or prerequisite still does not fit, change the scope. A shorter task shown explicitly is more useful than a complete process that viewers cannot follow.
Separate what viewers see from what they hear
Create a two-column outline: screen action on one side, spoken explanation on the other. For each step, write the action, the reason it matters and any detail that would otherwise be easy to miss. This exposes moments where narration has moved ahead while the screen is still loading.
Example: while selecting a project category, say, “Choose the option closest to the work you need,” rather than reading every category aloud. Let the screen carry visible labels; use narration to explain decisions. Name important controls so viewers can locate them without relying solely on cursor movement. Plan captions too, but do not expect captions to rescue tiny text or ambiguous framing.
Prepare a safe, readable starting state
Open only the pages needed for the demonstration. Close unrelated tabs, hide notifications and replace real client information with fictional details. Check menus, saved suggestions and confirmation screens as well as the main page: private information can appear after a click. Use readable zoom, then verify that it has not hidden a control the viewer needs.
If the process sends messages, creates bookings or changes live records, use a safe demonstration setup where possible. Otherwise, stop before the consequential action and explain that boundary. The trade-off is that viewers will not see the real completion state; do not imply that an unshown submission succeeded.
Run one rough rehearsal before polishing
Record a rough pass without elaborate editing. Watch it once for the sequence, then again without sound. The silent pass checks whether the visible actions remain understandable; it does not replace a caption review. Use four questions to decide what to change:
- Is the starting point specific to someone who has not seen the previous page?
- Can the viewer read each important label before the next action?
- Does the recording show or explicitly explain how to recognise completion?
- Can an optional explanation be removed without losing necessary context?
Make the smallest useful revision: remove a detour, add a pause or explain the ending. If the task still feels cramped, split it into separate walkthroughs rather than speaking faster.