@heather_reid - Which problems prompted you to ask this question? I guess one problem could be long meetings without any clear agenda. For planned meetings, especially ones which require a lot of time, I encourage people to include a clear agenda consisting of topics as bullet points.
I believe that a clear agenda forces meeting organizers to think why they are having a meeting, manage the meeting time better and know if they missed a crucial topic. The meeting invitees know the topics in advance, can request for topics to be added or removed or the amount of time to be changed. For example, I get a meeting to learn APIs for System abc. But, I don’t even know what is System abc! Should I learn “basics” of abc before the meeting or could you give an overview in the meeting itself? Btw, what do the “basics” consist of and how much time do we need to learn them?
I wish we could just reject vague meetings i.e. ones without an agenda, especially if we know that the organizer has significant work experience or continues to create vague meetings despite prior reminders. Unfortunately, many companies or managers focus too much on code and engineering (which is the most important), but neglect basic communication skills and etiquette.