Turn a product workflow into an accessible tutorial

Decide what the viewer should learn

Choose one concrete journey, such as creating an account or reviewing a saved report. Write the starting state and the result the viewer should be able to reproduce. Use a synthetic account and safe sample data for capture. Remove secrets, personal records and internal diagnostics before recording. Obtain rights for screenshots, music, voice and footage rather than assuming an installed tool grants them.

Review the product before filming

Ask a UI/UX reviewer to use the actual desktop and mobile journey, including keyboard focus, validation and a failed request. A tutorial should not conceal a broken flow by cutting around it. Keep the approved brand palette and typography. Explain settings in product language; implementation detail belongs only where it helps the viewer make a decision.

Script and divide roles

Assign the subject expert the factual steps, the voice role pronunciation and narration, and the video role timing, captions and exports. Give them one shared script revision. Clearly mark illustrative or sandbox scenes. If a provider is not configured, teach the setup state honestly; do not fabricate a successful API response for the film.

Build with the licensed implementation

For code-driven video, use the real rendering library and its documented composition/export workflow. Remotion’s licensing terms depend on the user and use case, so review the current licence rather than calling all uses free. Pin the library version and retain notices. Generate narration with a consented voice, then time captions to the actual audio. Keep original assets and work in a project-specific output directory.

Verify the exported file

Watch the complete export at the target size. Listen for clipped audio, mispronounced names and abrupt joins. Confirm text fits on mobile, captions are readable and controls remain visible. Compare the final steps against the real product again after UI changes. Save export dimensions, frame rate, duration, asset provenance and review findings. A browser preview is not evidence that the final video encoded correctly, and a sample render does not imply the underlying service is accepted.