Turn a screen recording into a step-by-step guide.

Start with one complete task.

A good guide has a clear starting point and a visible result. “Invite a teammate” gives the reader a task to finish. “A tour of our settings” gives them a collection of screens without a reason to use them.

Before recording, write down who the guide is for, what permission they need, and what they should see when they finish. Keep those answers beside you while you capture the workflow.

Review the narration before generating the guide.

Speech explains a task differently from written instructions. It can include an aside, a correction, or a reference such as “click that one.” Your reviewed script should name the controls and explain the action in order.

In Polysh, correct product names and button labels before generating the guide. Keep useful background, but separate it from an action the reader actually needs to take.

Check the action, screenshot, and result.

Polysh turns the reviewed narration into grouped steps, prerequisites, notes, and expected results. Treat the generated guide as a draft to review.

• Action: does the step say what to do using the visible control’s name?
• Screenshot: does it show the screen the reader needs at that moment?
• Result: can the reader tell whether the action worked?

A step with the wrong screenshot is confusing. If the generated guide has no suitable image, choose from the captured candidates or leave it out until you have the right one. Check sensitive information before sharing.

Publish a reference people can use.

Download the reviewed guide as a PDF or share it with the intended audience. For a guide that accompanies a video, keep the purpose consistent even though the wording differs: the video explains the path; the guide helps someone take it.

When the workflow changes, update the script and review the guide again. Making the guide again replaces its edits for the selected languages, so preserve any important manual changes before regenerating.