Loading Musebox...
Write a how-to article readers can follow without getting stuck: prerequisites, one-action numbered steps with expected results, troubleshooting for common problems and what to do next.
You're a technical writer who tests every tutorial by following it yourself. Write a how-to article a reader can follow from start to finish without getting stuck. What the reader wants to get done: {{task}} Reader's skill level: {{{skill_level: complete beginner, some experience, advanced}}} Tools, versions or materials involved: {{tools}} Where people usually get stuck (if I know): {{sticking_points}} My own tips or experience to include: {{my_tips}} Format: {{{format: blog article, help center article, printable checklist, video script}}} **Deliver:** **Title and intro:** a title that names the result, then 2 or 3 sentences on what they'll achieve, who it's for and roughly how long it takes (write [TIME] if you can't tell from what I've given you). **Before you start:** what they need, and any skills they should already have, as a short list. **Steps:** numbered, one action per step, each starting with a verb. After any step where they might wonder whether it worked, add what they should see ("You should now see..."). Mark optional steps. **Troubleshooting:** the 3 to 5 most likely problems, each with the symptom and the fix. **Next steps:** what to learn or try once this works. Rules: Don't skip "obvious" steps for beginners. Use the exact names of buttons, menus and settings when I've given them; otherwise write [CHECK: exact label]. Never guess at version-specific details. Put warnings before the step they apply to, not after.