On one project we had dozens(!) of meetings involving 5-10 people to decide what to call an API endpoint that no human being will ever see again after the initial implementation. A nearly cried. I told them that they could literally mash the keyboard and use that, it's fine, just make a decision already. Nope. Got to run it past marketing. Branding (a separate team). Networks. BAU support. Domain hosting team. Architecture team. SecOps. Etc, etc...
The same org then had daily meetings involving 10+ people to decide how to purchase $500 worth of USB security fobs. At one point a project manager broke down in tears and pulled his credit card out out, and offered to just buy it himself if it would make the madness stop. There was a stunned silence, and then somebody raised the point that yes, fine, sure, but then how would warranty returns be handled if he becomes the "supplier"? With a straight face that same guy suggested another meeting to discuss the warranty return issue.
[1] https://www.youtube.com/watch?v=JAk448volww
Full episode: https://www.youtube.com/watch?v=oLU-Evdlt-A
He lived under communism, with its dozen+ levels of government bureaucracy, so you can imagine why he thought it was hilarious.
Once I had worked as a consultant for government departments, I suddenly "got" it, and now Yes Minister is one of my favourite TV shows of all time. The bit about hospitals is all too true.
For example, just recently, I had to fill out a stack of paperwork to provision a virtual server for hosting an archived, read-only web site for data that hasn't changed since 2017 and has three (3) users. Literally a stack. As in, a pile. About a hundred pages, or a short novel. That nobody will ever read, except if the time comes to blame me for a shortcoming that they themselves could not have avoided.
But, I do exactly what you do - I prefer something well-written and it gives me time to think about it. As someone talking to a lot of people within the company, I sometimes get asked to go on a client call. I almost always say no. It's not my job to talk to clients (and that means being ready to look good for them) and saying whatever needs to be said in a call doesn't do much that an email can't do. While being there as an "expert" to the client is probably something that customer-facing people want, I have nothing to gain from it.
Useful meetings engage people : a fresh new idea to have everyone go research more, a way to gather the team to focus on tough questions, or to explain a point better than chat messages.
And don’t get it twisted. I’ve been in these types of meetings. Client meetings, project meetings, etc. It’s always been as an outsider, but they’re all the same. Small talk, people arrive, someone always has to have everyone introduce themselves, then there’s a quasi-presentation/conversation, and eventually everyone leaves. I can’t think of a less efficient means of communicating an idea than that.