Writing Work Instructions People Actually Read

Why work instructions often go unread

In the binder next to the machine there is an instruction for setting it up, four pages long, last changed three years ago. The experienced colleague does not need it, the new one cannot find what he is looking for and would rather ask. Since the fixture was rebuilt, two steps are no longer correct. Nobody has updated them, because nobody reads the instruction anyway.

The result is a company in which knowledge is passed on orally and everyone works a little differently. That goes well until the experienced colleague is sick, a complaint comes in, or an audit is due. Then it turns out that the instruction exists but does not describe the work that is actually done.

This article answers the question: how does a company write work instructions that are actually read and followed? To do so, we first distinguish the work instruction from other documents, introduce a thinking model from safety research, examine why people deviate from instructions, and derive the structure, wording, and upkeep of a good instruction.

An instruction that describes the work as it was imagined gets bypassed by those who know how it is done.

What is a work instruction, and how does it differ from a process description?

A work instruction describes a single task that one person performs at one workstation, step by step and so concretely that someone with the necessary basic training can complete it afterward. Examples are setting up a machine, booking a return, or checking an incoming invoice.

It differs from the process description, which shows how a workflow runs across several people, who takes over what, and what result stands at the end. The article on one-page process documentation describes a page with eight fields for this. The work instruction is, in a sense, a close-up of a single step on that page. A checklist in turn is even shorter: it assumes that the person has mastered the task and only ensures that nothing is forgotten. The article on checklists in the company shows what good checklists look like.

The thinking model: work as imagined and work as done

The safety researcher Erik Hollnagel coined a pair of terms that is widely used in research on work procedures. Work as imagined is work as those who plan and describe it imagine it, usually at a distance from the workstation. Work as done is work as it is actually carried out, under time pressure, with whatever tool is at hand, and with the special cases nobody foresaw.

There is always a gap between the two, because nobody can foresee every circumstance when writing. An analogy makes this tangible: directions derived from a map name the shortest road. Someone who drives the route every day knows there is a construction site there in the morning and takes a different way. Neither is wrong. But a newcomer who follows the directions ends up in a traffic jam.

For work instructions this results in a clear task. A good instruction narrows the gap between imagined and actual work by being derived from actual work. And it has a channel through which new deviations are reported, so that the gap does not grow again.

Why people deviate from work instructions

Rajapakse and Emad (2025) studied this question in an industry where deviations have particularly serious consequences: shipping. In 61 in-depth interviews with seafarers of various nationalities and ranks, they found four interconnected reasons for deviating from work procedures: a negative attitude toward procedures, inadequate training, poorly prepared procedures, and the changing conditions on board. Procedures are usually written as a linear sequence of steps, while work on board often is not. Where the two do not fit, their analysis shows, mistrust of the procedures arises, followed either by circumvention or by compliance in appearance only.

The authors explicitly oppose the habit of attributing accidents too quickly to human error. As an example they cite the grounding of a ferry off Scotland in 2022, after which the investigation found, among other things, that the crew had deviated from several procedures, partly because they did not trust them sufficiently. Their recommendation: develop procedures together with those who carry them out, align training with reality, and understand safety management as a learning system. The study is qualitative and limited to one industry. The pattern, however, can be transferred to any workshop and any office.

A second finding fits with this. Hanahara (2026) compared two Japanese sales departments that wanted to standardize. One practiced a shared basic pattern in role-plays, the other distributed detailed procedures. Only in the first did the change last. The instruction alone thus rarely works. It works when it is demonstrated and practiced.

Two views: rules from above or rules from practice?

In a review of research on work rules, Hale and Borys (2013) distinguished two basic views. In the first, rules are written by experts above those doing the work, and deviations count as errors to be prevented through control and training. In the second, rules emerge from the experience of those doing the work, and deviations are also information about where the rule does not fit.

Both views have their justification. Where a mistake is dangerous or expensive, such as safety shutdowns or inspection steps, firm rules are needed from which nobody deviates. Where the work varies, a rigid rule gets bypassed as soon as it no longer matches reality. For a small company I consider a mix to be right: a few binding steps, clearly marked and justified, and for the rest an instruction that arises from practice and is corrected by practice.

How to write a work instruction that gets followed

1. Watch the work being done

   Have the person who performs the task most often show it to you. Note every move, including those they take for granted.

2. Record purpose and result

   Write in one sentence what the task is for and how you can tell it has been done correctly.

3. Formulate the steps

   One step is one action, starting with a verb in the imperative. At most ten steps. Anything beyond that is two tasks.

4. Mark critical steps

   Mark the steps from which no one may deviate and write in one sentence why.

5. Photos of the real workstation

   A photo of the actual fixture or screen often replaces a paragraph of text. No pictures from manuals that look different from the workstation.

6. Test with a new person

   Give the instruction to someone who does not know the task and watch without helping. Every hesitation reveals a gap.

How to keep work instructions up to date

An instruction goes out of date as soon as tools, software, or the workflow change. A simple feedback channel helps against this: anyone who deviates from the instruction because it no longer fits reports this in one sentence. The reports go to the instruction's owner, who decides monthly whether the instruction or the way of working is adjusted.

The value of such a register lies less in the individual reports than in the pattern. When deviations pile up at one step, it is rarely due to the people. The essay on errors as process signals describes why recurring mistakes usually go back to the workflow.

• Every instruction has an owner and a date of last review.
• Deviations can be reported in one sentence without any disadvantage.
• Critical steps are marked and justified.
• New colleagues have the instruction demonstrated to them, not just handed over.

Conclusion: what makes a work instruction readable and effective?

The guiding question was how a company writes work instructions that are read and followed. The answer has three parts. First, the instruction is derived from the actual work, not from an idea of it, and it is worded so concretely that a new person can use it without asking. Second, it separates a few binding, justified steps from the rest, which may change with practice. Third, it has a way back: deviations are reported and lead to a review of the instruction. Research shows that people bypass instructions above all when they do not match reality. A good instruction is therefore never finished but becomes more precise with every piece of feedback.

How to get started

1. Choose a task about which new colleagues ask most often.
2. Watch the most experienced person do it for 30 minutes and note every move.
3. Write at most ten steps, each with a verb, and take two photos of the real workstation.
4. Mark the steps from which no one may deviate and justify them in one sentence.
5. Have the instruction tested by someone who does not know the task, and decide how deviations will be reported.

The first instruction takes the longest. From the third one on, the team has a form it knows, and new instructions are written in an hour.