A lone technician needs a priority system that is simple enough for production to understand and strong enough to resist whoever shouts the loudest. Priority is a business decision expressed through technical risk.
Start with consequence, not emotion
People naturally describe their own problem as urgent. A good system asks what happens if the job waits: injury risk, environmental release, full production stop, lost quality, secondary damage, or only inconvenience.
The point is not extra administration; it is reducing the next uncertainty: Use four priority levels and define them in plain language. Avoid ten-level systems that create arguments about the difference between level six and seven.
A broken guard interlock is not ‘just five minutes’ because the machine can still be physically operated. Safety consequence keeps it at the top.
If a request involving start with consequence, not emotion interrupts planned work, leave a breadcrumb before walking away. Note the exact step completed, the isolation state, removed parts, readings, and the next action. Returning to half-finished technical work is far safer when you do not have to reconstruct your own thinking.
Add deterioration to the decision
Some faults are not stopping production yet but are moving quickly toward failure. A hot bearing, leaking seal, intermittent contactor, or cooling fan alarm may deserve action before a smaller current stop.
A reliable one-person routine turns this into a standard rather than a judgment call: Ask, ‘What is the cost of waiting one shift?’ This question captures secondary damage and likelihood of escalation.
Replacing a noisy €40 fan during a controlled stop can be more valuable than waiting until a €4,000 drive trips from heat.
Use add deterioration to the decision to make the next shutdown more productive. Jobs that require access, parts, contractors, or long isolation should be prepared in advance with scope, materials, drawings, permits, and acceptance criteria. A lone technician cannot afford to spend rare downtime searching for basic information.
Make the queue visible
When priorities exist only in your head, people assume you forgot them. Visibility reduces repeated interruptions and turns prioritization into a shared operational picture.
The fastest way to make this useful is to attach it to the work itself: Use a whiteboard, digital list, CMMS queue, or shared sheet showing priority, status, blocker, and next action.
Production may accept a delayed sensor repair much more easily when they can see you are currently restoring the only boiler feed pump.
The maintenance value of make the queue visible increases when you can trend it. Even simple counts – repeats per month, hours waiting for parts, missed PMs, callouts, or downtime minutes – reveal whether the plant is improving. Trend direction is often more persuasive than one dramatic event.
Practical application
Take one recent maintenance event that relates to build a priority system production can understand. Reconstruct what you knew at the beginning, before resets, part changes, or production explanations influenced the diagnosis. Then review the event through three lenses from this chapter: start with consequence, not emotion, add deterioration to the decision, and make the queue visible. Write down where your real response matched the method and where it depended on memory, urgency, or luck.
Use the examples as prompts rather than scripts. For start with consequence, not emotion, the chapter showed: A broken guard interlock is not ‘just five minutes’ because the machine can still be physically operated. Safety consequence keeps it at the top. For add deterioration to the decision, it showed: Replacing a noisy €40 fan during a controlled stop can be more valuable than waiting until a €4,000 drive trips from heat. Decide on one practical change you can make before the same type of event returns – a measurement point, spare, label, note, backup, callout rule, PM task, or escalation contact.
Chapter action checklist
☐ Identify one current weakness related to build a
priority system production can understand.
☐ Choose one change that can be implemented without new
software or budget.
☐ Decide what evidence should be recorded the next time this
situation occurs.
☐ Identify the point where you would stop and escalate rather
than continue alone.
☐ Add any resulting repair, documentation, spare, training, or
management action to the visible backlog.