4 Myths About Fatigue Risk That Operations Managers Still Believe

Fatigue risk is the loss of reliable attention, judgment, reaction time, emotional regulation, and physical readiness when sleep, workload, shift design, recovery time, medication, commuting, or psychosocial pressure exceed what a person can safely sustain.

Many operations still treat fatigue as a private weakness. A tired worker is told to sleep better, drink less coffee, or show more discipline, while the schedule, overtime pattern, staffing gap, commuting burden, and supervisor pressure remain untouched. That approach may sound practical, but it leaves the risk exactly where it was created.

Across 25+ years in executive EHS roles and cultural transformation projects, Andreza Araujo has seen fatigue become dangerous when managers reduce it to attitude. The field usually shows the truth earlier: slower reactions, poorer hand placement, weaker pre-task checks, irritability, rushed shortcuts, and silence from people who no longer believe reporting will change the way work is planned.

Why these myths cost dearly

Fatigue myths cost dearly because they distort where leaders look for control. If fatigue is treated as laziness, the response becomes discipline. If it is treated only as a health promotion topic, the response becomes a wellness campaign. If it is treated as operational risk, managers must examine staffing, shift rotation, workload peaks, travel, recovery, supervision, and the authority to stop work when alertness is no longer credible.

NIOSH fatigue guidance and ISO 45003:2021 both point toward work design, workload, schedules, and organizational conditions, although many companies still keep fatigue outside the safety conversation. The gap matters for mental health at work because fatigue is not just sleepiness. It changes decision quality, emotional control, and the worker's ability to recognize a weak signal before it becomes an incident.

Myth 1: Fatigue is solved by telling people to sleep more

The first myth says workers already know what to do, so the company only needs to remind them to sleep more. The statement sounds reasonable because sleep is personal, and no manager can sleep on behalf of an employee. The problem is that personal responsibility does not explain a rotating shift pattern that cuts recovery, a maintenance shutdown that runs on extended hours, or a staffing model where overtime becomes the normal way to meet production.

When managers stop at sleep advice, they move the entire burden to the person with the least control over the system. The worker may be able to improve habits, but the operation controls start times, break timing, staffing levels, night work frequency, travel demands, callouts, and recovery windows. A fatigue program that ignores those decisions becomes moral commentary, not risk management.

In A Ilusao da Conformidade, glossed as The Illusion of Compliance, Andreza Araujo warns that formal evidence can look correct while the field remains exposed. A signed fatigue awareness form creates the same illusion. It proves the worker received information, but it does not prove the schedule allows recovery or that supervisors can slow work when alertness drops.

The stronger response is to review fatigue as a work-design exposure. Managers should map overtime, night work, consecutive shifts, commute burden after extended work, callout frequency, and tasks where reduced alertness can cause serious harm. Sleep advice can remain, but it belongs inside a control system whose first question is whether the operation is asking for a level of alertness that the current plan cannot support.

Myth 2: Coffee and motivation can compensate for unsafe schedules

The second myth is more dangerous because it feels operationally convenient. A team under pressure can be praised for resilience, given coffee, and asked to push through. Motivation may keep people present, but it does not restore reaction time, memory quality, emotional regulation, or the ability to notice a subtle change in equipment, traffic, chemical handling, or patient behavior.

That myth is common during turnarounds, emergency repairs, logistics peaks, audits, and seasonal production surges. The visible story is commitment. The hidden story is degradation. People make more assumptions, skip small verifications, accept poorer housekeeping, and tolerate irritability because everyone knows the schedule is tight. When fatigue becomes a badge of dedication, the operation loses the social permission to say the plan is no longer safe.

James Reason's work on organizational accidents helps explain the trap without blaming the operator. The fatigued decision is often the final visible layer, while the earlier layers sit in planning, staffing, supervision, maintenance timing, and leadership tolerance for work that depends on heroic endurance. If the same peak workload returns every month, calling it an exception is no longer credible.

Managers should set fatigue thresholds before the peak begins. A threshold can include maximum consecutive hours for safety-critical tasks, mandatory second checks after night work, supervisor review before driving after extended shifts, and a rule that critical work moves when alertness is questionable. These controls are not soft. They protect decision quality where motivation cannot.

Myth 3: Fatigue belongs to HR, not EHS

The third myth divides the problem by department. HR owns wellness, EHS owns incidents, operations owns staffing, and occupational health owns medical clearance. That division keeps each function busy, but fatigue crosses all of them. A tired worker may need health support, yet the risk can still originate in workload, overtime, job demands, shift design, or supervision.

HR usually sees absenteeism, turnover, conflict, and complaints. EHS sees near misses, poor hazard recognition, procedural drift, and injury precursors. Occupational health sees medication effects, sleep disorders, fit-for-work questions, and return-to-work limits. Operations sees staffing pressure. No single function has the full picture, which is why fatigue stays invisible when each team waits for another team to name it.

This is the point where mental health at work needs an integrated route. A fatigue concern may connect with occupational anxiety symptoms managers can miss, with workload conditions that appear in a workload risk plan, or with the practical choices in EAP, fit-for-work, and accommodation decisions. Treating those routes as separate silos weakens the response.

A better model gives fatigue a shared owner group. HR brings absence and psychosocial evidence. EHS brings task criticality and incident precursors. Occupational health brings medical and accommodation boundaries. Operations brings staffing and planning authority. The group should review fatigue signals monthly and immediately after serious near misses, because the question is not which department owns fatigue. The question is whether the current work system can safely demand the alertness it assumes.

Myth 4: If no one reports fatigue, the risk is under control

The fourth myth treats silence as evidence. If workers do not report fatigue, managers assume the schedule is acceptable. That assumption is weak because fatigue reporting often carries social cost. People fear being seen as fragile, unreliable, uncommitted, or difficult, especially in cultures where overtime is praised and refusal is interpreted as poor attitude.

Silence also appears when previous reports changed nothing. A worker who has reported exhaustion during peak workload and still received the same schedule learns quickly. The next time, the person may stay quiet, self-medicate with caffeine, swap shifts informally, drive home tired, or keep working while attention declines. The absence of reports can mean trust is low, not that fatigue is low.

Andreza Araujo's work in safety culture emphasizes that leaders must read weak signals before the injury record becomes the only evidence. In fatigue risk, weak signals include minor vehicle incidents, rising irritability, repeated procedural omissions, longer task completion time, more quality escapes, increased first-aid cases near the end of shifts, and supervisors who quietly normalize extended work because "everyone is tired anyway."

The response is to make fatigue visible without punishment. Use anonymous pulse checks during high-risk periods, supervisor prompts before safety-critical work, fit-for-duty conversations with clear privacy boundaries, and escalation rules for tasks that should not continue when alertness is impaired. Link the route to mental health return-to-work planning when recovery, medication, or accommodation affects capacity, but do not turn every fatigue concern into a medical case.

What managers should do now

Managers should start by naming fatigue as a safety and mental-health-at-work risk, then connect it to the decisions that create or reduce exposure. The first review should cover the last 90 days of overtime, night shifts, callouts, commuting after extended shifts, near misses, first-aid cases, quality escapes, and conflict reports. The goal is not to diagnose workers. The goal is to find where the work plan demands alertness without protecting recovery.

Build a short fatigue control standard for safety-critical tasks. It should define which tasks cannot proceed under impaired alertness, who can pause work, when a second check is mandatory, how supervisors document a fatigue concern, how HR and occupational health are involved, and how privacy is protected. The standard should also define what happens to the schedule after a fatigue signal appears, because a reporting route that does not change planning soon becomes symbolic.

The cultural test is simple, although not easy. If a supervisor can tell a worker to be careful but cannot change staffing, sequencing, break timing, or task assignment, fatigue control is still weak. In more than 250 cultural transformation projects supported by Andreza Araujo, the strongest progress appears when leaders stop treating human limits as excuses and start treating them as design constraints for serious work.