You're making the exact same mistake. Check the wikipedia article on this particular flight, under the heading 'Cause':
""The National Transportation Safety Board determined that the probable cause of the accident was "the omission of all the O-ring seals on the master chip detector assemblies leading to the loss of lubrication and damage to the airplane's three engines as a result of the failure of mechanics to follow the established and proper procedures for the installation of master chip detectors in the engine lubrication system, the repeated failure of supervisory personnel to require mechanics to comply strictly with the prescribed installation procedures, and the failure of Eastern Air Lines management to assess adequately the significance of similar previous occurrences and to act effectively to institute corrective action. Contributing to the cause of the accident was the failure of Federal Aviation Administration maintenance inspectors to assess the significance of the incidents involving master chip detectors and to take effective surveillance and enforcement measures to prevent the recurrence of the incidents.""
A faulty procedure means that every plane of this make and model would have this defect. A faulty execution of a correct procedure would only affect those aircraft that were handled by the people executing the procedure incorrectly.
It is the difference between a bug in the software (the procedure) or a computer with a faulty ram chip. Both will cause your program to crash, but the first will cause every instance of that program to crash, the second only affects the specific instance run on that hardware.
There is a huge difference when it comes to root causes. If perfect procedures are executed sloppily then it doesn't matter how good the procedures are. And that is why there was a huge flap over this particular incident because if there is one thing that the whole airline industry revolves around then it is adherence to procedures.