I have always in my 23 years in the IT world found that things like "requirements" and "specifications" were like the lines in a coloring book. I still get to pick the crayons but I'm expected to color within the lines.

Where I work we have a very regimented system whereby we have to ask "mother may I" before doing almost anything that I would consider System Administration 101. But that doesn't stop me from getting my job done. There are always creative ways to work within the system and still get your job done.

I've worked for small companies (less than 50) and very large companies (IBM) and they each bring to the table advantages and disadvantages as far as working for them goes. One company that I worked for there was only 3 people between myself and the CEO and boy could I get work done in short order because I rarely had to get approvals to do anything unless I was spending money. If I was spending money I could get an answer and/or approvals within a couple of hours.

That was OK when that company was small and there weren't many other people making changes in the data center. When the company grew a change management system was essential to maintain everyone's sanity and to prevent us hard charging IT folks from stepping on each other's toes. (example: "What do you mean you're putting that server on that shelf in that rack? I'm going to use that spot!")

The moral of the story is: structure can be a good thing if it is not abused. As long as it doesn't prevent you from getting your job done. It may occasionally slow you down, but in the long run it is a good thing.