Understand who knows what, who owns decisions, and how to ask for help without becoming dependent.
What to understand
The operator often knows what “normal” looks and sounds like. The senior technician knows recurring failure patterns. Production knows urgency. Engineering may know the design intent. Stores knows what parts really exist.
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
Good maintenance communication is specific. Replace “it is broken” with the observed symptom, what changed, what was measured, and what you need from the other person.
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
Build trust by closing loops. If someone gives you useful information, return later and tell them what the fault actually was.
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
You are called to a packaging machine that intermittently rejects good product. The operator says it started after the last format change. Instead of dismissing that as coincidence, you ask exactly what was adjusted. That clue leads you to a sensor bracket that was moved slightly and now sits at the edge of its reliable detection range.
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
Treating operators as unreliable witnesses
Hiding uncertainty instead of asking a precise question
Calling many people before gathering basic facts
Failing to update production after the repair
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 5