Choose one task with a stable result
A useful tutorial carousel lets someone repeat a real workflow. Use one task and a consistent sample object. This fictional notes-app example teaches how to locate a call note and identify its next step; it is not an actual product screenshot or customer result.
Keep the prerequisite close to the beginning: the viewer needs a workspace containing the sample note. If your app has another starting state, rewrite the sequence instead of assuming the same navigation.
Pair each slide with one visible instruction
The seven-slide table provides original copy and evidence directions. Capture the real interface for your product. Highlight one relevant control without covering its label, and retain enough context to orient the viewer.
Do not use a generated dashboard as proof that a feature works. If a screenshot needs annotations, distinguish the annotation from actual UI. A drawn arrow should help locate the control; it should not impersonate a product confirmation.
Start
PROJECT ATLAS Choose Call notes
Middle
MONDAY CALL Open the note
Finish
NEXT STEPS Read the actual task
| Decision or state | Example | Review |
|---|---|---|
| 1 — Goal | Find the next step from your last call | Show the destination, not an unsupported outcome. |
| 2 — Prerequisite | Open the project with your call note | Use safe sample data. |
| 3 — Navigate | Choose Call notes | Show the actual navigation label. |
| 4 — Select | Open Monday’s call | Keep the project consistent. |
| 5 — Locate | Find the Next steps section | Make its text readable. |
| 6 — Recover | Missing note? Check the project and access | Use your real recovery guidance. |
| 7 — Continue | Use the next step before your follow-up | Link to matching task instructions. |
Review the sequence as instructions
Check the slide order against the live workflow. A missing prerequisite can make a beautiful carousel unusable. Include a truthful recovery instruction for a missing note or unavailable control rather than promising identical results for every account.
Use consistent labels and make the resulting next step readable at normal phone size. Avoid adding a second teaching task merely to fill a slide count. Seven is the length of this example, not a required format.
Provide context outside the image
Write accompanying text that explains the task and links to maintained instructions. Add meaningful text alternatives where the publishing surface supports them. Do not rely only on arrows, color or screenshots to communicate the action.
Before sharing, ask a fresh reviewer to follow the carousel in an eligible account. Record the point where they hesitate. Revise that instruction or image, then check the actual export and destination rather than only the design canvas.
Copy the planning worksheet
Use this worksheet in your own notes. Fill it with verified product details and actual review observations before sharing an asset.
One task and prerequisite:
Slide words -> exact screenshot:
Annotation purpose:
Real labels / safe data check:
Recovery instruction:
Text alternative / accompanying explanation:
Fresh reviewer hesitation:
Export and destination review:Browse the founder guide library for the next task in your workflow.