Hot on the heels of yesterday’s post Meetings for an effective engineering organization, I bring you more meeting content! In You can’t just cancel 76,500 hours of meetings Becky Kane makes some good points about the context of meetings within an async culture:
Reducing meetings is just one piece of creating an async-first culture.
She gives some examples of other pieces that are harder but even more important in having a lasting impact on engagement and productivity:
- Decentralizing decision-making so people don’t have to wait for permission and deliberation before acting
- Delineating clear areas of responsibility so people feel individual ownership to move work forward
You can read the post for the other examples, they’re all very good! As with most of these kinds of topics it’s really valuable to think about them not in isolation, but as a system. It’s not about whether meetings are good or bad, it’s about how meetings fit into the culture and system of planning and delivery that the organization operates in.
Becky’s illustration of what “async” really means is a perfect example of this: