Technical skill does not cancel biology. Sleep loss reduces working memory, reaction time, and judgment. Treat fatigue as a condition to manage, not a character flaw to deny.
Five Principles to Use in the Field
- Use checklists when tired. Routine steps are exactly what fatigue causes people to skip. Short checklists protect isolation, measurements, force removal, and handover.
- Reduce task switching. Constant messages and parallel jobs increase cognitive load. During a critical fault, finish one diagnostic step before answering unrelated requests when possible.
- Say your reasoning aloud. A short verbal summary—”CPU is healthy, output is on, voltage is missing after relay K4″—can expose contradictions and keep teammates aligned.
- Use micro-recovery. A drink of water, food, fresh air, bright light, or a few minutes seated while waiting for a restart can restore attention better than grinding continuously.
- Recognize the stop point. If fatigue makes energized work or complex decisions unsafe, escalate or pause according to site procedures. Competence includes recognizing reduced capacity.
Pressure Mistakes to Avoid
- Working faster because you feel slower.
- Skipping documentation because you plan to remember later.
- Starting a second difficult job before the first machine is stable.
- Using excessive caffeine as a substitute for risk control or rest.
A Practical Breakdown Method
- Notice signs of cognitive drift: repeated checks, forgotten steps, irritability, tunnel vision.
- Externalize the plan in writing.
- Reduce interruptions and assign communication help.
- Use deliberate verification for safety-critical actions.
- Take brief recovery opportunities when the process allows.
- Escalate if fatigue is compromising safe judgment.
Scenario: After several hours on call, a technician realizes he has measured the same input three times and cannot remember the result. Instead of pushing harder, he writes a fault tree, asks a colleague to verify the isolation, drinks water, and resumes with a clear sequence. The issue is found in a failed interposing relay. The reset in method, not heroic speed, produces the result.
Train This Before the Next Callout
Choose one critical machine you know and apply the ideas from this chapter while it is healthy. For fatigue, attention, and night-shift decision making, write down the normal sequence, the key evidence you would want to preserve, and the first three checks you would make if the machine stopped. Then compare your plan with the electrical drawings, PLC diagnostics, maintenance history, and the experience of another technician. A ten-minute rehearsal in daylight can remove several minutes of confusion at night.
3 AM Rule: When tired, move more of your thinking out of your head and into checklists, notes, and verification.
Chapter Checklist
- Can I describe the symptom without naming an unproven cause?
- Have I preserved the evidence that could disappear after a reset or restart?
- Do I know which system boundary I am testing next and why?
- Have I kept safety controls and temporary changes visible and controlled?
- Can I explain my current facts, hypothesis, and next action in under thirty seconds?