I would be very careful taking that line. Organizationally, cutting a group out of decision making is probably the fastest way to alienate them and make them h

I would be very careful taking that line. Organizationally, cutting a group out of decision making is probably the fastest way to alienate them and make them hostile towards other groups. I have had this happen to me; my team is already overloaded from being pulled into various things, some team has a project we don't have time for, they go ahead without us, and it creates a mess. We're mad at them because their system won't work with ours, we blame them for moving ahead without us, they blame us for not being ready to move ahead. The end result was a bunch of re-work and resentment in both sides. It also screws up higher level planning and prioritization. It lets teams directly apply pressure to each other without filtering through upper management who can look at the big picture of prioritization before passing the pressure down. It doesn't matter if project X is more important, project Y is threatening to move ahead without us and we need to get in front of that before it becomes tech debt for us. Ultimatums don't work in relationships, and team dynamics are still a human relationship even if it occurs in a business setting. My real solution is that the lowest manager with oversight over both teams needs to clearly set priorities and expectations, and to enforce those. If that 50 person meeting is for a project with a low priority, people need to accept that it will likely move slowly. If it's for a high priority meeting, management needs to communicate that this meeting trumps other conflicts.