Meeting Design And Facilitation

Meeting Design and Facilitation

Overview

This skill covers how to design, structure, and facilitate effective meetings for B2B marketing teams—including recurring leadership meetings, cross-functional syncs, one-on-ones, and the async communication patterns that should replace unnecessary meetings. All practices are sourced exclusively from Exit Five podcast guests across 5 episodes. Do not supplement with general knowledge; if a topic is not covered here, acknowledge the gap rather than fill it.

Async vs. Sync: The Foundational Decision

Before designing any meeting, help the user determine whether synchronous time is warranted at all.

Reserve synchronous meetings for two purposes only (Note: this is contested — see Where Experts Disagree):

1. Sparring — real-time back-and-forth collaboration between equals to test ideas, get feedback, and sharpen thinking
2. Connection — building trust and rapport through conversation

Move everything else to async. Status updates, project progress, and information sharing should be handled via Confluence pages, Loom videos, Jira Goals updates, or Slack messages unless there is a genuine need for real-time dialogue. (Source: Ashley Faus, Episode #264)

Adopt bursty communication patterns. Structure team communication in bursts: periods of intense, rapid back-and-forth (sparring, real-time collaboration) followed by quiet periods for deep individual work. Teams that talk a lot, get fast responses, then go quiet to execute are the most successful and productive. Prevent constant context-switching by protecting deep async work time. (Source: Molly Sands, Episode #264)

Async Tools to Recommend

• Jira Goals for tweet-length async status updates: include what shipped, what's blocked, and what's coming. Link to a Confluence page for anyone who wants more context. This keeps status updates out of meetings entirely. (Source: Ashley Faus, Episode #264)
• Weekly Loom check-in videos (Friday morning cadence) structured as: (1) accomplishments from the week, (2) shout-outs for great work, (3) top-of-mind items or upcoming priorities. Keep it concise; include a written summary or transcript so people can skim. (Source: Molly Sands, Episode #264)
• Loom with emoji reactions to enable async feedback without a meeting. Emoji reactions signal understanding, agreement, confusion, or concern—giving the sender a sense of how the message landed without requiring synchronous time. (Source: Molly Sands, Episode #264)

Recurring Meeting Cadence and Structure

Leadership and Team Meeting Rhythms

Weekly leadership meeting with a running document. Run a weekly meeting with all direct reports using a running Notion document with toggles for each week's agenda. Start with topics top of mind for the CMO or marketing leader, then have the team add items. Keep it free-flowing—no pre-prepared decks. Separate numbers review into a dedicated weekly pipeline call on the same day, with sales leadership and RevOps present. This avoids spending half the week preparing for a meeting while maintaining alignment. (Source: Kelly Cheng, Episode #297)

For remote teams, establish a tiered meeting structure:

• Weekly leadership meetings with broad participation (not just direct reports, but regional and functional leaders)
• Monthly all-hands including BDRs and junior staff
• Variable one-on-one cadence based on seniority (see Where Experts Disagree for contested guidance on this)
• Supplement with async updates (PowerPoint decks, Slack messages) for leaders who travel frequently

(Source: Priscilla Barolo, Episode #302)

Establish regular operating rhythms between marketing and ops. Create a recurring meeting cadence (e.g., every Tuesday at 4pm) between marketing and ops leaders. Use these meetings to cover: big rocks and goals, team dynamics and performance, progress against goals, and tactical operational items. Start with strategic priorities before diving into operational details. A consistent rhythm prevents misalignment and keeps both teams grounded in shared objectives. (Source: Sean Lane, Episode #274)

Cross-Functional Marketing Meetings

Anchor cross-functional meetings on shared goals and blocker resolution. Structure cross-functional marketing meetings (e.g., lifecycle, product marketing, content marketing) around a shared scorecard or set of goals. Start by reviewing progress on those shared goals, then focus discussion on identifying and resolving blockers. Ask: What's blocked? Why? Can we unblock it right now? Do not spend time on status updates or reading through lists of bullets. (Source: Ashley Faus, Episode #264)

AI Learning in Team Meetings

Run weekly AI spotlights in team meetings. Dedicate time in every team meeting for one person to share what they're doing with AI. Spotlights can cover: building an agent for a specific use case, comparing outputs across different LLMs, reverse-engineering customer queries in search engines, testing specific prompts, or exploring new tools. This creates visibility into what's working, inspires cross-functional learning, and builds a culture of experimentation. (Source: Jennifer Cannizzaro, Episode #267)

One-on-One Design

Use one-on-ones to solve blockers and align on decisions, not for status updates (Note: this is contested — see Where Experts Disagree). When a direct report brings up a blocker, clarify whether they're asking for awareness or for you to take action ("shake some trees"). This prevents one-on-ones from becoming complaint sessions and keeps them focused on problem-solving. Status updates and project updates should be handled asynchronously or in group meetings. (Source: Priscilla Barolo, Episode #302)

One-on-one frequency by seniority (Note: this is contested — see Where Experts Disagree). Priscilla Barolo recommends a tiered cadence for remote teams:

• Weekly for direct reports managing large functions
• Monthly for functional leaders
• Quarterly for country/regional leads
• Twice yearly for junior employees

This prevents calendar overload while maintaining alignment. (Source: Priscilla Barolo, Episode #302)

Facilitation Techniques

Offer multiple input formats to accommodate different communication styles. Not everyone thinks best on the fly. When running meetings, provide multiple ways to participate: written comments on a page, whiteboard contributions, verbal input, and async follow-up. This ensures you hear from all personality types, not just those who think fast on their feet. (Source: Ashley Faus, Episode #264)

Run page-led meetings with async prep before sync discussion. Before a collaborative meeting, prepare a Confluence page (or whiteboard) with context, background, important perspectives, and decisions everyone needs to understand. Have team members review async and add written comments with cameras off for the first few minutes of the meeting. This ensures everyone has the same frame of reference, allows quieter team members to contribute in writing, and focuses synchronous time on discussion and problem-solving rather than information transfer. (Source: Molly Sands, Episode #264)

Facilitate by connecting individual contributions to shared goals in chat. As a meeting facilitator, when team members share work or ideas, use the chat to explicitly connect their contribution to the team's shared goals or broader context. This helps everyone understand how individual work fits the bigger picture and is especially useful for quieter team members or those less familiar with full context. (Source: Ashley Faus, Episode #264)

Use a parking lot to manage meeting scope. When relevant but off-topic ideas come up, acknowledge them and add them to a visible parking lot list. This signals that the idea is valuable without derailing the current meeting. Keep the meeting focused on its stated purpose while ensuring good ideas don't get lost. (Source: Molly Sands, Episode #264)

Rotate meeting facilitation and ownership across team members. Assign different team members to own and facilitate recurring meetings on a rotating basis. Each owner is responsible for setting the agenda, finding speakers or guests, prepping the meeting page, and facilitating discussion. This gives all team members practice with facilitation and presentation skills in a safe environment, and prevents meetings from becoming stale or defaulting to the same format every week. (Source: Ashley Faus, Episode #264)

Meeting Evaluation and Maintenance

Conduct a quarterly ritual reset to evaluate and redesign recurring meetings. Every quarter, review all recurring team meetings and ask: Is this meeting actually serving us? What is the goal of this meeting (connection, information sharing, sparring, brainstorming)? Does it change week to week? If a meeting has become stale or no longer serves its purpose, redesign it or eliminate it. This prevents teams from defaulting to generic formats (like going around saying what you're working on) that no longer add value. The Atlassian Team Playbook includes a free resource called the Ritual Reset to guide this process. (Source: Ashley Faus, Episode #264)

Where Experts Disagree

1. Should status updates be handled in synchronous meetings or asynchronously?

Support summary: 3 vs 3 — This is an evenly split disagreement among guests.

Position A: Status updates should be fully async Ashley Faus and Molly Sands (both from Atlassian) argue that status updates, project progress, and information sharing should be handled entirely asynchronously—via Confluence pages, Loom videos, Jira Goals, or Slack—and should never consume synchronous meeting time. Sync meetings should be reserved exclusively for sparring and connection. Priscilla Barolo also explicitly states that status updates and project updates should be handled asynchronously or in group meetings, while one-on-ones focus on blockers and decision-making. (Sources: Ashley Faus, Episode #264; Molly Sands, Episode #264; Priscilla Barolo, Episode #302)

Position B: Some status review warrants dedicated sync time Kelly Cheng separates numbers review into a dedicated weekly pipeline call with sales leadership and RevOps—implying that some status and numbers review warrants synchronous time. Sean Lane recommends a recurring sync meeting between marketing and ops that explicitly covers "progress against goals" and "tactical operational items"—content the async-first camp would classify as status updates. Priscilla Barolo, while advocating for async supplements, still maintains a weekly leadership meeting structure that includes alignment discussions. (Sources: Kelly Cheng, Episode #297; Sean Lane, Episode #274; Priscilla Barolo, Episode #302)

Context dependency: The fully-async position comes from Atlassian employees who work in a highly async-native culture with mature tooling (Confluence, Jira, Loom). CMOs at companies with less async infrastructure or cross-functional dependencies (e.g., sales alignment) may find dedicated sync status reviews necessary. The disagreement is genuine but may also reflect different organizational maturity levels.

Why it matters: Defaulting to sync status updates is one of the most common sources of meeting bloat. Getting this right can reclaim significant calendar time for deep work—but eliminating sync status reviews entirely requires organizational discipline and tooling that not all teams have.

When helping a user on this question: Surface both positions. Ask about their tooling maturity, team size, and cross-functional dependencies (especially with sales) before recommending a direction. Do not present the fully-async position as settled consensus.

2. How frequently should you hold one-on-ones with direct reports?

Support summary: 2 vs 1

Position A: Variable cadence based on seniority (majority position) Priscilla Barolo explicitly recommends a tiered cadence—weekly for direct reports managing large functions, monthly for functional leaders, quarterly for country/regional leads, and twice yearly for junior employees—citing calendar overload prevention as the rationale. Kelly Cheng structures her weekly leadership meeting as a group format rather than individual one-on-ones, implying that not every relationship requires a dedicated weekly one-on-one slot. (Sources: Priscilla Barolo, Episode #302; Kelly Cheng, Episode #297)

Position B: Weekly for all direct reports The weekly-for-all position is represented in the data primarily as a baseline assumption within Barolo's own framework—she recommends weekly one-on-ones for direct reports managing large functions, which could be read as a weekly-default stance for senior direct reports. However, her explicit recommendation is the tiered model, not a universal weekly cadence. (Source: Priscilla Barolo, Episode #302)

Context dependency: Barolo is explicitly discussing remote teams with geographically distributed staff. The variable-cadence approach is most relevant for large, distributed organizations. Smaller or co-located teams may find a uniform weekly cadence more practical.

Why it matters: Setting the wrong one-on-one cadence either wastes calendar time or leaves team members without sufficient support. Knowing when weekly vs. monthly check-ins are appropriate directly affects team performance and manager bandwidth.

When helping a user on this question: Ask about team size, geographic distribution, and whether the team is remote or co-located before recommending a cadence. Present the variable-cadence model as the more explicitly argued position, but note that context matters.

What NOT To Do

• Do not use one-on-ones for status updates. One-on-ones that become status report sessions waste the manager's and employee's time and prevent the meeting from serving its real purpose: solving blockers and aligning on decisions. (Source: Priscilla Barolo, Episode #302)
• Do not spend synchronous meeting time reading through lists of bullets or project updates. If the meeting is just information transfer, it should be async. (Source: Ashley Faus, Episode #264)
• Do not let recurring meetings run indefinitely without evaluation. Meetings that made sense six months ago may no longer serve their purpose. Failing to conduct a quarterly ritual reset leads to stale, low-value meetings that drain calendar time. (Source: Ashley Faus, Episode #264)
• Do not design meetings that only reward fast, verbal thinkers. Failing to offer written or async input options means you're systematically missing contributions from quieter or more reflective team members. (Source: Ashley Faus, Episode #264)
• Do not allow off-topic ideas to derail a meeting. Acknowledge them and park them; don't ignore them or let them hijack the agenda. (Source: Molly Sands, Episode #264)
• Do not prepare elaborate decks for internal leadership meetings. Pre-prepared decks for weekly leadership meetings waste preparation time and make meetings feel performative rather than collaborative. (Source: Kelly Cheng, Episode #297)
• Do not apply a one-size-fits-all meeting cadence to distributed teams. Calendar overload from excessive one-on-ones is a real risk, especially for remote leaders managing large, geographically distributed organizations. (Source: Priscilla Barolo, Episode #302)

Sources