Before attending a meeting, ask two questions: 1) "What specific decision or alignment will this create?" and 2) "What happens if we don't have this meeting?" If you can't provide clear, impactful answers, the meeting is a waste of time and should be canceled or handled asynchronously.
The feeling of being over-scheduled is a symptom of running ineffective meetings with no clear purpose. These bad meetings create new problems that then spawn more meetings to fix them, creating a vicious cycle of wasted time. The solution is better meetings, not fewer.
Scheduled, recurring meetings can lead to teams inventing topics to discuss simply because the time is blocked. This creates busywork that isn't impactful. It's better to meet when necessary rather than defaulting to a fixed cadence without a clear, persistent need.
To maximize the value of bringing teams together physically, focus on one of three goals. "Doing" involves collaborative work on a key project. "Learning" focuses on gaining business context. "Planning" aligns the team on strategy and roadmaps. This framework ensures gatherings are purposeful and effective.
Banning meetings doesn't solve the underlying need for alignment. Instead, it pushes chaotic, unstructured conversations into less effective asynchronous channels like Slack or Google Docs. This loses the benefit of real-time discussion without fixing the root cause of bad meetings.
If a recurring meeting serves multiple purposes (e.g., status, strategy, and tactical), it's a "Frankenstein" meeting that should be eliminated. Audit your meetings, assign a single label (Tactical, Strategic, or Operational) to each, and split any meeting that has multiple labels into separate, focused sessions.
The first step to better meetings is asking "should we have this meeting at all?" By eliminating purely informational meetings, you prevent the formation of norms like disengagement and silence. This makes it more likely that when a collaborative meeting is necessary, team members will actively participate.
Executive time in an M&A process should not be wasted on routine status updates. The steering committee's primary purpose is to be a decision-making body. Meetings must focus exclusively on program health, escalating critical risks, and making key decisions that functional teams cannot resolve on their own.
Reframe the objective of a sales meeting to be getting a 'no' as quickly as possible. A 'yes' is simply a byproduct of failing to get a 'no.' This counterintuitive approach helps identify non-decision-makers instantly and forces qualified buyers to justify why the conversation should continue.
Adopt the private equity board meeting model: circulate a detailed brief a week in advance. This forces attendees to consume updates asynchronously. The meeting itself can then be dedicated entirely to debating critical, forward-looking decisions instead of wasting time on status reports.
Instead of using meetings for context-setting, Loom’s team sends a required 'pre-watch' video walkthrough of the strategy. This forces stakeholders to arrive with full context, allowing the live meeting to be shorter and entirely focused on critique, asking clarifying questions, and making decisions.