Of course Microsoft is a big place and different divisions work differently. I'll never take the risk of landing in such a mess again, though.
Of course Microsoft is a big place and different divisions work differently. I'll never take the risk of landing in such a mess again, though.
That sounds horrible. Did you mention your concerns to the people who owned those meetings, in a way that made it clear you were trying to help improve them?
I've had success several times with this in BigCo, with various satisfactory outcomes:
1. "You're right, this meeting is BS! But it has to happen for various reasons X Y Z -- since you don't care about this area you don't need to come, we'll grab you if we need you."
2. "You're right, and other people feel tuned out as well, so let's try cutting it to 10 minutes / mailing out an agenda beforehand / starting exactly on time."
3. "You're right, this is an inefficient way to gather state so we're going to just swing by each person 1-on-1."
4. "You're right, this team is too big so we're splitting in 2/3 smaller groups"
I think the project I worked on was worse than average because it was the sort of cross-cutting change that affected a lot of different teams - six different products, I think? There were a lot of PMs involved.
It's worth testing the waters a few times. You'll know pretty quickly if they value your input, and if not you can decide if you want to continue working for them.