Meetings That Could Be Emails (and emails that should be meetings).

Legal is the only function that complains about too many meetings and then schedules a meeting to discuss how to reduce meetings. That's not a joke. It's a diagnosis.

The previous edition mapped the seven silent leaks of legal time. This edition focuses on the fifth — avoidable meetings — because it has its own mechanics, disproportionate cost, and a known solution that legal has yet to import from other functions.

Before we continue, an important distinction: meetings aren't the problem. Meetings without criteria are. Functions that have mastered async communication — software engineering, design, product — didn't ban meetings; they created objective criteria for when meetings make sense. That's the path. Not fewer meetings by principle: better meetings by criteria.
‍

The right question isn't how many meetings to schedule. It's which conversations work better written than spoken.
‍

The numbers are uncomfortable
‍

Global research on meeting time delivers data that would warrant reflection even in healthy environments — let alone in overloaded legal departments.

Only 11% of meetings are considered productive by the participants themselves. 77% of professionals report attending meetings whose only outcome was scheduling another meeting. The average effective attention span in a meeting is 15 minutes — after which most participants begin to mentally disengage, even while physically present.

APQC research with 982 knowledge workers estimated that each one spends an average of 2.2 hours per week in meetings the participants themselves deemed unnecessary or unproductive. Add preparation time, delays, rescheduling, and transitions between physical and virtual rooms, and the real number exceeds four hours weekly. Over a year, that's more than 200 hours per person lost to meetings that didn't need to exist.
‍

Why legal has more meetings than it needs
‍

Four cultural causes explain why legal departments accumulate meetings faster than other functions:

Cause 1: culture of caution

Legal is trained to avoid misunderstandings. An in-person meeting is seen as the safest channel for aligning understanding on sensitive topics. The intuition is correct — rich communication is denser than written. The problem is applying this logic indiscriminately, even to topics that don't require it.

‍

Cause 2: rigid hierarchy

‍In structures with multiple layers (associate, senior counsel, assistant GC, deputy GC, GC), meetings function as vertical alignment rituals. Each layer wants to be present, not so much for the content as for the visibility. The result: meetings with seven to ten participants where only two or three actually decide anything.

‍

Cause 3: no structured written channel

‍When the team has no place to write decisions in a referenceable and durable way, the remaining alternative is to talk. Email becomes the base for everything, but email is terrible for decisions — it's hard to search, loses context, becomes infinite threads. Without a good alternative, a meeting gets scheduled.

‍

Cause 4: confusing presence with importance

‍Legal operations managers are frequently invited to meetings where their presence isn't necessary — but where their absence would be noticed. Declining feels inappropriate. Accepting feels professional. This is the quietest engine of calendar inflation.

‍

When meetings make sense (3 objective criteria)

‍

There are three objective criteria that help decide whether a conversation deserves a meeting. If none of the three applies, there's a better format.

Criterion 1: the conversation requires negotiation or open debate. If the goal is to build a position that doesn't yet exist — for example, defining a defense strategy for a complex case, or negotiating contract terms with a counterparty — a meeting makes sense. Real-time rich interaction allows exploring nuances, reacting to arguments, adjusting positions.

Criterion 2: the topic is sensitive and requires reading emotion. Communicating a difficult decision. Giving delicate feedback. Discussing an interpersonal conflict. These topics benefit from tone of voice, body language, and opportunity for immediate response.

Criterion 3: there's significant ambiguity requiring iterative questions. When the problem is complex and still poorly defined, and resolution requires several rounds of back-and-forth to clarify, a meeting is more efficient than async exchange. But note: if the problem is already well-defined, even if complex, structured writing is better — because it gives time to think before responding.

If none of these three criteria applies, the conversation fits another format. And that's where the real gains are.

‍

‍

Async communication: what legal needs to learn
‍

Two decades ago, the software industry developed practices for coordinating complex work without endless meetings. The motivation was initially practical: distributed teams across time zones couldn't meet constantly. But what started as necessity became method — and the methods apply far beyond technology.

The core principle is simple: when something needs to be decided by more than one person, write first, discuss later. This inversion changes everything. The writer must think before proposing. The reader has time to process before reacting. Ideas arrive at the debate already structured, and the meeting — when it happens — is shorter and more decisive.

Applied to legal, this principle takes three concrete forms:

Form 1: decision documents instead of decision meetings. For any non-trivial legal decision, propose it in writing (one page, two maximum) with context, options considered, recommendation, and reasoning. Share with stakeholders. Allow comments for 48 hours. Decide based on comments — or schedule a 30-minute meeting only if disagreement remains. In departments that adopt this practice, roughly 70% of decisions never become meetings.

Form 2: structured status updates instead of conversational ones. Instead of individually responding to each stakeholder who asks about a matter's status, maintain a document or dashboard updated weekly with the status of all relevant matters. Those who need to know check it. Those who don't check didn't need to.

Form 3: priority-based communication. Adopt a simple model — P0 (real urgency, today), P1 (this week), P2 (this month), P3 (no defined deadline) — and treat each level through the appropriate channel. P0 goes by call or direct message. P1 goes by message with clear deadline. P2 and P3 go by structured document or email. Without this hierarchy, everything becomes P0, and everything becomes a meeting.
‍

Playbook: how to cancel 30% of meetings this week

It's not an exaggeration. Legal departments that apply three specific actions typically eliminate a third of their meetings within two weeks, without losing coordination.

• Action 1 — calendar audit. Pull up your calendar from the last two weeks. Color-code each meeting: productive (green), partially useful (yellow), unproductive (red). In nearly every team, yellows plus reds add up to 50%.
• Action 2 — structured decline. For recurring meetings in the yellow or red category, propose: replace with a weekly updated document, convert from weekly to biweekly, or cancel and reassess in 30 days.
• Action 3 — duration cap. Establish that meetings with fewer than four people last a maximum of 25 minutes, and meetings with more than four last a maximum of 50 minutes. This limit forces focus and eliminates Parkinson's Law applied to calendars.

Initial resistance is expected. Some people will feel devalued by no longer being invited. Others will argue the team will lose alignment. Almost always, within four to six weeks, the same resisters are the ones most grateful for the time recovered.

‍

What's coming in the next edition

The next edition closes the Mapping phase with the most frustrating leak of all: rework. That moment when someone asks "how did that matter turn out?" — and you realize you'll need to redo work that was already done. We'll understand why this happens structurally, why it has little to do with individual failure, and how modern departments build active organizational memory that prevents silent rework.

‍