Instructions can seem obvious to you because you already know the outcome, while a reader stops at the first missing detail: which file, where should it go, and what does “finished” mean? Writing repeatable steps means transferring the knowledge in your head into a procedure another person can follow, then comparing the result with a defined outcome without guessing your intentions.
We will use an original teaching example: preparing an envelope containing three cards. This is not a report of an actual experiment or a claim that users tested the procedure. It illustrates how to write and review instructions. The image is generated for an imaginary stationery exercise. The content was prepared with AI assistance and has not received independent human editorial review.
Define the result before writing the first step
Begin with something observable: “An open envelope containing one square card, one circle card and one triangle card, with no extra cards.” This is narrower and clearer than “prepare the materials correctly”. A reader can remove the cards, count them and compare their shapes without knowing your private definition of a good arrangement.
Separate the required result from details that do not affect it. If card order does not matter, changing their positions should not count as a mistake. If order matters in another task, state it explicitly with a useful reason. Every constraint should serve the goal; otherwise it becomes a distraction from the actual success criterion.
State the starting point and materials
Our example needs an empty envelope and three ready-made cards: one showing a square, another a circle and the third a triangle. The procedure does not assume printing, cutting or additional tools. Say this before the steps so the reader does not discover halfway through that an essential material is missing.
For a digital procedure, the starting point might be an open sample file or an account with a particular permission. Describe these conditions without asking the reader to share a password or bypass their access rights. If a condition is unmet, the correct response may be to stop and obtain the proper resource, not to continue through an undocumented workaround.
Specify the action, its location and the observable result
Google's procedure-writing guidance discusses ordered steps and task context. In our exercise, “get them ready” is incomplete. “Place the three cards in front of the envelope so you can inspect their shapes” identifies the objects, the action and the reason for the position.
Do not bundle unrelated decisions into a long sentence. Conversely, avoid splitting a simple movement into artificial fragments that do not help the reader. A step is an understandable action whose completion can be identified, not a fixed number of words. A shorter sentence is not automatically clearer if it removes necessary information.
A complete example of a small procedure
The aim is to prepare one envelope with the specified cards, leaving it open for inspection. Use sample materials only; do not include personal documents in this exercise.
- Place the empty envelope and three cards on a surface where you can work clearly.
- Inspect the shapes: there must be one square, one circle and one triangle. If a shape is missing or repeated, stop and obtain the correct set.
- Count the cards before inserting them. The required count is three.
- Put the three cards inside the envelope and leave it open.
- Remove the cards for inspection. Check for one of each shape and confirm there is no fourth card.
- Return the checked set to the open envelope and record that the contents check is complete.
The final check is different from simply seeing an envelope on a table: an envelope can be present while its contents are incomplete. We also avoid asking readers to seal and reopen it, because sealing is not part of the exercise's goal. Do not introduce a change that the outcome criterion does not need.
Make vague wording observable
| Vague wording | More precise wording for this exercise | What can be checked? |
|---|---|---|
| Take the appropriate things | Select a square card, a circle card and a triangle card | Presence of all three shapes |
| Put them there | Put the cards inside the open envelope | Card location and envelope state |
| Make sure everything is good | Count three cards and check for one of each shape | Count and shape variety |
| Repeat as needed | Prepare six envelopes, each with a complete set | Envelope count and each envelope's contents |
If the task expands to six envelopes, you need six cards of each shape: 6 × 3 = 18 cards altogether. Having 18 cards is not sufficient on its own; they might all be squares. Verification therefore combines quantity with the distribution of types. Neither replaces the other.
Separate alternatives and choices from the main route
If adding a label is optional, mark it as optional and explain that its absence does not fail the task. If two completely different routes are available, present each as a separate procedure rather than mixing both into every line. Readers need to know which route they are following and when their responsibility ends.
A missing branch should not send someone back to an unclear beginning. If the triangle card is missing, for example, return to checking the set after obtaining it, rather than preparing every completed envelope again. State the restart point, especially when repetition could duplicate work or change materials already checked.
Use images to clarify what is difficult to describe
Microsoft's instruction checklist covers presentation and interaction options. The picture in our exercise helps identify shapes, but it does not prove how many cards are inside the reader's envelope. The written check remains necessary; an illustration is not evidence of success.
For an interface guide, use the visible element name instead of relying only on “the blue button on the right”. Colour and position can change. Alternative text should describe the relevant information. Remove personal information from a screenshot before sharing it, and do not present a fabricated image as documentation of a real product interface.
Test the document without supplying the answers
When a trial with an appropriate participant becomes possible, provide the instructions and specified materials, then observe where a question arises. If you verbally explain a missing step, record that assistance. Success afterwards does not demonstrate that the text alone was sufficient. Revise the wording and try again from the declared starting point.
Write precise observations: “Stopped at the word ‘set’ because the required shapes were unclear” is more useful than “did not understand”. In a hypothetical scenario, if two readers completed the task with help and a third has not tried it, do not report “three successful independent tests”. Retain each attempt's outcome, conditions and preceding revisions.
Explain what happens when the result differs
If an envelope contains four cards, compare them with the list before removing anything. The aim is to identify the extra card, not to discard a random one merely to reach three. If the triangle card is absent, stop at the part that requires it. This distinguishes addressing the reason for a mismatch from making the final number look right.
In software or equipment instructions, an unexpected result is not a reason to replace the manufacturer's procedure with a full reset or file deletion. Specify what can be recorded safely and where to obtain appropriate support. A repeatable procedure is not permission to repeat an action that might produce additional effects each time.
Keep a version and state the limits
Give the document a clear name and a version number or date, and record what changed. If a later version replaces the three-card set with four cards, update the materials, steps and checks together. Changing only the materials list leaves a contradiction for anyone following the remaining text literally.
Distinguish “the steps have been written” from “tested under the specified conditions”. A document may be linguistically complete while still awaiting practical testing. State that honestly; do not invent reviewers or trial results. Sensitive applications require a specialist procedure approved by the responsible organisation, not this general paper exercise.
References and the next step
The two linked references were read on 2 November 2026. The example, calculation, table and method for recording assistance were created for this article; the sources' examples and commands were not reproduced. Choose a small, non-sensitive procedure, write its outcome, starting point, steps and check, then state honestly what still needs testing before it can be relied upon.
