> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcdemo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Design a demo that gets to the point

> Turn a product workflow into a clear story for a specific audience.

## Decide what the viewer should learn

Name one audience and one outcome before recording. “A new teammate can invite a colleague” is more useful than “show all workspace settings.” Choose a starting screen that gives enough context and an ending that makes the result visible.

## Make each step earn its place

Remove navigation that does not help explain the outcome. Put the instruction next to the relevant control and describe the action in the viewer's language. If the screen changes after an action, include the result rather than assuming the viewer knows it worked.

For example, “Invite your teammate” tells the viewer why the action matters; “Click the blue button” only describes the interface. Use a short title for the outcome and a brief instruction for the action.

## Review from the outside

Preview without relying on your knowledge of the product. Can someone find the next action? Is text readable at the size it will be embedded? Does each branch have a sensible destination? Does the ending offer a useful next step?

A teammate who did not build the demo can often find confusing transitions quickly. After publishing, combine their feedback with [engagement analytics](https://docs.arcdemo.io/share/measure.md) to decide what to improve.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.