This week's security brown bag topic was the Quad9 filtered DNS service: pros and cons, alternatives, etc. This post contains my notes.
I hate meetings. I hate anything that asks me to step away from my work for overhead tasks. However, meetings are useful and necessary if you want a group of people to act in a coordinated fashion. I've been working recently with a group that includes several people new to the professional world, some of whom are struggling with how to have a meeting like a professional. It occurred to me that while there's been a lot of writing on meetings, I didn't have a succinct checklist to point folks to... until now.
Qualities Of a Good Meeting
You know you've had a good meeting if it:
Makes efficient use of all participants' time.
Communicates information clearly, in a way that invites clarification and corrects miscommunication before they can become a problem.
Acts as a "forcing factor", an event that spurs people to action before they have to report on their inaction.
Results in clear, actionable decisions.
Meetings that waste people's time or don't accomplish anything don't deserve those people's time or attention.
How To Have a Good Meeting
Respect Everyone's Time.
- Be on time to the meeting: everyone waiting for you is wasting their time.
- Be prepared when the meeting begins. You should never discover a teleconferencing problem, rifle around to find note-taking tools, or take your first look at the agenda after the meeting begins.
- End the meeting on time. Failing to do so can wreak havoc on others' schedules, causing them to miss other commitments.
- Don't have more meeting than you need. Scheduling meetings for one hour blocks seems to be the default, but that is usually a bad choice. Consider:
- If the meeting is well-run and of a small scope, it can probably be done in 25 minutes.
- A one-hour meeting can, at worst, usually be trimmed to 50 or 55 minutes in order to allow all participants time to get to their next meeting.
- Don't encourage people to "fill the whole time slot" in order to appear busy. If the meeting ends 4 minutes or even 45 minutes early, thank everyone for their efficiency and release them to get back to their "real" work.
- Make the schedule clear. Use calendaring software, if possible, or failing that an easily referenced meeting list to make sure that everyone knows upcoming meeting dates and times, and receives notices of cancellations or changes.
Make it easy for all to prepare for the meeting.
- Both the notes from the previous meeting and the written agenda for the coming meeting should be made available at least one business day in advance of the coming meeting.
- The written agenda should be organized by topic, not by the person reporting, though the person reporting on each subject, or leading discussion on it, should be noted.
- The written agenda should include (by reference or attachment) any related materials for discussions to be held.
Two models for effective meeting notes:
- Option A: Have a designated person present to take notes, who is not part of the proceeding, and who will distribute notes to all attendees after.
- Option B: Use a collaborative editor, such as Google Docs, to take notes as a group in a location that all can reference.
Have a written agenda beforehand, and stick to it.
- You may want to open up the floor for about a minute at the start of a meeting to allow additions for something last-minute, but once the agenda is set, anything not listed will be deferred for discussion at a later time.
- Forcing adherence to an agenda is the best way to get the meeting to end on time.
- One person should chair (run) the meeting. It is up to this person to keep discussion moving, prevent tangents, and keep to the agenda.
- The chair (with help from all participants) should ensure that any decisions to be made in the meeting actually happen.
- The person(s) taking notes should ensure that all action items are included, and that action items from the current meeting make it to the next as "old business" so that they can be reported on (if needed) or confirmed done.
Do your part as a participant.
- Before the meeting: Add any items you wish to discuss to the agenda. Review the agenda and any attached materials.
- The day of the meeting: Show up on time, with working equipment (note-taking gear, your teleconference set-up, etc.), and prepared to discuss the items on the agenda. Be prepared to take notes for yourself or as part of a group note-taking document. Pay attention so others don't have to wait on you.
- After the meeting: Review the meeting notes and make sure that you have added any action items that resulted from the meeting to your to-do list, then do them.
Why I Care
I've been told that I'm very un-hacker-ish about meetings. By my observation, the usual hacker behavior is to whine about meetings, show up late and/or unprepared, and waste lots of other people's time with interruptions, distractions, and meandering monologues or debates that cause the meeting to run longer than scheduled. I've even seen one such person play video games in the middle of a meeting. So, I'll take that particular charge as a compliment.
I don't grok why so many hackers not only behave like this, but aren't embarrassed by their total lack of professionalism.
Meetings are going to happen. Doing them properly means that we get less bikeshedding and more action, and that everyone gets to spend less time on meetings. My record for one-hour meetings is getting everyone out of the door in 21 minutes (per meeting average for a three-month span in which I tracked it).