Royal Army College

Lesson Overview

A safety system can be sound on paper, a thorough risk assessment, well-chosen controls, a clear safe system of work, and still fail, because between the system as designed and the safety actually delivered stands a person, and people get tired, distracted, complacent, overconfident, and pressured. This lesson is about that human element: the human factors that cause most accidents even where the system was good, and why understanding them is the difference between a safety officer who writes a sound plan and one who actually keeps people safe. The earlier lessons built the system; this lesson is about the people who run it, who are at once the system's greatest strength, able to notice and adapt to what no plan foresaw, and its greatest vulnerability, because they fail in predictable human ways.

The central truth is uncomfortable but liberating once grasped: most accidents are not failures of knowledge or of the system, but failures of human performance, and the commonest are entirely predictable. People are tired and miss things; people cut a corner once and then always; people grow complacent on a task that has been safe a hundred times; people press on under pressure when they should stop; people assume rather than check and communicate. None of this is unusual or blameworthy weakness; it is how human beings reliably behave, and a safety officer who knows it can design for it, watching for the human signs, building controls that survive tired and distracted people, and countering the pressures that defeat good intentions. The safety officer who ignores it builds a system for ideal people and is surprised when real ones have an accident.

This is the knowledge layer. It teaches you how fatigue and human factors cause accidents, why sound systems fail in performance, and how the safety officer designs and supervises for real human limits, so that you understand the human dimension that the rest of the course's method depends on. The judgement to read fatigue and complacency in a real team, and the authority to counter pressure in the moment, are built by performing the safety officer role in person under qualified supervision and signed off. Read this to understand why systems fail; learn to hold them up in practice.

By the end you will be able to explain why most accidents are human-factor failures rather than system failures, manage fatigue in training, recognise the common human factors including complacency and the normalisation of deviance, explain how pressure and poor communication defeat safety, and design and supervise so that a safe system survives real human limits.

Key Terms

Human factors: the ways human characteristics, fatigue, attention, complacency, overconfidence, pressure, and communication, affect performance and cause or prevent accidents.
Fatigue: tiredness that degrades judgement, attention, and reaction, with effects comparable to those of alcohol, and which the tired person tends to underestimate.
Complacency: the relaxation of care that comes from a task having been safe many times, leading to corners cut and signs missed on the very task that has lulled the person.
Normalisation of deviance: the process by which a cut corner, having caused no harm, becomes the accepted normal way, so that the unsafe gradually becomes routine.
Task fixation: the narrowing of attention onto a goal (finishing, succeeding) so that mounting danger and the case for stopping go unnoticed.
Pressure: the push, from time, from others, from the wish to succeed or not to be the one who stops, that drives people to continue when they should not.
Error-tolerant design: building a system so that a single human error does not cause harm, because errors are caught or cannot reach the danger, rather than relying on no one erring.
Latent condition: a weakness built into a system or situation that lies dormant until a human action triggers it into an accident.
Safety climate: the shared sense in a group of how much safety really matters, which decides whether people actually stop, speak up, and report (developed in Lesson 10).
The performed system: the safety system as it actually operates with real, fallible people, as opposed to the system as designed on paper.

Why most accidents are human-factor failures

When an accident is examined honestly, the cause is usually not that the people did not know the safe way, nor that the system on paper was wrong, but that, in the moment, a person did not do what they knew and the system required, because they were tired, distracted, complacent, rushed, or pressured. The knowledge was there; the system was there; the human performance failed. This is the consistent finding of accident investigation across every field, and it reframes the safety officer's job: writing a sound system is necessary but not sufficient, because the system is only as safe as its performance by fallible people, and the largest remaining risk, once the system is sound, is human.

This is not a counsel of despair about human unreliability; it is the key to preventing the accidents a good system alone does not. Because human failures are predictable, they can be designed against. We know people get tired, so we manage fatigue rather than assuming alertness. We know people grow complacent on routine tasks, so we guard the routine especially. We know people press on under pressure, so we build in thresholds and the authority to stop. We know people assume rather than check, so we require positive checks. The human factors are not random; they are a known list of ways people reliably fail, and a safety officer who knows the list can anticipate and counter each, which is exactly what distinguishes a system that works on paper from one that works in the field.

The deepest version of the point is that the human is both the weakest and the strongest part of the safety system. Weakest, because people fail in the ways this lesson describes; strongest, because a thinking person is the only part of the system that can notice the hazard no plan foresaw, sense that something is wrong, and stop. The safety officer's task is to reduce the human weaknesses, by managing fatigue, guarding against complacency, countering pressure, and to enable the human strength, by creating the conditions and climate in which people actually do notice, speak up, and stop. The rest of this lesson is the practical how of both.

Fatigue

Of all the human factors, fatigue is the most underrated and one of the most dangerous, because tiredness degrades exactly the faculties safety depends on, judgement, attention, reaction time, mood, and self-awareness, and does so in a person who usually does not realise how impaired they are. A seriously fatigued person performs, in attention and judgement, comparably to a person affected by alcohol, and would never be allowed to run a range or supervise a dangerous activity drunk, yet exhaustion is routinely tolerated and even worn as a badge of toughness. The tired safety officer misses the hazard; the tired instructor makes the error; the tired soldier on the range or in the water has the lapse. Military training, with its long days, broken sleep, and exertion, is a fatigue-generating activity, which makes managing fatigue a core safety duty, not an indulgence.

The safety officer manages fatigue by treating it as the real hazard it is. Plan for rest: build sleep and recovery into long activities rather than running people into the ground, especially those holding safety-critical roles like the RCO, the marshal, or the medical cover, who must be alert. Rotate people through demanding or critical tasks so no one holds an alertness-dependent role too long. Recognise the signs of dangerous fatigue, the missed step, the slowed reaction, the irritability, the microsleep, the loss of the thread, in others and, harder, in oneself, and act on them. And respect the limits: there is a point at which a tired person, however willing, is no longer safe to run or take part in a dangerous activity, and continuing past it trades safety for the appearance of endurance. The hard part is cultural: a force that admires pushing through exhaustion must learn that there are activities, the range, the water, the supervision of others, where a fatigued person is a danger, and where stopping to rest is the disciplined choice, not the weak one.

Complacency and the normalisation of deviance

Two linked human factors do much of the quiet damage in safety, and both grow from the same root: success breeds carelessness. Complacency is the relaxation of care that comes from a task having gone safely many times. The danger that was respected on the first range day, the first airsoft serial, the first cold-weather exercise, comes to feel routine after the hundredth, and the careful attention that kept it safe slackens, on the very task whose long safe record created the false comfort. Complacency is most dangerous precisely where it is most natural: on the familiar, oft-repeated activity, run by experienced people, where everyone "knows" it is safe. The safety officer guards the routine activity with particular care for this reason, because routine is where the discipline most quietly erodes.

Normalisation of deviance is complacency's more insidious form, the process by which a cut corner becomes the accepted normal. A control is skipped once under pressure, or a small rule bent, and no harm comes; so it is skipped again, and again, and the cut corner becomes "how we do it", the unsafe gradually redefined as normal, until the day the missing control would have mattered. The treacherous thing is that each step is small and is "proven" safe by the absence of harm, when in truth the activity has only been getting away with it, running closer and closer to the edge with the margin invisibly gone. The safety officer counters this by holding the controls as designed, treating a skipped control as a problem even when it caused no harm, and remembering the lesson of Lesson 01: an activity that endangered people and got away with it has not succeeded but been lucky, and luck is not a safety measure. The near miss and the harmless deviation are warnings, not reassurances.

   SUCCESS BREEDS CARELESSNESS

   COMPLACENCY              care relaxes because the task has been safe
                            many times; most dangerous on the FAMILIAR,
                            routine, "we know it's safe" activity
                            ......... guard the routine with particular care

   NORMALISATION OF         a corner cut once with no harm becomes cut
   DEVIANCE                 always; the unsafe gradually redefined as
                            "how we do it", margin invisibly gone
                            ......... each step "proven" safe by absence of harm,
                                      but the activity is only getting away with it

   THE GUARD: hold controls AS DESIGNED; treat a skipped control / near
   miss as a WARNING, not a reassurance. Lucky is not safe.

Pressure, communication, and task fixation

Several more human factors push people to act unsafely in the moment, and the safety officer must recognise and counter them. Pressure is the strongest: the push of time ("we're behind, press on"), of others (a senior wanting the serial finished, peers not wanting to be the one who stops), and of the wish to succeed or not to disappoint. Pressure drives people to skip controls, continue past thresholds, and silence their own doubts, and it is strongest exactly when stopping is most needed, when things are going wrong and time is short. The safety officer's role is partly to be the counterweight to this pressure, to hold the threshold and the stop against the push to continue, and to make it clear that stopping for safety is always right and always backed, so that no one, including the safety officer, has to choose between safety and not being the one who halted things.

Task fixation is the narrowing of attention onto a goal, finishing the exercise, completing the crossing, winning the engagement, so that the mounting danger and the growing case for stopping simply go unnoticed; the fixated person is not ignoring the warning signs but genuinely not seeing them, their attention captured by the task. The un-immersed marshal of the last lesson, and the safety officer standing outside the activity, exist partly to hold the wider view that the fixated participant has lost. Communication failures complete the list: the unclear brief, the assumption that someone else has done the check or will catch the problem, the doubt left unspoken because it seemed not one's place, the two people each thinking the other had it. Many accidents turn on a piece of safety information that someone had and someone else needed, and that did not cross the gap. The safety officer counters this with clear, confirmed communication, positive checks rather than assumptions, and a climate in which the unspoken doubt gets spoken, which is the safety climate of Lesson 10.

Why safe systems fail, and designing for real people

Pulling it together: a safe system fails when the gap between the system as designed and the system as performed by real, fallible people is wide enough for an accident to fall through. The risk assessment was sound, but a tired person missed a step; the controls were right, but complacency let one slide; the threshold was set, but pressure pushed past it; the brief was given, but an assumption replaced a check. The system did not fail on paper; it failed in the hands of human beings behaving in the predictable human ways this lesson has named. Often a dormant latent condition, a weakness already built into the situation, waits until a human action triggers it, and the accident is the meeting of the two.

The answer is to design and supervise for real people, not ideal ones, and it runs through everything this course has taught. Build error-tolerant systems, so that a single human error is caught or cannot reach the danger, rather than relying on no one ever erring: the positive check that catches the live round, the eye protection that guards the forgotten danger, the backstop that stops the unsafe shot, the second person who confirms. Use the human strengths against the human weaknesses: marshals and safety officers outside the activity to hold the view the immersed and fixated lose, checklists to carry what tired memory drops, the stop anyone may call to catch what one person misses. Manage the human state: fatigue, complacency, and pressure handled as the hazards they are. And build the climate in which people actually stop, speak up, and report, because the best-designed system still depends on a person being willing to halt it, which is the subject of the final lesson. The safety officer who designs for the real human, fallible, fixated, fatigued, pressured, but also thinking, noticing, and able to stop, builds a system that survives contact with people, which is the only kind that keeps anyone safe.

In Practice: The Accident That Almost Was

A sergeant of the Royal Army College reviews a near miss from a recent exercise, and it is a textbook of this lesson. On paper, the activity had been safe: a sound risk assessment, the right controls, a clear safe system. Yet it had come within a moment of a serious accident, and not one part of the written system had been wrong. A weak analysis would blame the individual who nearly erred; the College's sergeant reads the human factors instead.

She finds a chain of predictable human failures, not a system fault. The activity was the familiar, oft-run kind, and complacency had crept in, the careful checks of the first iterations now done by habit and half-attention. A control had quietly been skipped on the last few runs without harm, the normalisation of deviance, so that the margin was already thinner than anyone realised. The team was deep into a long day and genuinely fatigued, judgement and attention dulled though no one felt unsafe. They were behind time and under pressure to finish, which pushed them to continue when a pause was due. And the person best placed to catch the problem was fixated on completing the task and did not see the warning, while a doubt another had felt went unspoken, a communication gap. The near miss was the meeting of all of these with a latent weakness in the ground, and it was caught only because one un-fixated person, standing back, saw it and called the stop.

Her conclusions are about the performed system, not the paper one. She does not add a rule to a system that was already sound; she addresses the human factors: managing fatigue on long serials, guarding the familiar activity against complacency, treating the skipped control as the warning it was, countering the pressure to finish, and strengthening the climate so the unspoken doubt gets spoken and the stop comes faster. She records it, by the discipline of Lesson 10, as the free lesson a near miss is. The accident did not happen, this time, because the human strength, one person noticing and stopping, caught what the human weaknesses had set up. The sergeant's job is to make that catch reliable, by designing and leading for the real people who run the system, which is the whole of this lesson.

Check Your Understanding

Explain why most accidents are human-factor failures rather than failures of knowledge or of the system, and why this is "liberating once grasped." In what sense is the human both the weakest and the strongest part of a safety system?
Describe how the safety officer manages fatigue (why it is so dangerous and underrated, and the controls of rest, rotation, recognition, and respecting limits). Then explain complacency and the normalisation of deviance, why they are most dangerous on familiar activities, and how they are guarded against.
Explain how pressure, task fixation, and communication failures defeat safety in the moment, and how the safety officer counters each. Then explain why safe systems fail (the gap between designed and performed) and what it means to design error-tolerant systems for real people.

Reflection (write a short paragraph): This lesson argues that human failures, fatigue, complacency, pressure, fixation, are predictable, not random, and so can be designed against. Think honestly about which of these you are most prone to: do you push on when tired, grow careless on the familiar, bend to pressure to finish, or fixate on a goal and miss the wider picture? Recall an occasion when one of them nearly caught you out. Knowing that the system you run will be performed by people exactly as fallible as you, what would you build into it, a check, a rotation, a threshold, a stop, so that a single human lapse, yours or another's, cannot reach the danger?

Summary

Most accidents are human-factor failures, not failures of knowledge or of the system: in the moment a person did not do what they knew and the system required, because they were tired, distracted, complacent, rushed, or pressured. A sound system is necessary but not sufficient; the largest remaining risk is human, and predictable, so it can be designed against.
The human is both the weakest part of the system (failing in predictable ways) and the strongest (the only part that can notice the unforeseen hazard and stop). The safety officer reduces the weaknesses and enables the strength.
Fatigue is the most underrated human factor, degrading judgement and attention like alcohol in a person who underestimates their own impairment. Manage it as a real hazard: plan rest (especially for safety-critical roles), rotate demanding tasks, recognise the signs, and respect the limit past which a tired person is unsafe, against the culture that admires pushing through.
Complacency (care relaxing because a task has long been safe) and the normalisation of deviance (a cut corner with no harm becoming the norm) are most dangerous on familiar, routine activities. Guard the routine especially; hold controls as designed; treat a skipped control or near miss as a warning, because lucky is not safe.
Pressure (time, others, the wish not to be the one who stops), task fixation (attention narrowed onto the goal so danger goes unseen), and communication failures (assumptions, unspoken doubts, information that does not cross the gap) defeat safety in the moment. The safety officer is the counterweight: hold the threshold and stop, keep the outside view, require positive checks, and get the doubt spoken.
Safe systems fail in the gap between the system as designed and as performed by fallible people, often triggering a latent condition. Design for real people: build error-tolerant systems where one error cannot reach the danger, use human strengths (marshals, checklists, the stop) against human weaknesses, manage the human state, and build the climate where people actually stop and speak up.
This is the knowledge layer; reading fatigue and complacency in a real team and countering pressure in the moment are built by performing the safety officer role under qualified supervision and signed off. This lesson deepens the supervision of Lesson 05, underlies the discipline of Lessons 06 to 08, draws on the leadership of LDR 420 and LDR 301, and leads directly into the recording, review, and safety climate of Lesson 10.

Fatigue, Human Factors, and Why Safe Systems Fail