
What You’ll Learn
- What a human performance warning flag is — a weakness that predicts error long before an incident names it
- The two program-level flags: over-relying on risk processes, and processes so cumbersome they invite workarounds
- The organizational flags, from groupthink and deference to experts to high-risk activities with no clear owner
- The supervisory flags, including supervision that is physically or mentally separated from the job site
- The worker flags — self-imposed production pressure, risky snap judgments, and problem reporting that is not transparent
- Why “past success” appears at nearly every level, and why it may be the most dangerous flag of all
Weaknesses That Announce Themselves
Incidents rarely arrive unannounced. Long before the event, the weaknesses that will contribute to it are usually visible — in how the program is built, how the organization thinks, how supervision shows up, and how workers behave under pressure. Annex Q calls these human performance warning flags: common process, organizational, supervisory, and worker performance weaknesses that signal elevated risk. Two things about the flags matter. First, they are meant to be identified by the organization itself, in calm times, not catalogued by investigators afterward. Second, finding one is not the end of the work — action should be taken to address the root cause. A flag is not a prediction of a specific accident; it is a statement that the defenses are thinner than they look.
Program and Process Flags: When the System Itself Is the Problem
The program or process flags sit at the top of the system, in the risk management machinery itself. The first is over-reliance: risk management processes are leaned on instead of personal ownership and accountability for managing risk. When the process becomes the owner, nobody is — the form gets completed, the box gets checked, and the actual judgment about whether this task is safe today quietly belongs to no one. The second flag is the opposite failure with the same result: risk management processes that are inefficient or cumbersome. The annex adds a dry warning — “more” is often not better. A process heavy enough to fight will be fought: shortened, pencil-whipped, or routed around, and the organization ends up with the appearance of control and the reality of a workaround culture.
Organizational Flags: How the Whole Company Thinks
The organizational flags describe the habits of the institution. Personnel tend to engage in consensus or group thinking — groupthink — without encouraging counterview points, so the first plausible plan in the room becomes the only plan ever examined. Personnel overly defer to managers and perceived experts, which silences exactly the people closest to the work when they see what the expert missed. Activities with high risk are not assigned clear owners, leaving the most dangerous work in the building with no named person accountable for how it is controlled. The organization assumes its risk management is healthy simply because a program or process was established — complacency dressed as assurance, where the existence of the binder substitutes for evidence that the binder works. And woven through this level is the flag that recurs at every level below it: past success without adverse outcomes becomes the basis for continuing current practices, as if a run of good luck were a measurement of good control.
Supervisory Flags: Distance, Bottlenecks, and Borrowed Confidence
The supervisory flags describe the layer that connects the organization to the work. Delegation is lacking, with a few individuals relied on to make major decisions — a bottleneck that both overloads those individuals and leaves everyone else practiced in not deciding. Supervision is physically or mentally separated from the job site and insufficiently aware of current conditions and attitudes: the supervisor approving the work cannot picture the actual equipment, the actual crew, or the actual pressures in the field that day. Personnel do not understand how risk is perceived and managed at the worker level, so the gap between the plan’s assumptions and the crew’s reality goes unnoticed. Past success without adverse outcomes again becomes the basis for continuing current practices. And performance indicators are used to justify existing risk management strategies — the numbers are read as proof the strategy is right, rather than as a prompt to ask whether the strategy is still the right one.
Worker Flags: Pressure, Pride, and Silence
The worker flags are the ones closest to the point of work. Individuals or groups exhibit self-imposed production pressure — nobody ordered the rush, but the crew rushes anyway, to finish, to look efficient, to not be the delay. Work activities are considered routine, which drains the attention that unfamiliar work would automatically command. Individuals are quick to make risky judgments without taking the time to fully understand the situation. Personnel take pride in their ability to work through or with levels of risk that could have been mitigated or eliminated — skill at surviving hazards becomes a badge, instead of a sign the hazards were left in place too long. Risk is not communicated effectively up the company: individuals assume the next level of supervision already knows or understands the risk involved, or that there are insufficient resources to manage it, so nothing is said. And problem reporting is not transparent — individuals are not willing to report high-risk conditions, so the organization’s picture of its own risk is systematically rosier than the truth. Past success, once again, is on the list: it becomes the basis for continuing current practices at the level of the individual crew.
The Flag That Appears Everywhere: Past Success
One flag repeats so insistently that it deserves its own reading. Past success — a history of getting away with it — appears among the organizational flags, the supervisory flags, and the worker flags alike. That repetition is the point. At every level of a company, a clean record is the easiest evidence to reach for and the weakest evidence there is: it cannot distinguish between a practice that is genuinely safe and a practice whose failure simply has not come due. Each uneventful repetition quietly raises the crew’s confidence and lowers its guard, until the day the same practice meets the one condition it could not survive. When an organization hears “we’ve always done it this way and nothing has happened” offered as a safety argument — in a planning meeting, in a supervisor’s approval, or on the tools — Annex Q’s flag lists say to hear it as what it is: a warning.
Worked Scenario
A utility contractor reviews its flag picture during a safety stand-down, honestly. At program level, its risk assessment process has grown to eleven pages for routine switching — and field crews privately admit they complete most of it after the work. At organizational level, planning meetings rarely hear a dissenting voice; the senior engineer speaks first and the room agrees, and the company’s energized-work tasks have no single named owner — “operations” owns them, which means no one does. The supervisors’ own review stings: two of them approve job plans from an office forty minutes from the substations and have not walked the main yard in months, and both cite last year’s zero-incident record when questioned about a shortcut that has become normal. The workers, given an anonymous channel, name the rest themselves: crews race the clock they set for themselves, breaker operations are “just routine,” and two high-risk conditions found last quarter were never reported upward because the crews assumed supervision already knew. Nobody in the room can claim the flags were hidden — every one of them was visible before the stand-down. The value of the list is that it gave the company a vocabulary for what it was already seeing, and a starting set of root causes to fix: simplify the process, name owners, get supervision back to the field, and make reporting safe and expected.
Common Mistakes and Safety Notes
- Waiting for an incident to identify the flags. The flags exist to be found by the organization in advance — after an event, the same list becomes an investigation finding.
- Treating a found flag as a paperwork exercise. Identification is only the start; action should be taken to address the root cause.
- Believing a long process equals a strong process. Cumbersome, inefficient risk processes are themselves a flag — “more” is often not better, and heavy processes breed workarounds.
- Letting the expert speak last — and only. Deference to managers and perceived experts, and groupthink without counterview points, silence the people who see the hazard first.
- Owning high-risk work collectively. “The department” is not an owner. High-risk activities without a clear, named owner are a flag.
- Reading a clean record as proof of safety. Past success without adverse outcomes is a flag at the organizational, supervisory, and worker levels — not a defense of current practice.
- Assuming silence means safety. Non-transparent problem reporting and risk that never travels up the company mean the organization’s risk picture is wrong in the comfortable direction.
Summary
Annex Q’s warning flags name the performance weaknesses that precede incidents, at four levels. Program and process flags: risk processes over-relied on in place of personal ownership and accountability, and processes so inefficient or cumbersome that they invite workarounds. Organizational flags: groupthink without counterview points, excessive deference to managers and perceived experts, high-risk activities with no clear owner, and complacency that a program’s existence proves its health. Supervisory flags: missing delegation and decision bottlenecks, supervision separated from the job site and unaware of real conditions, no understanding of how risk is managed at the worker level, and performance indicators used to justify existing strategies. Worker flags: self-imposed production pressure, work treated as routine, hasty risky judgments, pride in working through avoidable risk, risk not communicated upward, and non-transparent problem reporting. Running through three of the four levels is past success without adverse outcomes used to justify continuing current practices — the flag that turns a lucky history into a future incident. The flags are there to be identified by the organization, with action taken against their root causes.
Quick-Check Questions
1. What should an organization do when it identifies a human performance warning flag?
Answer: Take action to address the root cause of the weakness the flag reveals.
2. What are the two program or process warning flags?
Answer: Risk management processes are over-relied on instead of personal ownership and accountability for managing risk; and risk management processes are inefficient or cumbersome.
3. Name three organizational warning flags.
Answer: Any three of: consensus/group thinking without encouraging counterview points; personnel overly deferring to managers and perceived experts; high-risk activities not assigned clear owners; past success becoming the basis for continuing current practices; assuming risk management is healthy because a program was established.
4. A supervisor approves field work from a distant office and rarely visits the site. Which flag is that?
Answer: Supervision physically or mentally separated from the job site, insufficiently aware of current conditions and attitudes.
5. Which flag appears at the organizational, supervisory, AND worker levels?
Answer: Past success without adverse outcomes becoming the basis for continuing current practices.
Based on NFPA 70E (2024), Informative Annex Q, paraphrased for study.
Video lesson for this module is in production — coming soon.
Quiz for this module is being prepared.
Flashcards for this module are being prepared.



