How Do You Write Step-by-Step Instructions Someone Can Follow?

Good instructions help someone reach a clear result without having to guess what you meant. Start by naming the task and the intended reader, then describe the actions in the order they must happen. Finish by showing how to recognize success and testing the draft with someone who does not already know the process.

The challenge is often noticing the small decisions you make automatically. A beginner needs those decisions written down.

Define the reader and the finish line

Choose one task with an observable ending. “Create a reading list” is a more manageable scope than “Organize your reading.” Say what the instructions cover and, when necessary, which device, app version, or starting situation they assume.

Decide what your reader already knows. Someone familiar with an app may need only the relevant menu names; a first-time user may need help finding the starting screen. Digital.gov’s plain-language principles emphasize writing for the audience’s actual knowledge and experience.

Write a working finish line before drafting: “At the end, you will have one named list containing three book titles.” That gives you something specific to check later.

Put preparation before the numbered steps

List the materials, access, files, or information someone needs before beginning. Keep this separate from the actions so readers can prepare without hunting through the procedure. Google’s procedure guidance recommends giving readers necessary preparation information in advance.

For an everyday digital task, your short preparation list might identify:

• The app and starting screen.
• Whether an existing account is needed.
• The information the reader will enter.
• Any earlier task that must already be complete.

Only include genuine prerequisites. An optional preference does not belong in a list of requirements.

Write actions in the order they happen

Use numbers when order matters. Give each meaningful action its own step, and begin with a direct verb such as open, select, enter, or place. Include the final action that actually completes the task, rather than stopping just before the reader must confirm it. These practices align with Microsoft’s instructions guidance.

Put a condition before the action it controls: “If the list is empty, select Add a book.” The reader should discover whether a step applies before performing it. Likewise, identify the location first when necessary: “In List details, select Rename.”

If a step becomes a paragraph full of decisions, split it. If different readers need substantially different routes, give each route a separate heading.

Use names the reader can recognize

When identifying an onscreen control, use its actual label. Avoid substitutes such as “the usual button” or “the thing on the right.” Google’s guidance on interface elements recommends naming controls by their labels and avoiding directional descriptions that may not work for everyone.

Keep your terminology stable. If you call something a list, do not switch to collection halfway through unless those are genuinely different features.

Here is a fictional example using an imaginary reading-list app. The labels and behavior are invented solely to demonstrate the writing technique.

Before: Open the app, make a list, put your books in, and finish.

After: Create a reading list containing three books. Begin on the app’s My lists screen with three book titles ready.

1. Select New list.
2. In List name, enter Weekend reading.
3. Select Create list. An empty list opens.
4. Select Add a book.
5. In Book title, enter your first title.
6. Select Save book. The title appears in the list.
7. Repeat steps 4–6 for the other two titles.

Check: The heading reads Weekend reading, and exactly three book titles appear beneath it.

The revised version supplies a starting point, recognizable controls, and a visible result.

Place illustrations where they help

Use an image when it resolves a visual question, such as which part of a screen contains a control. Place it beside or immediately after the relevant step, rather than making readers search elsewhere.

Crop screenshots to the useful area, remove private information, and keep essential instructions in text. Provide appropriate alternative text for informative images. Google’s image guidance explains these accessibility and clarity considerations.

Test the instructions without filling in the gaps

Ask someone who resembles your intended reader, ideally a newcomer to the task, to try the draft. Have them explain what they are looking for while you observe. Note where they hesitate, choose the wrong item, or ask for help. Digital.gov’s usability-testing guidance recommends observing representative readers and retesting after revisions.

Avoid explaining every confusing step immediately; your explanation can hide what the page needs to say. Revise the instructions, then test again.

Before sharing, check one final question: can the reader tell both what to do next and when the task is complete?