1 - Get 1300 emails a day (not an exaggeration) - 8 am
2 - Get 50 emails from executives who basically want to fire you OR someone who works for you and you have to act fast to stop the bleeding. - 10 am
3 - Get another 400 emails that are related to an ongoing discussion with managers on your level who are trying to stick your department with more work/blame/responsibility without letting you in on it. React at lightning speed to ward off evil. 2 pm.
4 - Attend many, many meetings in which executives will try to blame you, other managers will try to blame other managers, and long, tedious initiatives are discussed in hushed tones. Fight urge to nod off/strangle people/demand clarity. Pay attention because in six months one of these hapless bastards will claim everyone agreed to something preposterous in the meeting. - takes place: Every available minute. Including lunch, because "that was the only time everyone had available for some reason."
5 - Developer says he CC'd you on several emails related to the XYZ system and is baffled as to why you aren't completely up to date. Don't tell him that at 10 am the CEO was demanding he be fired (from a cannon). 6 pm.
This is why I am a developer for life.
I occasionally get similair situations to this at work, which is why I request read receipts. Makes it even more satisfying when an account manager is having a go at you for not emailing them something and you point out they sent you a read receipt for it, they just obviously didn't actually read it. My account managers hate my read receipts :)
This also means that if your developers drop the ball, you're screwed. You can't possibly know if someone is sticking bugs in the code as they race for a deadline, but when the system misses deadline because of it, guess who's responsible?
Doesn't help when you stick up for a dev for weeks or months and then they burn you by introducing shoddy code or not testing thoroughly, and their response is 'well I sent you a bunch of read receipt emails, so those browser bugs I introduced aren't my fault - you should be paying attention'.
This experience is why I work so hard to back up my boss or lead when I'm just a developer on a project.
Sounds like every project just needs the equivalent of a Twitter feed. "Status: everything's goin' smooth."
These could then be correlated, perhaps, into a dashboard of some sort. ;)
I like how you feel you protected the developer even while he was criticizing you for not doing any real work. That sums up a lot of big co. work relationships.
I've been a manager before and didn't have constant meetings. Most decisions actually get made in hallways or between a couple of you casually chatting after everyone else has gone home in my experience. I avoided meetings when I feasibly could and tacitly approved of the same attitude in my team too.
But one can imagine a totally competent boss that HATES meetings and tries to have as few of them as possible to get the job done.