- Meetings are so easy, so useful, so tempting…
- Three rules for effective meetings
- Meetings are regular
- Meetings are optional
- Meetings are well prepared
- What about “Brainstorming sessions”?
- What about “Status meetings”? Change them to “hang outs”!
- How many people on a meeting? As few as needed!
- Remember: Write stuff up after the meeting, too!
- One thing: switch to regular, optional and prepared meetings
Meetings are so easy, so useful, so tempting…
One of the major problems for most of the companies hit by the Covid-19 pandemic was the way they did meetings. They thought that because now everyone had access to video-conferencing software, they could just replicate the same dynamic they had in the office. They just kept organizing meetings.
I get it, it’s tempting. When you’re all in one office, you’ve got this all too easy. After all, everyone’s around and there’s a hole in everyone’s calendar, let’s fill it up with yet another meeting, right?
I mean, meetings have so many benefits:
- As a meeting participant you get to show off in front of everyone how busy you are, being on yet another meeting, contributing yet another brilliant thought, stroking your manager’s ego with a praiseful comment, while at the same time you have a few moments to catch up on email and social media.
- As a meeting organizer you’ve got this unique opportunity to delegate responsibility to the group and be off the hook for making an incorrect decision. It works every time - don’t know what to decide? Organize a meeting!
- Meetings are a solution to all common team problems. No ideas? No direction? No strategy? Let’s organize a brainstorming session! Additionally this is so good for team spirit, right?
And on top of that, make sure to invite everyone you can! Don’t forget anyone, or they’ll feel offended! After all, the more the merrier, right?
This has to stop. It’s time to approach meetings differently.
Three rules for effective meetings
Over the years we have come up with these rules for running effective meetings:
- Meetings are regular.
- Meetings are optional.
- Meetings are well prepared.
Let me dive into all three below:
Meetings are regular
By definition we avoid impromptu meetings. We resolve to having few regular meetings that happen weekly, like:
- Developers’ meeting every Monday at 10am for up to 1 hour
- Directors’ meeting every Monday at 2pm for 1-1.5 hours
- Support meeting every Tuesday at 9am for 1-1.5 hours
- Design meeting every Tuesday at 2pm for up to 2 hours
- Marketing meeting every Wednesday at noon for 1-1.5 hours
- Roadmap meeting every Thursday at 3pm for up to 1 hour
The cool thing about these meetings is that they’re clearly defined. They are on our company’s calendar and everyone knows:
- When the meeting takes place
- What it’s about
- Who’s assisting
- Where the meeting takes place (we have a separate virtual room dedicated for each meeting1)
Additionally every meeting is time-constrained and they run no longer than 2 hours - if we haven’t discuss everything, we move it to next week’s meeting.
For each meeting there’s no negotiation, no RSVP, no barrier of entry. We all have agreed once on these meetings and that’s it.
These predictable pattern of meetings helps everyone on the team plan their week, make sure they can budget their time for focused work (as discussed in Chapter 4) and preparation time for each meeting (more on that below).
Now, despite these meetings being “set in stone” every week, each of them is…
Meetings are optional
That’s right. Meetings should be completely optional. If we don’t have topics to discuss or just feel like we’re just too busy this week and the topics can wait, we cancel the meeting. If someone cannot come to the meeting, they just let others know and don’t show up and nobody gets offended.
Whenever we cancel a meeting, we almost never re-schedule it. We just cancel this week’s meeting and we meet next time same time next week. That’s it. Makes everything very easy.
Meetings are well prepared
This is key. If a meeting doesn’t have an agenda, there’s no reason for this meeting to happen at all.
Agenda is not enough.
Each topic on the agenda has to be written up. If nobody took their time to write up a topic, we usually don’t discuss it. There should always be a person responsible for each agenda topic.
Meetings are not a time for a presentation.
Presenting an idea on a meeting hardly ever makes sense. It’s better to add this idea to the agenda and write it up and let everyone read it before the meeting.
This way during the actual meeting we don’t waste time discussing the entire topic, as everyone has read it beforehand, but we only focus on the points of tension, the nuances, the missing parts.
But for this to work…
Everyone has to do their homework. Everyone assisting the meeting has to read and digest the documentation prepared before the meeting.
Famously Jeff Bezos before each meeting is doing something similar.2 Before they start talking, everyone reads the documentation in complete silence and only once everyone has read it, they start to discuss topics.
It’s a good first step, but we take it to a whole new level. I personally need more time to form an opinion, so I prefer to read the documentation a few hours before the meeting to really think things through.
As discussed in Chapter 5 about writing stuff down, we use a collaborative documentation app so we can comment on each and every paragraph of a written text. This way very often there’s a “meeting before the meeting” where we exchange comments about certain parts of the documentation hours before the meeting. This makes our real-time meeting so much more efficient. We’ve already argued the main points in the comments by then, so once the meeting starts we focus on the last bits now that we’re all live in the same virtual room.
Of course for that to happen, the documentation has to be prepared in advance. Our rule of thumb is that the topics must be written up until the evening the day before the meeting.
What about “Brainstorming sessions”?
Avoid them like a plague. You are not that brilliant, nor is anyone on your team, to come up with a genuinely great idea on the spot. Usually the first ideas that come to mind are crap. Good ideas require thinking time, research and focused work.
Sometimes we do a “brainstorming moment” on one of our meetings, but we limit the time for this to more-less 15 minutes, then we write down all the ideas that came from it and we choose a person who’s going to process these ideas and prepare an agenda item for the next week’s meeting.
What about “Status meetings”? Change them to “hang outs”!
We don’t do status meetings. Why would we? As I described in chapter 6 about banning email, we communicate in projects and tasks, so to learn a status of a project or task we just need to check our system. There’s no need for a verbal status update.
However, as we’re an all-remote company, I want to make sure we don’t feel alone. When you don’t go to an office, don’t meet your team members every day, it might get lonely. That’s why we have our directors, developers, support and marketing meetings. These might not have many agenda items but usually happen anyway so that we can just see each other, say hi, share a little what we’re working on this week… and just re-connect with our team members.
These meetings have the “hang out” part, where we just hang out together and the “agenda” part where we discuss certain topics. However, if there are not many topics to discuss, we respect each other’s time and we just cut the meeting short. That’s why above I mentioned all the meetings with “up to” times. If one week we’ve got only 1 hour of things to discuss, we don’t extend the meeting, we cut it short and get back to our work.
We try to avoid having longer meetings than 2 hours. It’s a magic threshold. After that we’re just too tired to discuss anything. The good thing about having regular weekly meetings is the fact that very rarely we’ve got so many topics that extending a meeting beyond 2 hours is warranted… and after all, we can always get back to things next week. So no stress.
How many people on a meeting? As few as needed!
We make sure we don’t have too many people on our meetings. Usually more than 6 is too crowded. So we try to make sure that nobody feels bad about not being part of a meeting. We are very mindful of each others’ time.
Steve Jobs3 famously before each meeting looked around the conference room and checked if there’s no one excessive assisting the meeting. He often just threw people out when he believed they had no reason to be there. It’s radical but I totally get the sentiment.
We try to find the people who give the most insight for each meeting and sometimes important people on our team don’t participate in some of our important meetings, because we’d prefer they used their time in a better way.
For example, our CTO doesn’t participate in Tuesday’s Design meeting. But we still have his contribution, because he reads each meeting’s agenda and the associated documents so gives us his feedback in comments before each meeting. Actually that’s where we ask many of our team members about their feedback.
Again, that’s why publishing agenda documents before a meeting is so useful. Everyone on the team can contribute with their comments, even if they later don’t participate in a meeting in person.
Remember: Write stuff up after the meeting, too!
After each meeting one of the meeting participants posts “meeting minutes” as a comment to the meetings’ task. This way the entire team can read what the meeting was all about and what we’ve agreed on.
Also all the relevant tasks discussed on the meeting get updated, so we can move on with actionable items right after the meeting.
I keep repeating myself, but as noted in Chapter 4 - write stuff down! Especially:
Write agenda items up before each meeting and later write the conclusions. This way everyone on the team can feel like they’ve been there and they know what’s going on.
One thing: switch to regular, optional and prepared meetings
Avoid impromptu meetings, make meetings regular, no longer than 2 hours, no more people than enough and always written up with agenda items before and with actionable items or conclusions written right after. That’s the only way for your team members to feel in control of their calendar and plan their time around meetings and longer stretches of focused work.
For further reading on the subject of meetings I recommend the book: “Read This Before Our Next Meeting” by Al Pittampali4.
One of such scenes is described by Ken Segall in his book Insanely Simple: The Obsession That Drives Apple’s Success ↩