What Are the 18 Human Error Traps in Procedure Writing?

What are the 18 human error traps in procedure writing?

The 18 error traps are the specific, recurring situations in a written procedure that make a competent person more likely to make a mistake — not because the procedure is technically wrong, but because of how it's written. They are the human-performance failure modes that the industry's procedure writing standards, anchored in PPA AP-907-005, are specifically designed to eliminate. If you learn to see them, you can write against them; if you don't, they hide in plain sight in every procedure you produce.

The critical insight underneath all 18 is this: most procedure-related errors are not knowledge failures. The person knew the task. The procedure created the conditions for the error through ambiguity, poor structure, or missing information. That's why these are called traps — they catch skilled people.

The categories of error traps

The 18 error-likely situations cluster into a handful of recognizable families. Understanding the families makes the individual traps easier to internalize than memorizing a flat list.

Ambiguity traps — the procedure can be read more than one way. Vague action verbs ("check," "verify," "ensure" where a specific action is needed), unclear referents ("it," "they," "the valve" when several exist), and undefined terms all put the user in the position of guessing intent. Every guess is an error opportunity.

Structure traps — the information is present but arranged against how people work. Multiple actions buried in a single step, conditional logic ("if X, then Y") written as prose instead of clearly branched steps, and steps that require the user to hold too much in working memory at once. The content is right; the packaging causes the error.

Placement traps — the right information in the wrong place. The classic is a warning or caution that appears after the step it's meant to govern, so the user meets the hazard before the warning. Notes that interrupt an action sequence, or critical information in a location the user reaches too late, fall here too.

Level-of-detail traps — the guidance doesn't match the user. Too little detail pushes a less-experienced user into guessing (knowledge-based performance, where error rates are highest); too much detail buries the critical steps in noise and trains experienced users to stop reading carefully. Matching detail to the actual user population is a discipline, not an accident.

Identification traps — the procedure fails to flag what matters. Critical steps that look identical to routine steps, missing place-keeping aids, and no clear indication of which steps require independent verification all leave the user without the signals a high-consequence task demands.

Why they matter more than technical accuracy

Here is the counterintuitive part that surprises most organizations: when procedures fail in the field, they are usually technically correct. The steps are accurate. The error traps are what turn an accurate procedure into an unusable one.

Consider the human-performance data. When a procedure provides only high-level "what to do" guidance and forces the user into knowledge-based performance, error rates can run as high as 1 in 2 to 1 in 10. The same task, written to keep the user in rule-based performance (clear, followed steps), drops to 1 in 100 to 1 in 1,000 — and skill-based performance lower still. The error traps are precisely the writing choices that push users up into the high-error zone. Eliminating them is what moves a procedure from "accurate but risky" to "accurate and reliable."

How to write against the traps

You don't eliminate error traps by trying harder. You eliminate them by writing to a human-factored standard, consistently, and by reviewing against the traps deliberately:

• Use specific action verbs and define terms once, clearly.
• One action per step where the action matters; branch conditional logic explicitly.
• Place warnings and cautions before the steps they govern, every time.
• Match level of detail to the actual user, not to the writer's own expertise.
• Flag critical steps distinctly and build in the verification they require.
• Review against the traps as a checklist, not just for technical accuracy.

That last point is where certification and training pay off. A writer trained to recognize the 18 traps sees them in a draft the way a proofreader sees typos — automatically. A writer who hasn't been trained sees a technically correct procedure and misses the traps entirely, because nothing about them looks wrong on the surface.

The bottom line

The 18 error traps are the human-performance situations most likely to turn a technically correct procedure into one that fails in the field. They cluster into ambiguity, structure, placement, level-of-detail, and identification families, and they share one root: they create conditions where a skilled person makes a predictable mistake. Writing against them — consistently, to a human-factored standard — is the difference between procedures that pass a technical review and procedures people can actually follow when it counts.

Quick FAQ

What are the 18 error traps in procedure writing? They are the recurring human-performance situations in a written procedure most likely to cause a competent person to make an error — including vague action verbs, multiple actions per step, misplaced warnings, mismatched level of detail, and unflagged critical steps. They cluster into ambiguity, structure, placement, level-of-detail, and identification families, and are the situations human-factored writing standards (PPA AP-907-005) are designed to eliminate.

Why are they called error "traps"? Because they catch skilled, knowledgeable people. The errors they cause are not knowledge failures — the person knew the task — but conditions created by how the procedure was written. That's what makes them dangerous: nothing about a trap looks wrong on the surface.

How do you eliminate error traps? By writing to a human-factored standard consistently and reviewing against the traps deliberately — specific action verbs, one action per step, warnings before steps, level of detail matched to the user, and distinctly flagged critical steps. Training writers to recognize the traps is what makes the process reliable rather than accidental.