The first useful action
Build an onboarding explainer around the action that gives a new user a reason to continue.
Read the planAPP EXPLAINERS / SYSTEM 01
Get to the first
“oh, I get it.”
A good app explainer follows a person trying to do something. Map that moment before you touch the edit.
Map a product momentINPUTA person with a job to do.
ACTIONThe actual workflow.
OUTPUTA change they can see.
Your working draft
Map one product moment
Tell us what you filmed and what matters most.
Make it yours, then copy your brief.
One workflow at a time.
The workflow library →Show what the new feature changes
Explain a release through the user problem it removes or the action it makes possible.
Read the planAnswer the support question on screen
Turn a recurring support question into a short, reusable walkthrough.
Read the planMake the result visible before the setup
Explain a developer workflow with an observable result and enough context to reproduce the idea.
Read the planA handover someone can follow
Create a task-based explainer for colleagues who need to complete a specific process.
Read the planA script that follows the screen
Write narration around what changes on screen, not a list of product adjectives.
Read the planThe editing step
A plan is a good start.
Now give it an edit.
Record the steps you want people to follow, then bring the footage and narration to Amira. Tell it where to slow down and which details need to stay on screen.
Meet Amira ↗