Skip to main content
A useful demo answers a question the viewer already has. Before recording, write down who it is for, what they need to understand, and what you want them to do next. Those three choices determine which screens belong in the demo.

Start with the outcome

Use this brief before opening the recorder: This is a fictional example, not a template you must follow. Replace the question and outcome with your viewer’s actual problem. If the demo tries to answer three unrelated questions, consider separate flows or separate demos.

Storyboard the path

Write the start and finish first. Then list only the actions that connect them. For the example above: open the dashboard → filter for late orders → open a result → explain the follow-up. Include a state before an action and the result after it; otherwise a viewer may click without seeing what changed. For each screen, ask:
  • What should the viewer notice? Show the part of the interface that proves the point.
  • What should they do? Use one clear action in the guide, such as “Select Late” rather than “Explore the filters.”
  • Why does it matter? Explain the result when the screen does not make it obvious.
  • Where can they go next? Give the path a deliberate ending, including a next action where appropriate.
Cut setup that the audience does not need to understand. Keep enough context that the final screen makes sense. A shorter demo is useful only if it still answers the question.

Prepare before capture

Use a test account and representative data, set the window size, dismiss unrelated notifications, and rehearse the path once. For a sandbox, plan the alternative states and return paths as well as the happy path. Choose a capture method for the experience, not just the fastest recording. After recording, compare the result with the brief. If a screen does not support the viewer’s question, remove it or explain why it matters. Continue with write effective guides and review before publishing.