Simple Rules to Ensure Your Meetings Matter
May 7, 2020
Why do so many meetings suck? Most people see meetings as an interruption from work, that they’re a waste of time. How many times have you heard in whispers “that meeting could have been an email” and agreed?
In the time of COVID-19 and Zoom, companies are leaning into more meetings than less in order to replicate the office environment, making it more frictionless than ever to invite someone to a meeting, whether or not it’s really necessary. This is often done without asking the all-important question: Why?
Without this question it’s impossible to look objectively at other questions, such as: Can I be more mindful of people’s time by sending an email, or a well-written slack message? Can I write a page on the internal resource library to have a longer-term impact? What is the value of this quick communication? Jumping to the conclusion of needing a meeting also fails to recognize that a meeting does not always extract value equally for every attendee. Some people can zone out, are less vocal due to introversion, or absorb information worse during a meeting. And when meetings simply exist to take up time, we lose out on time that could be spent making products better.
Basecamp states in their rule book that “chat dissolves, writing persists”. A meeting will be forgotten within the month, but if you write an email or memo you create a permanent resource that can be archived and re-read. Asynchronous communication can allow participants to be more mindful of what they say and how the audience interprets the content. This transition into more intentional and respectful communication can allow us to build more thoughtfully designed products.
On a recent project, I introduced a new set of API endpoints. I scheduled a meeting to walk through them with the team. Afterwards, I realized that I could have shared documentation instead, and asked for their feedback asynchronously. Then, if it was decided that a meeting was necessary, I could have scheduled as per the team’s needs. In this way, I would be able to use an asynchronous-first communication style that allows the team to give careful consideration and measured feedback in their own way, allowing them to do their best work and make the best products possible.
If a meeting has a clear reason for being scheduled and requires the direct participation of every participant, it can be an invaluable way to sort something out. However, when was the last time you came out of a meeting thinking “that was a perfect use of everyone’s time”?
We need to take extra care that meetings are valuable and worthwhile uses of everyone’s time. We need to appoint a facilitator to maximize the value of meetings.
A facilitator is responsible for achieving the meeting goal while maximizing the level of engagement of all attendees.
- A facilitator establishes the goal of the meeting. Examples:
- Communicate decisions made
- Gather information from others
- Create a plan
- Drill down to the actual goal. “You want to communicate a decision made. What is the end goal of knowledge being transferred? What action items do you wish the attendees fulfill?
- Clarify if more than one meeting is needed. The facilitator is responsible for scoping the meeting and it’s goal.
Facilitating meetings properly when they’re necessary and considering alternative, more long lasting methods of communication can allow us to build better products. We have more time to do them, our attention isn’t broken as easily, and we can consider our input better.
Over the past few weeks, as I’ve ended meetings only to look around and realize I’m still at home, I’ve had the time to truly see the value of good meetings and understand the frustrations of others when a meeting puts a dent in their productive time. At Connected, our job is always defined around one key job—building better products—and for me, only if a meeting helps to do that job, is it time well spent.
Thu Jun 23
Plugging In: How Going Remote-First Is Challenging Our Engineers to Collaborate More Deliberately
Going remote-first isn’t just giving our engineers the freedom to do their best work. It’s challenging them to define what and how they’ll achieve it, forcing them to work together more deliberately - in pairs and across projects. And that’s an excellent thing.
Fri Jun 17
Connector Spotlight: Ryan Lim
What does Ryan Lim, Director of Engineering, Practice, do outside of work? Most might know that he is occupied with video games, but you likely didn’t know that he’s also quite the handyman. While he’d describe himself as chill, curious, and creative, knowing that he can renovate floors, tile, drywall, electrical and plumbing, we’d also like to add capable to that list. Whether it’s letting his imagination flow while working on a project or playing with his favourite stackable blocks (can you guess what his favourite product is?), rest assured that the only vendetta from Ryan you need to worry about is in a movie. Discover more about Ryan in this week’s Connector Spotlight!