Maybe in a perfect world, but this is heavily context-dependent. Ignore office culture/politics at your own risk.
But I've found that at times it's better to work within the system a little bit like. IMing my boss if we're in the meeting to check with him first.
Stopping a meeting seems like a massive waste of resources, especially when you've already gathered the folks that can fix it.
Stopping a meeting in the middle of the planned duration is a bit dramatic, but if it’s clear after 15 minutes the group collectively doesn’t have the information needed to make a decision, its worth stopping.
I’m currently spending a quarter of my day or more in status meetings of various types. I will absolutely tell people I’m dropping (which is a the “lite” version of stopping a meeting) if they stop providing value.
> when you've already gathered the folks that can fix it.
Far too many people gather the wrong people, and stopping to excuse people is critical.
This is a really bad advice, especially in this context. Don't annoy or confront your coworkers. Tell your manager if you feel like stopping some meetings. It's strictly their job, and they will be happy to step in and do that. Besides, any meeting of 20 people should have a manager present.
In my experience, the way to handle this is usually a quick Slack conversation with the meeting organizer starting with "hey, I saw you invited all of team X to the meeting - do they all need to be there or just Y". The response is almost always "I don't know anyone on that team so I just invited them all", and by initiating the conversation you are offering to help.
There will be a discussion that starts meandering, going down rabbit holes, and somehow he'll find the perfect question to ask, which is always a very simple one, to set everyone back on target. Sometimes I don't think people even realize this is happening.
The reason it's hard to explain is because it comes across as an innate character trait, a skill that's just core to his personality, which is why it's so hard to emulate.
> In retrospect, higher ups did mention in passing about an year ago about how I need to speak up in meetings etc.
That's a critical point. If you have 15 years experience, even if you don't have a "leadership" title, you are expected to demonstrate some leadership in meetings.
First: In the meeting, you should be able to discuss tradeoffs, explain why certain things are easier, safer, or more dangerous. You should be able to give context and have an opinion. Your opinions need to be fair and unbiased, or you should be able to point out that you're biased towards a particular approach. You're in the meeting for your experience, both career experience, and (if you've been in the job for awhile,) experience with the product(s).
Second, and this is more critical, but harder to do: You need to be able to stop bad meetings. In some cases, this is a matter of just telling someone that their 20 person invite list is too long. In other cases, you need to interrupt people and force them to make their point or move on; or you need to interrupt a meeting to politely excuse half of the people in the room who don't need to be there.
Yes, it's technically management's job to stop bad meetings, but it's also your job too. Stopping bad meetings is everybody's job, but it falls on the most experienced people on a team to lead by setting an example.