How to Write Instructions Someone Else Can Actually Follow

“Put the files in the right folder and send them over” may sound obvious to the person who wrote it. The reader still has to guess which files, which folder, what format and what counts as finished.

The useful habit: write for someone who cannot see the assumptions in your head.

Define the result before the steps

Begin with the task and its completed state. For a fictional team handover, the result might be: “Create a PDF of the approved report and place it in the shared review folder. Do not email it externally.”

This gives the reader a destination and a boundary. A procedure is easier to follow when the reader knows what it is meant to achieve.

State the starting conditions

List the access, materials and information needed before beginning. Mention the relevant software version or physical setup when it changes the procedure. Put an important warning before the action that could cause harm, not beneath it.

For the report example, the reader needs the approved source file, access to the review folder and the naming convention. Missing access is not something better phrasing inside step five will fix.

Use actions the reader can recognise

Vague wording More useful wording
Handle the document Open the approved report file
Save it correctly Export a PDF using the agreed filename
Put it there Upload the PDF to the shared review folder
Check everything Open the uploaded PDF and confirm every page is readable

Use the real labels people will see. If the interface says “Export,” do not call it “Publish” unless that is genuinely a different action. Prefer input-neutral verbs such as “select” when instructions should work with a mouse, keyboard or touch input.

Keep the sequence visible

Use numbered steps when order matters. Keep each step focused on one main action, with a short expected result where useful. Split a long procedure into meaningful stages rather than turning it into a wall of tiny numbered fragments.

Microsoft’s writing guidance recommends consistent phrasing and numbered procedures without overwhelming the reader. The aim is not to reach a magic number of steps; it is to make the next action easy to find.

A worked handover example

Task: prepare the approved report for internal review.

  1. Open the approved source file identified in the handover note.
  2. Export a PDF with the filename format specified in that note.
  3. Open the PDF and confirm the title, page count and tables match the approved source.
  4. Upload the checked PDF to the named shared review folder.
  5. Open the uploaded copy to confirm it is readable, then record its link in the internal task.

This fictional procedure deliberately leaves actual filenames and folder locations to a handover note. In a real instruction, those references must be concrete and accessible. A placeholder is not a finished instruction.

Include the exception path

Tell the reader what to do when a required condition is missing. “If the approved file is unavailable, stop and contact the document owner” prevents someone from quietly substituting an old draft.

Do not encourage guesses around destructive, safety-critical or externally visible actions. Link to the authoritative procedure where specialist steps are required.

Test with a fresh reader

Ask someone unfamiliar with the task to follow the instructions in a safe setting. Observe where they hesitate, search or ask a question. Avoid explaining every unclear step aloud; those explanations identify material the document may need.

Record whether the final result matches the stated goal. A person saying “that seems clear” is weaker evidence than actually completing the task without hidden assistance.

Keep instructions maintainable

Name an owner and review date for recurring procedures. Update screenshots and labels when the system changes. Remove obsolete copies or clearly identify the current version so readers are not forced to choose between conflicting documents.

Note to keep: good instructions transfer enough context for a person to act and enough feedback for them to know whether they succeeded.

Related: investigate repeating problems and place approval before consequential actions.

Sources

Latest

How to Make a Decision When Important Information Is Missing

Waiting for complete information can become a decision of...

Why Every Process Needs a Way to Catch Mistakes

A careful person can still attach the wrong file,...

How to Run a Small Experiment Before Making a Big Change

A new system can look convincing in a meeting...

Why a Lower Monthly Payment Can Still Cost More Overall

A monthly payment answers one important question: what must...

Newsletter

spot_img

Don't miss

How to Make a Decision When Important Information Is Missing

Waiting for complete information can become a decision of...

Why Every Process Needs a Way to Catch Mistakes

A careful person can still attach the wrong file,...

How to Run a Small Experiment Before Making a Big Change

A new system can look convincing in a meeting...

Why a Lower Monthly Payment Can Still Cost More Overall

A monthly payment answers one important question: what must...

How to Compare Prices Using the Same Unit

The smaller pack costs less at the checkout. The...

How to Make a Decision When Important Information Is Missing

Waiting for complete information can become a decision of its own. Deadlines pass, options disappear and the cost of delay grows. Acting immediately can...

Why Every Process Needs a Way to Catch Mistakes

A careful person can still attach the wrong file, miss a field or send a package to the wrong destination. A dependable process assumes...

How to Run a Small Experiment Before Making a Big Change

A new system can look convincing in a meeting and become awkward in daily use. A small experiment gives you a way to learn...