The benefits of standardization should not be so rigorously enforced that potential time saving and innovative fresh approaches are suppressed. One approach is to do everything in a new way, making everything up as the system is built, never looking back to previous successes. Another is to religiously follow established patterns of uniformity, never allowing new ideas to be introduced, always doing everything the same way.
Most companies fall somewhere in between.
The optimal approach is to begin with the existing standards as a baseline, and then to review, discuss, revise, and implement each throughout the system building process. Another unreasonable focus can be on program efficiency and processing speed, rather than on program modularity and maintainability. This is a mistake. With the availability of today's highly advanced technical platforms, no one really cares anymore if it runs in 20 instead of 80 nano-seconds. This is especially true for business programmers.