The point of sequels coming out instead of new IP is actually a side-effect from developing fantastic storylines. People want to continue the stories and worlds they've visited, and is that a bad thing?
The amount of information you're trying to free is entirely staggering and consists, largely, of tables of numbers. These numbers are incredibly significant, but people generally can't see them.
After you free all of this information and make it available to the public (as it should be), then what? What do you expect for the public to do with these numbers? Tables of information are not nearly as useful as graphs. This data needs to be seen, but, more importantly, it needs to be understood.
Do you have any ideas for how to disseminate this information? Perhaps a team-up with someone like gapminder.org's Hans Rosling might be particularly valuable for all of us.
Having worked in a similar position, it can be incredibly hard managing hundreds of computers with different requirements. When one supplier decides that they're not going to support the new OS iteration fast enough, the IT department gets to pick up the slack and everyone hurts.
I see very little proof here beyond that snarky responses beget snarky responses and the system stays broken.
When your day-in-day-out job is to deal with the angriest person in the building, you tend to either have an emotional breakdown or you ice-over, harden up, and learn to bring a healthy level of disdain with you. It's about survival. Trying to actively be everyone's friend gets you beaten pretty badly in the field. You can't give everyone what they want.
Finally, because of policies, you have the be the bad guy. You can't simply choose not to enforce the policies. Someone higher up the chain makes those decisions for one reason or another, and even if they are good decisions for overall policy, there are bound to be problems that arise. Because policy will always be in need of update and will never completely respond to the needs of users, you, the IT monkey, becomes the lightning rod for every ounce of ire that cannot be directed at the policy.
Everyone expects that IT seems to either magically know exactly what's going on at all times, or that they're know-nothing lower primates. The truth is they're working stiffs like anyone else and that their job revolves entirely around dealing with the problems that noone else really wants to touch.
It's janitorial work w/ computers and added stress.
A debugged program is one for which you have not yet found the conditions that make it fail. -- Jerry Ogdin