An example of rules and unwanted outcomes. I once wrote an application at a big company, which had a strict application packaging process, for remotely install

An example of rules and unwanted outcomes. I once wrote an application at a big company, which had a strict application packaging process, for remotely installing apps on machines. A last minute change was requested, which resulted in a small error being made in the 'tab order' of the screen. It would have taken one compile and 20 seconds to fix, but because the rules said the executable couldn't be updated once packaged, it remained so. 7 years down the track, the same application was still being used, and the users of said app had to skip using the tab key to get around fields and instead mouse backwards. 7 years of aggravation and frustration on the part of users which could have been avoided with 20 seconds worth of rule breaking. I'm aware of what those rules are for, but having a structure so fixed that it causes this type of inefficiency is frustrating to all involved. It's not like anyone benefited from following the rules, save for the guy who could honestly say to his boss 'I made them follow every last rule'.