Define the deviation and contain risk
Describe the product, operation or shift affected, the expected condition and the actual result. For a hypothetical packaging-line stop, record the time, the observed trip and what production was affected. For a quality deviation, distinguish affected material from material merely suspected of being affected. Containment protects the operation while investigation continues.
Follow the process, not assumptions
Compare settings, batch or shift records, inspection results, changeovers and equipment conditions. Map possible causes with Fishbone, including measurement quality: an apparent process shift may be a sensor or gauge issue. Use Why-Why to trace the branches that evidence supports; keep others Unverified or mark them False/Inconclusive as appropriate.
Connect findings to controlled action
An action should say what changes, who owns the change and when it is due. Where appropriate, include training, process standardisation or a check in another line or shift. A completed action is not the same thing as a verified effective action: compare follow-up evidence with the original problem definition.
Communicate at two levels
Management needs the problem, investigation status, root causes, open gaps and action progress. Engineers need the supporting branches, evidence and detailed action register. EasyFixProblem keeps both views attached to the same RCA case.