How to write a step-by-step guide people actually follow
Seven rules for how-to guides that work, from one action per step to screenshots that show where to click, plus a checklist you can copy.
A good step-by-step guide lets someone finish a task without asking anyone for help. To get there, write one action per step, start each step with a verb, show a screenshot of exactly where to click, and test the guide on someone who has never done the task.
Most guides fail for the same few reasons: steps that hide two actions, screenshots that don't match the screen, and missing context about why a step matters. Here's how to avoid them.
1. Start with the outcome
Before the first step, say in one sentence what the reader will have at the end, and what they need before they start.
Goal: invite a teammate to your workspace. You need: admin access and their work email.
This lets readers check in five seconds whether they're reading the right guide.
2. One action per step
"Open Settings, go to Members and click Invite" is three steps pretending to be one. When a reader gets lost, they can't tell which part failed.
Split it:
- Open Settings.
- Go to Members.
- Click Invite member.
More steps that each take two seconds beat fewer steps that each need re-reading.
3. Start every step with a verb
Click, select, type, open, choose, copy. A verb at the start tells the reader what to do before they read anything else. Put the name of the button or field in bold, spelled exactly as it appears on screen.
| Weak | Strong |
|---|---|
| The Members page is where invitations happen. | Go to Members. |
| You'll want to enter the email. | Type their email in Email address. |
4. Show where, not just what
A screenshot is worth a paragraph only if it shows the reader where to look. For each step:
- Capture the screen just before the action, so it looks like what the reader sees.
- Mark the exact button or field with an outline or arrow.
- Crop or blur anything private: names, emails, customer data, API keys.
Screenshots taken after the click show the result of the click instead of where to click, which is one of the most common ways guides confuse people.
5. Add a tip only where people slip
Most steps need no explanation. Add a short tip only where readers often go wrong: a setting with a side effect, a button that's easy to confuse with another, or a field with a required format.
Tip: if the invitation expires before they accept it, resend it from the same page.
6. Keep guides up to date
Software changes, and a guide with an old screenshot is worse than no guide, because readers stop trusting all of them. Note when each guide was last checked, and re-record the ones for screens that changed.
7. Test it on a beginner
Give the guide to someone who has never done the task and watch, without helping. Every place they hesitate is a step to split, rename or illustrate. One test like this catches more problems than any amount of re-reading.
A checklist you can copy
- One sentence on the goal and what you need before starting
- One action per step, starting with a verb
- Button and field names in bold, exactly as on screen
- A marked-up screenshot for every step, taken before the action
- Private data blurred
- Tips only where people slip
- A "last checked" date
- Tested on someone new to the task
Doing this faster
Writing guides this way by hand takes a while: take each screenshot, crop it, mark it up, write the text, and do it all again when the screen changes. Guidie does the mechanical part for you. Record the task once in your browser, and it captures a screenshot before every click, outlines the target, and writes one instruction per step, with a narrated video if you want one. You then review and adjust the text instead of starting from a blank page.
You can see the flow in the demo, or read how support teams use it.