Meeting & Facilitation Anti-Patterns

Meetings are the most common complaint in modern work — and most of the complaints are justified. The anti-patterns below are specifically about how meetings and facilitated sessions go wrong. Some are about scheduling (the wrong meetings happen), some are about running (the right meetings go badly), and some are about what happens before and after (decisions don't land). Each has a recognizable signature and a specific fix.

Scheduling Anti-Patterns

The Default Meeting

Scheduling a meeting as the default response to any coordination need, without asking whether synchronous discussion is necessary.

Signals:
  - Calendars full of meetings that could have been emails
  - Every question becomes "let's schedule a quick sync"
  - Async tools (docs, Slack, issue trackers) are under-used

Fix: Before scheduling, ask: "Could this be resolved in writing?" Default to writing; convert to sync only when the discussion needs real-time dynamics (decisions with debate, emotional topics, brainstorming, ambiguity).

The Recurring Zombie

A recurring meeting that exists because it has always existed, whose purpose has evaporated but whose calendar slot survives.

Fix: Quarterly, audit every recurring meeting. Ask: "If this didn't exist and we proposed it today, would we add it?" If no, cancel.

The Meeting with No Agenda

A meeting is on the calendar with a title ("Sync") and no agenda. Attendees arrive unprepared; the meeting meanders; nothing is decided.

Fix: No meeting without a written agenda distributed 24 hours prior. If no agenda can be written, no meeting.

The Oversized Invite

Inviting 12 people because "they might want to know." Most sit silent; some contribute reluctantly; all donate their time.

Fix: Invite the smallest group that can make the decision. Everyone else gets notes. If someone on the notes-list objects to the decision, they can respond; if they don't, their silence is sufficient.

The Wrong Channel

Using a meeting for what should be async communication, or async for what should be a meeting. Both are miscalibrations.

Use a meeting when:
  - Emotional or trust-sensitive
  - Complex decision with debate needed
  - Creative brainstorming
  - Building relationship
  - Third back-and-forth on something written

Use async when:
  - One-way information sharing
  - Status update
  - Review of written work
  - Most routine coordination

The Meeting Marathon

Back-to-back meetings with no breaks. By hour 4, participants are depleted; by hour 6, they're passive. Quality decays exponentially.

Fix: Build 10-15 minute gaps between meetings. "No-meeting" blocks for deep work. 50-minute default rather than 60, to enforce margin.

Running-the-Meeting Anti-Patterns

The Monologue Meeting

One person talks for 40 of the 45 minutes. Attendees become an audience, not participants. The meeting should have been a recorded video.

Fix: If a meeting is primarily information delivery, record it asynchronously. Meetings are for multi-directional communication.

The Rambling Check-In

Starting every meeting with a 10-minute round of "how are you all doing" that consumes a quarter of the scheduled time.

Fix: Quick, time-boxed check-in (30 seconds per person, or none for short meetings). Larger check-ins belong in 1:1s or team rituals, not working meetings.

Debugging in Public

A standup or sync that turns into a live debugging session for a specific issue, while 8 other people watch.

Fix: Facilitator intervenes: "Great, this needs a deeper look — can the two of you pair after this?" Protects the rest of the group's time.

The Expanding Discussion

One topic expands to consume the whole meeting while 5 other agenda items are squeezed or deferred.

Fix: Timebox each agenda item. When time is up, facilitator asks: "Can we wrap or do we need to extend? If extending, what are we cutting?"

Circular Debate

The same arguments, from the same people, in the same order, for the third meeting in a row. Nothing converges.

Fix: Name it. "We've been here before. What new information would change anyone's view? If none, let's decide now and move on."

The Silent Participants

Half the room never speaks. The half that does dominates. Decisions reflect who spoke, not who knew.

Fix:

- Silent writing at the start of a decision (anyone can write;
  not everyone wants to speak first)
- Round-robin with an explicit invitation to quiet voices
- "Temperature check" with fingers or dots before open discussion
- 1:1 follow-ups with quiet participants to confirm their views

The HIPPO Meeting

The highest-paid person's opinion is accepted without challenge. The meeting becomes ceremonial — the decision was made in the HIPPO's head before the meeting, and no one wants to push back.

Fix: Written proposals first. Anonymous polling. Explicit "disagree and commit" norms. The HIPPO themselves must actively solicit dissent and respond to it well.

Meeting as Audit

Using a meeting to audit someone's work in front of their peers. Status updates become interrogation. Performance review in public.

Fix: Critiques happen in private. Public meetings are for decisions and coordination, not evaluation.

Decision Anti-Patterns in Meetings

The Fake Consensus

"Any objections?" — silence. Taken as agreement. Meeting adjourns. Three people walk out still disagreeing and quietly sabotage execution.

Fix: Active consent, not silent assent. "I need each of you to say 'yes' or 'I have concerns,' out loud, one by one."

The Unnamed Decider

A decision is made but it is unclear who made it. Later, nobody owns it, and everyone can blame everyone else.

Fix: Before any decision is discussed, name the Decider. "Priya, you own this decision. We'll give you input; you call it." Use DACI or RAPID if the decision is complex.

The Invisible Decision

A decision is made in passing and never written down. A week later, no one remembers what was actually agreed.

Fix: Write the decision before the meeting ends. "To confirm: we are doing X, starting Y, with Z as the owner." Post it in writing within 24 hours.

The Meeting That Ended a Decision

Declaring a decision made at the end of the meeting with no implementation plan. The decision is abstract; no one knows what to do Monday morning.

Fix: Every decision has an owner, a next step, and a date before the meeting ends.

Facilitation Anti-Patterns

The Passive Facilitator

The facilitator is present but does not facilitate. The meeting drifts. Loud voices dominate. Time is not managed.

Fix: Facilitation is active. Interrupt when necessary. Call on quiet people. Redirect tangents. It is not about being nice; it is about being useful.

The Biased Facilitator

The facilitator has their own agenda and steers the meeting toward it, consciously or not.

Fix: If you have strong views on the topic, someone else should facilitate. Separation of decider and facilitator is often a good default.

The Framework Over the Room

Running a mechanical 5 Whys / retro / pre-mortem without reading the room. The framework becomes a straitjacket rather than scaffolding.

Fix: Facilitators serve the group, not the framework. Adjust, compress, or change format if the current one is not working.

The Closed Question Trap

Facilitators who ask closed questions ("Does that make sense?") when they should be asking open questions ("What do you think?"). Closed questions get nods; open questions get data.

Fix: Default to open questions during discussion. Close only to confirm agreement at decision points.

Pre- and Post-Meeting Anti-Patterns

The Missing Pre-Read

A 45-minute meeting is scheduled to discuss a document that nobody has read. The first 25 minutes are spent reading; the last 20 discussing.

Fix: Amazon-style silent read at the start of the meeting if pre-reads cannot be enforced. Or require pre-reads to be distributed 48 hours prior, with the meeting cancelled if they aren't.

The Notes-Taker Orphan

No designated note-taker. Afterward, different people remember different decisions. Re-litigation follows.

Fix: Assign a note-taker at the start. Rotate. Notes are posted in a known location within 24 hours.

The Unactioned Meeting

Notes exist; actions don't. Or actions exist; nobody follows up. The meeting produces artifacts but not change.

Fix: Every meeting ends with: What did we decide? Who owns each action? When is the check-in? Track them in a visible system.

The Surprise Attendee

An executive drops in unannounced and derails the meeting. Or a stakeholder shows up for the last 10 minutes and pulls the agenda into their pet issue.

Fix: Manage the invite list. If a late entrant wants a specific agenda item, schedule a separate meeting or add it next time. Do not let one person override the agenda for 10 others.

Remote / Hybrid Anti-Patterns

The In-Room Default

Hybrid meetings where in-room attendees dominate and remote attendees are relegated to "also attending." Remote participants self-censor, miss cues, and eventually disengage.

Fix:

- All-in-room or all-remote (not hybrid) when possible
- If hybrid: everyone on their own camera, even those in the
  building. Mute and unmute explicitly.
- Facilitator must actively include remote participants first.
- No sidebar in-room conversation.

The Muted Minority

Remote participants who never unmute because it's awkward. Their input is lost.

Fix: Direct invitations: "Priya, what's your read?" Chat channels for lighter input.

Video-Off Culture

Meetings where most people have cameras off. Reads as disengagement; eliminates nonverbal cues; makes decisions harder.

Fix: Norms about camera-on for working meetings (with grace for genuine exceptions). Video-off is acceptable for informational meetings.

The Time-Zone Tax

A recurring meeting scheduled at a time that disadvantages the same team every week. "Asia" or "the EU contingent" loses.

Fix: Rotate time slots for global-team meetings. Or use async-first for non-critical sync. If one group consistently attends at 6am their time, the meeting design is flawed.

Meta-Antipatterns

The Meeting-Heavy Culture

Organizations where meetings are the default medium for everything. People have 6 hours of meetings per day and no time for actual work. Status replaces execution.

Signal: Calendar looks like a Tetris game. Deep work happens only after hours.

Fix: Cultural move at the leadership level. No-meeting days. Meeting-free mornings. Quarterly calendar audits. Meeting budgets per person.

Meeting as Performance

Meetings where people attend to be seen attending, not to contribute. Value is in visibility, not output.

Signal: People juggle multiple meetings simultaneously, half-listening. Attendance is higher than engagement.

Fix: Smaller invites. Output-focused metrics ("what did we decide?"). Performance systems that measure outcomes, not face time.

Facilitation as Gatekeeping

A single person controls all meetings, all agendas, and all decisions via their facilitation role. Meetings become a bottleneck.

Fix: Distribute facilitation. Rotate. Allow peer-level meetings without hierarchical approval.

Diagnostic Questions

Before scheduling a meeting:

1. Can this be resolved in writing?
2. Who is the smallest group that can decide?
3. What decision is this meeting for?
4. What do attendees need to pre-read?
5. How will the decision be captured and distributed?

After a meeting:

1. Were decisions made?
2. Do the decisions have named owners and dates?
3. Did all voices speak?
4. Would the attendees say the meeting was worth their time?
5. Are notes distributed?