Source: https://polysh.io/examples/

EXAMPLES

# One task.  Two clear ways to share it.

See how a rough explanation becomes a focused narration and a guide someone can follow. These examples use a fictional Acme workspace.

[Explore the team invite](#team-invite)

TEAM INVITE · EXAMPLE

## From “let me show you” to “here’s how.”

THE SCREEN

One clear ending: the teammate’s invitation is pending.

THE GUIDE

STEP-BY-STEP GUIDE · EXAMPLE

### Invite a teammate.

**For:** a workspace administrator.

**You’ll need:** permission to invite and your teammate’s email.

01

### Open Your team.

Choose **Your team** in the workspace sidebar.

02

### Send the invitation.

Choose **Invite member**, enter the email, and send.

03

### Check the result.

The new teammate appears with an **Invite pending** status.

Same workflow. A reference someone can keep beside them.

THE WORDS MATTER

## Keep the task. Lose the detour.

THE ROUGH TAKE

“So, um, you just go here and then, uh, click on your team to add someone. Put the email here, and then, yeah, send that.”

THE REVIEWED NARRATION

“Open Your team and select Invite member. Enter your teammate’s email, then send the invitation. Check that their status reads Invite pending.”

The reviewed version names the controls, follows the action on screen, and ends with a result the viewer can recognize. You review the script before turning it into narration.

WEEKLY STATUS · EXAMPLE

## A procedure needs a finish line.

THE VIDEO EXPLAINS THE PATH

### Publish the weekly status.

Open this week’s status page, add the approved notes, check the date, and publish. Keep the recording focused on the coordinator’s actual actions.

[See the SOP workflow](https://polysh.io/use-for/sop-documentation/)

THE GUIDE MAKES IT REPEATABLE

### Give the next person the checks.

**Before starting:** have the approved notes and permission to edit.

**Expected result:** the published page shows the correct week and approved update.

**Final check:** open the published page as a reader.

[Turn a recording into a guide](https://polysh.io/blog/screen-recording-to-step-by-step-guide/)

YOUR FIRST PROJECT

## Use this pattern for a task of your own.

1. 01
  ### Record one complete task.
    Start on the screen your audience will use. Finish on the visible result.

2. 02
  ### Review the explanation.
    Fix control names, remove the detours, and make sure the words match what happens on screen.

3. 03
  ### Make the useful outputs.
    Create the narrated video, generate and review the guide, then export or share the result.

MAKE IT CLEAR

## What do you explain  more than once?

That is a good place to start.

[Explore the workflow](https://polysh.io/how-it-works/)