In a new series I’m exploring ways that my new team can grow and change. The team is really fantastic – super capable, skilled, dedicated, and hard-working. As a CS group we can easily find our time eaten up with customer calls, user group meetings, and onboarding/implementation activities. Our meeting times need to be highly productive.
One of the great strengths of any team is the way its members share and work together. At their best, our meetings will amplify and enhance* the benefits of being together, while ensuring that they remain focused and effective for all.
In re-examining our meetings, we’ll seek to make some tweaks that achieve the following: * Run highly effective meetings * Building something of a consistent, predictable daily or weekly schedule * Ensure we don’t have a single, over-emphasised ‘meeting day’.
Leading effective meetings
Some things we’ll try this year include adopting the following guidelines:
- Be explicit about the goal/purpose: training? FYI? Decision?
- Be selective about attendees - protect the time of others but try not to exclude
- Pick the right duration: don’t do an hour where 15-30 minutes will suffice
- No agenda, no meeting
- Everyone comes prepared. Agenda posted 1 day before? Reading material?
- Look for ways to drive involvement from everyone. Collecting input before the meeting can help here.
- Be explicit in documenting actions/outcomes. We’ve met; so what now?
Building a regular daily and weekly schedule
The second priority is perhaps less important, but can be equally valuable.
A regular cadence ensures that valuable items are always covered. It should reduce the need for large numbers of ad-hoc meetings.
This is often a bit of a balancing act. If something is truly urgent it should happen straight away. Most things we consider ‘urgent’ are just considered this way because they’re in our heads right now. They can usually wait.
This is no doubt just a starting point. We’ll need to keep iterating and improving our practice, and I’ll try to reflect on those adjustments as we go.