Yeah, no kidding.
I worked on a government contract once. Getting anything done required extensive amounts of fighting the process, and sometimes fighting the people -- they had their process, there was nothing in the world which could streamline it, and everybody was so incredibly territorial about their own stuff it was absurd. To the point that an Oracle DBA went in and removed permissions from an Oracle product -- the Oracle product explicitly said "need these permissions", the departmental policies said "no you can't" -- and then we spent 3 days understanding why something broke until the DBA said "oh, I removed those".
And then as the pilot project was coming on line (and it was purely a pilot project), the government employees started demanding the training course, the manuals, the support callflow, and a dozen other things which didn't exist yet.
It was maddening, the Director (or whatever he was called) would say "this must be done today", and we'd start doing our part ... and then the government people would throw up dozens of roadblocks to make it impossible. Even when directly told by him to do it this way, they just simply didn't.
There were some smart people, but everybody had been so beaten down by the bureaucracy that it was impossible to get anything done.
I sure as heck wouldn't want to be doing tech in the government, because getting anything done was nigh on impossible, and there were usually 3-4 layers of CYA going on as everyone tried to ensure that if anything ever went wrong they could say "well, I followed all appropriate processes".
The tie, I could live with since I don't find them to be that bad. I actually like the tie.
The processes and pointless procedures ... that was just crazy.