It's not about "job quality" per se
ISO is about being able to reliably repeat a process day in and day out. Even if it is being done in an inefficient way, it is consitantly repeatable.
As the article states though, by documenting you can attempt to see where your problems are and update your processes and proceedures to fix them. Just because you document it one way does not mean it cannot change.
ISO can be a good thing if handled properly. The problem is, in most places it is not handled or implemented properly.