| Info |
|---|
Brief note on attitudeReading this piece carefully will take a few minutes. A brief review may lead you to conclude that it’s “overkill”, and that you prefer to “keep things simple” – meaning that maybe you’ll read it later. As a meeting leader, you owe it to your participants to plan productive meetings. This piece will help you do that. Maybe make a game of it. Try to find anything that you think is unnecessary. Try to find things you would do differently. Whatever you do, keep in mind that this piece was written by someone who has led thousands of meetings. The advice herein is imbued with inescapable principles, that if embraced will likely result in your meeting participants to regard the meetings you lead to be worth their time, but if ignored will lead your meeting participants to question their involvement. |
Meeting Name
Use the following format for naming a wiki page, Google docs name, Word document name, etc.: YYYY-MM-DD [Org Unit Name] Meeting. Let’s break this down
YYYY-MM-DD: Date in a format that is recognizable across cultures, and supports sorting by date (as opposed to M/D/YY, which doesn’t).[Org Unit Name]: Replace the brackets and the text with the name of the organizational unit. For example, “Board”.Meeting: The literal string “Meeting”. This allows the same name to be used for both agendas and minutes, which is helpful in that often agendas are edited to produce minutes.Example:
2020-06-17 Board MeetingOptionally, for physical files (e.g., Microsoft Word, PDF), replace space characters with underscore characters. Example:
2020-06-17_Board_Meeting.pdfDoing so will improve readability in cases where web servers escape (replace) spaces with%20in filenames of files they serve as downloaded files (e.g.,2020-06-17%20Board%20Meeting.pdf).
...