Often the issue isn't even meeting prep, but the meeting itself. - presenting information: is often better in document form (if precise, concise, not fluf, wit

Often the issue isn't even meeting prep, but the meeting itself. - presenting information: is often better in document form (if precise, concise, not fluf, with diagrams etc.) with the added benefit of potentially being able to fix error retrospectively (Note: Similar to presentations you don't want to obsess about spelling, grammar, style and bullet points often are the way to go. Avoid "story writing" at all cost, you are presenting information not telling a story. - technical discussions: if done in meeting for anything non trivial leads often to sub-par results, interestingly that is in my experience also true for fast messaging style text communication (like e.g. slack motivates you to do). Thinking more before writing and also having all you questions/comments written down before sending any of them does in my experience works the best. - teaching people: here meeting like things can be good if individualized to the learner and supplementary only. But often you wouldn't call it a meeting anymore. Transcripts can be quite nice in this case but as it should only be supplementary should be unnecessary. - synchronizing work: Inefficient if mostly done through meetings, through sometimes having supplementary meetings for it can be useful. - planing work: Often highly inefficient if mainly done through meetings, through finalizing a plan through a short meeting is a good idea. - brain storming: Can be started by a meeting, should not be concluded by a meeting as mind tend to pop up ideas at the strangest times and should not diverge into technical discussions about the proposals. combine that with how interruptive meetings can be having too frequent meetings seems like a sure fire way to reduce productivity