Key Takeaways

  • Fatigue can impair sustained attention, monitoring and response speed, but subjective tiredness and objectively measured performance do not always change together.

  • NASA flight-simulator research found that brief breaks improved some physiological and subjective sleepiness measures without demonstrating an improvement in objective vigilance performance during the measured period.

  • For managers, visible alertness or an employee's reassurance that they feel fine should not be treated as a complete assessment of fatigue-related risk. The implications below are organizational interpretation, not a clinical diagnostic protocol.

Someone can appear engaged, answer questions clearly and continue working while their ability to notice an unexpected signal is deteriorating. Fatigue is often discussed as if it were a feeling that employees can simply report accurately. Yet human-performance research distinguishes subjective sleepiness, physiological indicators and performance on specific tasks. These measures can move together, but they are not identical. That difference matters most in work where the critical demand is not constant activity but noticing something unusual at the right moment.

Does feeling alert mean someone is performing well?

No. Feeling alert is useful information, but it does not prove that attention, response speed or error detection are unaffected. NASA's Fatigue Countermeasures Laboratory describes how circadian misalignment, acute and chronic sleep loss, and sleep inertia affect alertness and performance. The laboratory studies these factors with multiple measures, including psychomotor vigilance tests and subjective questionnaires, rather than treating a single self-rating as definitive.

This does not mean that subjective reports are worthless. People often recognize that they are sleepy, and reports may provide essential information that a manager otherwise lacks. The narrower point is that a self-report is one signal among several. It cannot reveal every lapse that might occur during a long period of monitoring or every change in the ability to respond to an unexpected event.

What did NASA's flight-simulator study find?

A 2002 randomized study by Neri and colleagues investigated brief breaks during a simulated overnight flight. The experiment involved fourteen two-person crews, divided between a condition with five short breaks during cruise and a comparison condition with one break. Researchers collected electroencephalographic and eye-movement measurements, subjective sleepiness reports and vigilance-task results (Neri et al., 2002).

In the latter part of the night, the multiple-break condition showed reductions in selected physiological signs of sleepiness for roughly 15 minutes after a break, and participants reported improved alertness for up to 25 minutes. Crucially, the researchers did not find evidence of improved objective vigilance performance in the measured 15–25-minute interval. Their conclusion was qualified: short breaks might help manage sleepiness, but feeling more alert did not automatically translate into a demonstrated performance improvement on that measure.

This is one controlled simulator study with a limited sample, not proof that breaks are ineffective or that people always misjudge their fatigue. Its value is conceptual. It shows why an intervention can improve how someone feels, or one physiological measure, without improving every operationally relevant outcome.

Why is monitoring particularly vulnerable to fatigue?

Monitoring tasks can demand long periods of attention with relatively few important events. The difficulty is not necessarily doing something complicated every second. It is remaining capable of detecting the rare signal that changes what needs to happen. NASA's 2021 account of a study of partially automated driving reports that a passive supervisory role exposed latent sleepiness relative to manual driving under the research conditions. The associated study examined sleepiness, unintended sleep transitions, reaction time and attention failures; it was not a field experiment on corporate managers.

That distinction is relevant when organizations assume that automating routine work always reduces human workload. Automation may reduce manual effort while leaving people responsible for noticing the exception. A quieter task can be easier in one respect and more demanding in another. The effect depends on the task, the degree of automation and the person’s sleep and circadian conditions.

How do fatigue and sleepiness differ?

In everyday speech, the words overlap. In research and operational safety, sleepiness often refers to the propensity to fall asleep, while fatigue can describe a broader reduction in capacity associated with sustained effort, sleep loss, circadian factors or other demands. They are related, not interchangeable, and different studies use different operational definitions. NASA's laboratory work explicitly examines sleep restriction, circadian misalignment and sleep inertia as distinct contributors to human performance (NASA Fatigue Countermeasures Laboratory).

For organizational discussion, precision matters. An employee who says they are exhausted may be describing insufficient sleep, heavy cognitive demands, emotional strain, illness or several factors together. A manager cannot infer the cause or an individual's fitness for a safety-critical duty from that phrase alone. Where regulated fitness-for-duty standards apply, those standards and qualified occupational assessment take precedence over a general leadership article.

What can leaders infer from apparently normal performance?

Only that the observed tasks were performed as observed. A person may complete routine work while having more difficulty with an unexpected event, and the absence of a visible error does not establish that vigilance is unaffected. The 2002 simulator study demonstrates why performance should not be inferred from subjective improvement alone. NASA's broader research also shows that fatigue effects vary with sleep history, biological timing and the kind of task being measured.

Imagine a hypothetical operations team finishing a routine shift with no recorded errors. That outcome is encouraging, but it cannot tell the manager how much attention was required to maintain it, how close the team was to missing an unusual signal, or how the next shift would perform after insufficient rest. These are questions about limits of inference, not a claim that the team is unsafe.

Why is fatigue an organizational issue rather than just a personal one?

Employees have responsibilities concerning rest and fitness for duty, but their opportunities to rest and the cognitive demands of work are also shaped by schedules, staffing, task design and operational expectations. The NASA laboratory explicitly studies both acute sleep deprivation and repeated sleep restriction because these exposures affect performance. A workplace that treats fatigue exclusively as a motivation problem can overlook predictable constraints imposed by how work is organized.

AeroLeadership's interpretation is that fatigue makes the gap between visible completion and remaining capability especially important. Managers see tasks completed; they cannot directly see the cognitive reserve required to handle a surprise. This connects with the broader concern in operational slack: the capacity to respond to unexpected demands is not necessarily visible in routine output.

The implication is not to distrust employees or replace their judgment with surveillance. It is to avoid using a single reassuring signal—appearance, self-rating or a successful routine task—as proof that all relevant performance capacities are intact. The AeroLeadership Framework places human limits alongside communication, situational awareness and organizational reliability. The program explores their integration; this article addresses the narrower evidence question of what feeling alert can, and cannot, tell us.

Sources and further reading