Q
IMO...If you are not following the process/procedure as written then you should ask yourself, is the process/procedure necessary? If it's not a necessary process, as in it has no influence on the finished product and not required by ISO, get rid of it! If it is necessary, is the process written to align with best practices? If the actual process achieves the same or better results than the written process, it time to re-write the process.
The problem I run into is we write great processes and people will choose not to follow the process through carelessness or impatience.
If it takes a little longer to do it right the first time, it is still quicker than doing it twice.
But I digress, I was handed a QMS three months before certification. I had little knowledge of ISO or quality in general. I had to quickly polish up what was already written, find the holes, and make it work. Now that we are certified, I have had the time to really look at things and see if they make sense. I have found that we have over-documented everything. We have process flows for filling out forms.
The Cove has been a very helpful resource!
The problem I run into is we write great processes and people will choose not to follow the process through carelessness or impatience.

If it takes a little longer to do it right the first time, it is still quicker than doing it twice.
But I digress, I was handed a QMS three months before certification. I had little knowledge of ISO or quality in general. I had to quickly polish up what was already written, find the holes, and make it work. Now that we are certified, I have had the time to really look at things and see if they make sense. I have found that we have over-documented everything. We have process flows for filling out forms.
The Cove has been a very helpful resource!