Use safety, production, quality, and consequence to choose work rationally.
Figure: Days 61–68: Prioritization When Everything Is “Urgent” — a practical way to think about the system.
What to understand
Maintenance demand will always exceed immediate capacity somewhere. Priority should reflect consequence, not volume of complaints or who speaks the loudest.
Start by turning the idea into an observable question. What should the machine, component, person, or process be doing at this moment, and what evidence would prove that it is doing it? Defining normal first gives your troubleshooting a reference point and prevents you from reacting to the first unusual thing you notice.
How to apply it
Safety and environmental risk come first. Then consider production loss, quality risk, cascading damage, redundancy, and whether a degraded machine can run safely until a planned window.
Apply the idea one boundary at a time. Confirm one condition, record what you learned, and only then move to the next point in the chain. This makes your work easier to explain and greatly reduces the temptation to swap parts or change several variables at once.
What good work looks like
Communicate the queue. People accept delay more easily when they understand what is being handled first and why.
Good maintenance work leaves a trail of evidence. Measurements, alarm times, verified states, photos where permitted, and clear work-order notes let another technician understand why you made the repair and whether the same failure mechanism returns later.
Field scenario
Two calls arrive together: a conveyor has stopped in a non-bottleneck area with a buffer, and another machine is running but a guard latch is damaged. The guard issue has the higher safety consequence even though production has not yet stopped. Prioritization is about risk, not only downtime minutes.
After the immediate repair, capture the point in the sequence where the expected condition was lost and what evidence proved the cause. That small discipline turns a one-time fix into knowledge the whole maintenance team can reuse.
Field checklist
Common mistakes to avoid
Prioritizing whoever calls most often
Working FIFO when consequences differ greatly
Leaving a dangerous degraded condition because the line still runs
Failing to communicate why a job is waiting
Ask yourself: If this machine failed again on the next shift, what information could I leave behind that would make the next diagnosis faster and safer?
90-day action
Before moving on, choose one task from this chapter and perform it during normal work. Record what you learned in your plant notebook. The value of the first 90 days comes from turning concepts into repeatable behavior, not from reading alone.
CHAPTER 27