SEO fieldnotes

Tutorial design

25 checkable notes for tutorial design.

1. Write a prerequisite checklistReaders fail before the first instruction.
2. Show the expected resultSteps tell users what to click but not what should happen.
3. Explain a disabled controlA grey button gives no useful direction.
4. Write a reversible practice taskA tutorial risks changing important work.
5. Teach a destructive actionDeletion instructions need a clear decision boundary.
6. Use screenshots sparinglyToo many images obscure the actual instructions.
7. Write keyboard instructionsMouse-only steps exclude other users.
8. Handle a slow operationReaders may repeat an action while it is pending.
9. Explain a permission errorA failed action is presented as a generic outage.
10. Write a conflict recovery guideA stale draft cannot safely overwrite newer work.
11. Teach export verificationA successful download may contain the wrong version.
12. Explain a missing history stateA user expects versions that were never recorded.
13. Write a short troubleshooting branchA long decision tree overwhelms the main task.
14. Teach a mobile workflowDesktop navigation names do not match mobile controls.
15. Write a first-draft walkthroughA guide assumes content already exists.
16. Explain a restore confirmationThe action copies old text into a new candidate.
17. Teach a review handoffThe tutorial stops after editing.
18. Write a no-account learning pathSignup is unavailable or unnecessary for practice.
19. Explain a reload checkA UI success message may hide unsaved state.
20. Document a changed navigation pathA tutorial references an old menu.
21. Teach a source attachment practiceA draft needs recoverable evidence.
22. Write an empty-state explanationNothing is displayed and users cannot tell why.
23. Explain a safe retryRepeating a mutation can create duplicate work.
24. Teach an account switchPrivate content must not bleed into another workspace.
25. Close a tutorial with verificationThe final click is not proof of completion.