by John J. Walters
I stumbled across this humorous image about meetings as I was scouring the web for seed ideas for this week’s blog post, and it reminded me of why we started this site in the first place. Simply put: meetings suck. But they don’t have to. Most people regard meetings as pointless wastes of time, and in many cases they’re right to do so.
The idea of paying employees to sit through weekly (sometimes daily) meetings that can only be described as “complete wastes of time†must make most business owners cringe. But if they’re all bad, then why don’t we abolish meetings entirely?
Meetings are an unfortunate reality of life in the business world, but they certainly don’t have to be as bad as they are. We have emails, phone calls, and text messages to keep employees updated. We have services like PBworks (which MeetingCaptain syncs with, incidentally) to allow coworkers to facilitate collaboration without anyone being in the same room. Most people resent the technological leash that businesses are using these days, but I’m sure they would resent it a lot less if it meant a massive reduction in the number and length of pointless meetings they are required to attend.
True, some things need to be hashed out in a group setting. When my team was working together on the first draft of our book, our weekly meetings were essential to keeping the project rolling and maintaining a high quality of work. The idea that we would all have to justify our work to each other on a weekly basis provided a healthy atmosphere of competition and accountability. In fact, we often found ourselves going over the allotted time because we had so much to accomplish.
If I wanted to keep the meeting to a manageable length, I found that I sometimes had to shortchange my own work even though I was the team lead and project manager. Then I realized that if I didn’t want to cut work time, I had to make an effort to cut the seemingly obligatory logistics update at the beginning of the meeting. How did I do this? By making good use of technology.
Unfortunately, I didn’t have MeetingCaptain or PBworks to help me back then. Instead of adding everyone to one online workspace and using that to store the latest files and communicate important updates I had to send a lot of emails and keep painstaking account of each and every draft. It required a lot of preparation, but it also allowed me to keep the meetings shorter than two hours. It also placed the burden almost entirely on me to make sure we had a good meeting, even though I was only one of the seven participants.
Running a good meeting requires a lot of strategizing and coordinating. That’s a fact. But if you can take care of the first part, then technology can take care of the second.