> There are some weekly meetings to review changes and incidents for a 100+ person department, where they work through changes and incidents one by one, in rand

> There are some weekly meetings to review changes and incidents for a 100+ person department, where they work through changes and incidents one by one, in random order - basically you have to listen in for the whole hour+ so you can respond if they get to an incident/change you are involved with, you can maybe address questions/concerns for 30 or 45 seconds, but have to listen and wait to be called for over an hour. If you aren't responsive when called upon, you look bad, so 100+ people all spend an hour waiting for their 30 second slot. Perhaps I wouldn't do it weekly with 100+ people, but since you're already there, isn't there some value in understanding more about the incidents that are impacting other teams on live systems so that you can bring those learnings back to your team and make them more robust? Or are talking about incidents on completely different stacks and systems?