Marketing Project Management

Marketing Project Management

Overview

This skill covers how to structure, prioritize, plan, and execute marketing work effectively — including team organization, planning cadences, stakeholder management, prioritization frameworks, meeting hygiene, and execution velocity. All practices are sourced exclusively from Exit Five podcast guests across 32 episodes. Do not supplement with general knowledge not represented here.

Planning Cadences and Goal-Setting

Annual and quarterly planning structure

When helping users build a planning cadence, recommend a multi-level structure: annual strategic goals, quarterly deliverables, monthly check-ins, and weekly project tracking for high-impact initiatives. Annual OKRs should be approximately 90% locked for the year, with quarterly flexibility to adjust specific deliverables. (Source: Shane Murphy, Episode #173)

For cross-functional alignment, recommend breaking annual goals into quarterly must-haves, should-haves, and nice-to-haves — and explicitly confirming that downstream teams have prioritized the same must-haves, not just the marketing team. This prevents heavy-lift projects from being deprioritized by easier work elsewhere. (Source: Mychelle Mollot, Episode #182)

For quarterly planning specifically, recommend creating detailed roadmaps with specific monthly milestones per work stream, followed by a postmortem at quarter's end to assess outcomes, identify what went off track, and understand mitigating factors. Frame this as borrowed from product management. (Source: Kady Srinivasan, Episode #276)

(Note: the choice between formal OKR frameworks and simpler priority systems is contested — see Where Experts Disagree)

Goal simplicity and ownership

Every goal must have a named owner — a specific person or team driving toward it. Goals without owners are not goals. (Source: Amrita Mathur, Episode #188)

When testing new initiatives, pair outcome goals with explicit learning goals. This reframes experiments as learning opportunities rather than failures if the outcome metric isn't hit. (Source: Amrita Mathur, Episode #188)

Apply the napkin test: if all your goals don't fit on a napkin or postcard, you have too many or they're too complex. Force prioritization until the entire company can remember and rally around the goals. (Source: Dave Gerhardt, Episode #188) (Note: this is contested — see Where Experts Disagree)

Identify the 3 vital priorities that will drive business outcomes. The other work will happen anyway. If one of the vital three doesn't happen, everyone notices; if number 997 doesn't happen, no one notices. (Source: Peter Mahoney, Episode #128)

Assigning ownership early

Assign specific people ownership of each major goal, initiative, or campaign early in the planning process — not after the plan is written. This surfaces capacity gaps and prevents initiatives from falling through the cracks. (Source: Rowan Tonkin, Episode #197)

Marketing calendar alignment

Build a single-page document that maps business goals to marketing campaigns with a full-year timeline view. Include evergreen (always-on, automated) campaigns alongside seasonal and strategic campaigns. This allows the team to see the entire year at a glance and make trade-off decisions when new requests arrive. (Source: Hannah Rankin, Jessica Skovira, Dave Gerhardt, Episode #210)

Align the marketing calendar with the product roadmap. Work with the product team to understand what's shipping and when, then design marketing moments and campaigns around those releases. (Source: Dave Gerhardt, Episode #123)

Schedule 1–2 major product or marketing moments per year (or quarterly for fast-moving companies) as pre-calendared "lightning strikes" — forcing functions where marketing commits to a launch date, product commits to shipping something meaningful, and sales prepares to capitalize on demand. This prevents budget from being spread thin and creates predictable moments of company-wide focus. (Source: Kyle Coleman, Episode #123)

Establish a predictable monthly rhythm for launches, content drops, or marketing initiatives on a fixed date (e.g., first Tuesday of every month). Not every moment needs new product — some can be content, events, or repackaged features. The fixed date creates a forcing function for both product and marketing teams. (Source: Dave Gerhardt, Episode #123)

Team Structure and Organization

Squad-based team structure

Organize the marketing team into cross-functional squads, each focused on a specific motion or stream (e.g., paid squad, product launch squad, SEO squad). Each squad includes all necessary functions — design, dev, content, etc. — and meets weekly. Maintain a shared project management board (e.g., Asana) per squad with quarterly projects. This reduces handoffs between siloed functions and enables faster execution. (Source: Sylvia Lepoidevin, Episodes #283 and #199)

Rebrand-specific team structure

For rebrand execution, establish a small core decision-making group of 4–6 people including the CEO, marketing leader, brand strategist, and operational representatives. Avoid all-executive councils disconnected from frontline teams. Conduct comprehensive research interviews across all departments and customers upfront, then use checkpoint meetings to bring broader stakeholders in for feedback without slowing core decision-making. (Source: Clare Schmitt, Episode #333)

Once rebrand strategy and creative assets are finalized, transition to a dedicated project manager as the single point of contact for all departments requesting rebrand assets. The PM should be detail-oriented, spreadsheet-driven, and responsible for tracking every asset change — from office signage to sales decks to email templates. This separates strategic decision-making from execution logistics. (Source: Clare Schmitt, Episode #333)

For established companies with $50M+ in revenue that have been in business at least 5 years, budget 6–9 months for a full rebrand from RFP to launch. Startups and smaller companies can move faster (3 months is possible), but established companies need the longer timeline to manage complexity and ensure proper adoption. (Source: Clare Schmitt, Episode #333)

Fractional CMO operating model

Structure fractional CMO work similarly to a full-time role: set OKRs, run regular standups, manage team alignment, and oversee agencies. The key difference is efficiency — fewer hours, full-time value. Prioritize meeting hygiene to avoid spending all available hours in meetings. This model works best with smaller teams that need strategic direction and coordination. (Source: Amanda Goetz, Episodes #244 and #158)

Prioritization Frameworks

Filtering work against goals

Create 1–2 ambitious but achievable high-level marketing goals specific enough to act as guardrails (e.g., "break the perception that we're marketing-only and SMB-only"). Every project should be assessable against these goals. This prevents the need for constant top-down approval and helps teams say no to work that doesn't ladder up — even if that work would generate leads or other metrics. (Source: Dmitry Shamis, Episode #238) (Note: this is contested — see Where Experts Disagree)

Build a decision-making framework that evaluates all ideas against two criteria: (1) Is it unique — does it stand out from what competitors are doing? (2) Is it valuable — does it help the audience, or is it just self-promotional? Make this framework specific to your brand and mission. Use it as a rulebook that lets you say no without debating whether an idea is "good" or "bad." Teach it explicitly to your team and CEO so they self-filter ideas before bringing them to you. (Source: Natalie Marcotullio, Episode #194) (Note: this is contested — see Where Experts Disagree)

Establish clear North Star metrics and quarterly OKRs at the company level, then use these as the decision-making framework for prioritizing requests to shared resource teams (like creative/brand). Hold weekly syncs where focus team leaders debate prioritization against committed goals. This removes emotion and prevents the "who bangs the table loudest" dynamic from driving resource allocation. (Source: Jason Lyman, Episode #263)

Saying no to leadership and managing requests

Use a structured three-step process when leadership proposes new marketing work:

1. Ask the Why — ask where the idea came from and why it's a priority right now (often it's not urgent, just exciting).
2. Swap It Out — if it is truly a priority, show what existing work would be deprioritized. Make clear it's an "or" situation, not an "and."
3. Let's Experiment — if they're committed, propose a small, bounded test with defined success criteria rather than full commitment.

This eliminates opinion-based arguments and grounds decisions in data and constraints. (Source: Natalie Marcotullio, Episode #194) (Note: this is contested — see Where Experts Disagree)

Maintain a shared document with your CEO where they can log ideas, requests, and questions instead of sending random Slack messages or emails. Review the doc before one-on-one meetings and come prepared with data, context, and rationale. This eliminates in-the-moment decision-making pressure and allows you to ground your "no" in evidence rather than opinion. (Source: Natalie Marcotullio, Episode #194)

Use the "three mentions" rule to triage founder ideas: only act on an idea if the founder mentions and follows up on it three times. If they mention it once or twice and don't follow up, it's likely a passing thought. This prevents wasting resources on ideas that seemed important in the moment but aren't actually strategic priorities. (Source: Danielle Messler, Episode #169) (Note: this is contested — see Where Experts Disagree)

When leadership or team members suggest ideas outside of planning cycles, respond with: "I'll add this to our backlog of ideas. We're reviewing them next Friday. Join the meeting if you want." This prevents reactive pivots while still capturing ideas and showing respect for the suggestion. (Source: Adam Goyette, Episode #164) (Note: this is contested — see Where Experts Disagree)

Create a centralized database (e.g., Notion) where all CEO and founder ideas are captured and explicitly prioritized by discipline (separate databases for product marketing, demand gen, brand, etc.). Groom this backlog on a regular cadence like a software team would. When the CEO proposes a new idea, use this system to show them what existing work it would displace. The CEO can still override and shuffle priorities — but the trade-offs become visible. (Source: Brian Kotlyar, Episode #118) (Note: this is contested — see Where Experts Disagree)

True prioritization

True prioritization is not ranking all ideas 1–100. It is identifying a clear cutoff line and intentionally not pursuing important or good ideas below that line. This requires discipline to say no to genuinely valuable work. (Source: Matt Devincentis, Episode #260)

Protecting team focus

As a leader, position yourself in the middle to receive incoming requests, assess their true priority (P0 vs. lower), and filter what actually reaches your team. Not every urgent request needs to cascade to your entire team. This protects focus and prevents constant context-switching. (Source: Matt Devincentis, Episode #260)

When new requests arrive, don't just say yes or no. Facilitate a trade-off conversation: "If we do this, it means we're deprioritizing X or Y." This allows leadership and stakeholders to make informed decisions and understand the cost of new requests. It also prevents the team from being seen as blockers. (Source: Hannah Rankin, Episode #210)

Meeting Hygiene and Communication Cadence

Async vs. synchronous defaults

Replace recurring meetings that exist primarily to share information or updates with asynchronous video recordings (e.g., Loom). Monthly metrics reviews, status updates, and one-way information sharing can be recorded once and consumed on-demand. Reserve real-time meetings for situations requiring debate, conflicting ideas, or decisions that need to be made together. This is particularly valuable for distributed/global teams across time zones. (Source: Matt Devincentis, Episode #260) (Note: this is contested — see Where Experts Disagree)

Use a meeting management tool like Fellow to allow team members to asynchronously add agenda items throughout the week. Status updates go into the tool and are reviewed offline by the manager before the meeting; discussion items (problems, challenges, opportunities) are reserved for synchronous time. (Source: Mychelle Mollot, Episode #182) (Note: this is contested — see Where Experts Disagree)

Structured synchronous cadences

Create a document that each marketing leader fills out weekly with: (1) top priorities for the week, (2) problems they want to discuss, and (3) asks of other team members. Use this to drive a 30-minute weekly marketing leadership meeting. Every other week, address the document synchronously to resolve problems and cross-team asks; on alternate weeks, address it asynchronously and spend meeting time reviewing progress against quarterly KPIs. (Source: Ruth Zive, Episode #175) (Note: this is contested — see Where Experts Disagree)

Weekly alignment tools

Create a centralized document or dashboard listing the top 3–5 priorities for the week, broken down by team member or function. Include both planned work tied to campaigns and a miscellaneous section for inevitable ad-hoc requests. Review this at the start of each week so all team members understand what others are working on and how their work contributes to goals. (Source: Hannah Rankin, Episode #210)

Imposter syndrome and project management

When facing imposter syndrome about not knowing a specific marketing discipline, lean into being the person who makes meetings happen, pulls the right people into the room, takes notes, creates tracking mechanisms (Slack channels, action items), and ensures execution. You don't need to be the expert; you need to be the person who drives it forward. (Source: Priscilla Barolo, Episode #302)

Intake, Requests, and Workflow Management

Formal intake processes

Establish a rule that all requests from sales, leadership, or other departments must be submitted through a centralized channel (e.g., Slack channel, form, project management tool) rather than direct messages or ad-hoc asks. This ensures visibility across the marketing team, allows leadership to see the full request load, and enables group-level trade-off conversations about priorities. Without this, one-off requests fragment the team and derail planned work. (Source: Hannah Rankin, Episode #210)

Templates for recurring motions

Create standardized templates for recurring marketing activities (e.g., webinars, field events, email campaigns, landing pages). Document the steps, timeline, and requirements once, then reuse and iterate. This reduces decision fatigue, accelerates execution, enables team members to self-serve without micromanagement, and creates a training tool for onboarding. Review and refine templates regularly with the team to remove friction and unnecessary steps. (Source: Hannah Rankin, Jessica Skovira, Dave Gerhardt, Episode #210)

Identifying and systematizing busy work

Busy work consists of regularly scheduled, predictable activities where you know exactly what will happen after completion — e.g., webinars that always get cut into clips, turned into social posts, and spawned into blog posts. These tasks are so routine that their downstream work should be anticipated and planned for. Recognizing this pattern helps distinguish between necessary work and work that should be systematized, automated, or eliminated. (Source: Dmitry Shamis, Episode #238)

Experimentation frameworks

Establish a dedicated idea board (e.g., in Asana) where team members submit marketing ideas continuously. Once per month, hold a Friday afternoon meeting where everyone pitches their ideas. Select at least two ideas per two-week sprint to test, ensuring ideas are tied to specific KPIs or OKRs. This creates a structured funnel for experimentation without requiring ideas to be perfect before testing. (Source: Adam Goyette, Episode #164)

When launching new creative or campaigns, frame them as tests to bypass lengthy approval processes. By calling something a test, you can launch faster, get real data, and iterate. The test framing is honest — you genuinely don't know if it will work until you launch it. (Source: Adam Goyette, Episode #164) (Note: this is contested — see Where Experts Disagree)

Execution Quality and Velocity

Shipping speed

Rather than perfecting each marketing initiative before launch, commit to shipping work at 80% completion. This applies to landing pages, emails, creative, and campaigns. The goal is to maintain velocity, get real feedback from the market, and iterate quickly. Establish a team cadence (e.g., one large, one medium, one small project per month) and stick to it. This is especially critical in early-stage companies where speed and momentum compound. (Source: Eli Rubel, Episode #120) (Note: this is contested — see Where Experts Disagree)

Upfront process investment

Avoid spontaneous brainstorming meetings. Instead: (1) define guardrails upfront — deadline, budget, look/feel, what good/bad looks like, relevant examples; (2) create a brief with 3–5 reference examples of what you like and why; (3) let the brief marinate for a day or two rather than expecting ideas in real-time; (4) use time-blocking (e.g., 1–2 hour focused blocks) to execute on ideas after they've had time to develop; (5) be willing to generate bad ideas first to get the flow going. Deadlines and constraints force better decisions than open-ended creative freedom. (Source: Dave Gerhardt, Episode #214) (Note: this is contested — see Where Experts Disagree)

As a solo marketer working with freelancers, invest time in creating comprehensive briefs that explain context, goals, and expectations. This reduces friction and allows freelancers to work more independently and efficiently. (Source: Sara Lattanzio, Episode #268) (Note: this is contested — see Where Experts Disagree)

Stakeholder alignment before creative work

Early in a creative engagement, explicitly ask who could derail the project with late-stage opinions or objections. Ask directly: "Who could screw this up for all of us? Who's going to be the one who has strong opinions that gets clued in late in the game?" This surfaces hidden stakeholders before they become project grenades halfway through. (Source: Eli Rubel, Episode #153)

If you hire an outside creative expert or agency and pay a premium for their work, trust them to do their job. Set clear expectations upfront via the brief and stakeholder alignment, then get out of the way. The marketer's role is to provide timely, specific feedback and make decisive go/no-go calls, not to direct the creative process. (Source: Eli Rubel, Episode #153)

Decision-making culture

After a decision is made on a marketing initiative, require team members to commit to the decision even if they disagreed during the feedback phase. Explicitly discourage throwing rocks at ideas behind closed doors or withholding commitment after a decision is finalized. Set a clear decision deadline and move forward as a unified team. (Source: Dave Gerhardt, Episode #141)

For complex decisions like pricing and packaging, explicitly define who is the approver, who are the advisors/council, and who are the informed parties using a RACI-style framework. This prevents decision paralysis by separating voices that have weight in the decision from voices that provide input. (Source: Shane Murphy, Episode #173)

Calendar blocking

Block out large chunks of time on your calendar at the start of each quarter, month, or week for major projects and OKRs. This makes your capacity visible and prevents you from saying yes to new requests that would overlap with committed work. For recurring tasks, establish a fixed time window and communicate it to your team so they know when to expect deliverables and when you're unavailable. (Source: Natalie Marcotullio, Episode #194)

Teach your framework to your team

Explicitly teach your team and CEO your decision-making framework and the three-step no process. When team members bring ideas, practice the framework out loud with them. Over time, team members will internalize the framework and start self-filtering ideas before bringing them to you. This distributes the decision-making burden and prevents burnout. (Source: Natalie Marcotullio, Episode #194)

AI and Tools for Marketing Operations

AI for execution bottlenecks

Use AI to automate tedious, time-consuming work that drains mental energy — the "dirty work" that takes hours but doesn't require human judgment. Do not use AI to outsource thinking, strategy, or creative direction. AI lacks lived experience and observational skills, so output is mediocre without human curation. Use AI to speed up research, generate templates, or handle repetitive tasks so humans can focus on taste-making, strategy, and authentic creative work. (Source: Dmitry Shamis, Episode #238)

AI for meeting preparation

Before attending a meeting, upload relevant materials (proposals, decks, vendor information) to a secure AI tool and ask it to generate questions you should ask, identify what you might be missing, or surface competitor information. This accelerates meeting prep and allows you to enter meetings more informed. (Source: Jessica Hreha, Episode #136)

Use AI to help with data analysis, summarization, and presentation preparation for quarterly business reviews (QBRs). This can reduce the time spent on QBR prep and improve the quality of insights presented. (Source: Jessica Hreha, Episode #136)

Project management tools

Implement a project management tool (Monday, Asana, ClickUp) where all event or campaign tasks live in one place, with clear assignment, due dates, and ownership. Pair this with a "key info doc" (a Google Sheet or similar) that serves as the source of truth for all event information that people reference repeatedly. (Source: Kera Wright, Episode #124)

Event and Campaign Execution

Event planning

Rather than discussing event ideas indefinitely, pick a concrete date and book the venue immediately (even with a deposit) to create a forcing function. All other decisions — marketing timeline, speaker sourcing, logistics — flow from that fixed deadline. (Source: Dave Gerhardt, Episode #147)

Consciously decide which 1–2 moments at your event will be the primary focus of your effort and quality investment, and accept that other aspects won't be perfect. This prevents burnout and allows you to deliver excellence where it matters most to your audience. (Source: Kera Wright, Episode #124)

Post-event follow-up

Do not assume sales or content teams will own post-event follow-up. Assign a dedicated person (ideally from marketing) to manage all follow-up activities, monitor analytics daily, track which prospects have been contacted, and ensure follow-up is actually happening. This prevents leads from going stale and ensures consistent execution. (Source: Stephanie Christensen, Episode #227)

Where Experts Disagree

1. Should early-stage or small marketing teams use formal OKR frameworks or simpler priority systems?

Support summary: 3 vs 2

Position A — Use formal OKR frameworks: Formal OKR frameworks with annual goals broken into quarterly deliverables and monthly check-ins provide the structure needed for accountability and cross-functional alignment. Even complex must/should/nice-to-have breakdowns within OKRs are worth the overhead because they prevent misalignment between teams.

• Shane Murphy (Episode #173) recommended a multi-level planning cadence: annual OKRs with ~90% locked strategic initiatives, quarterly deliverables, monthly check-ins, and weekly project tracking for high-impact projects.
• Mychelle Mollot (Episode #182) recommended 5–6 broad annual goals broken into quarterly must-have, should-have, and nice-to-have OKRs, with explicit cross-team prioritization to prevent downstream misalignment.
• Kady Srinivasan (Episode #276) advocated for quarterly roadmaps with monthly milestones and quarterly postmortems, borrowed from product management, to create accountability and enable course-correction.

Position B — Use simpler priority systems: Formal OKR frameworks are too complex for early-stage companies and even mature teams. A simple P0/P1 stack-ranked system or napkin-test goals are more actionable, easier to communicate, and more likely to be remembered and executed.

• Amrita Mathur (Episode #188) explicitly recommended a P0/P1 priority system over complex OKR frameworks for early-stage companies: 3–5 tangible priorities per quarter with numbers and clear owners.
• Dave Gerhardt (Episode #188) argued that if goals don't fit on a napkin or postcard, they're too complicated. Explicitly said "avoid getting married to frameworks like OKRs" and focus on clarity and simplicity instead.

Context dependency: Amrita Mathur and Dave Gerhardt explicitly frame the simple approach as suited for early-stage companies, while Shane Murphy and Mychelle Mollot appear to be advising more mature organizations. However, Dave Gerhardt's napkin test is framed as a universal principle — not stage-specific — creating genuine tension with the formal OKR advocates.

Why it matters: Choosing the wrong planning framework wastes significant time on process overhead that could go to execution, or alternatively leaves teams without enough structure to stay aligned.

2. Should you act on leadership or founder ideas quickly, or systematically defer and filter them?

Support summary: 4 vs 2

Position A — Defer and filter systematically: Do not act on leadership ideas immediately. Use structured systems — backlogs, review meetings, three-mentions rules, or three-step no processes — to filter which ideas are genuine priorities versus passing thoughts before committing resources.

• Danielle Messler (Episode #169) recommended the "three mentions" rule: only act on an idea if the founder mentions and follows up on it three times.
• Adam Goyette (Episode #164) recommended deferring ad-hoc ideas to structured weekly review meetings rather than committing immediately.
• Natalie Marcotullio (Episode #194) recommended a three-step no process (ask why, swap it out, experiment) and a shared CEO one-on-one doc to batch and prepare responses to ideas rather than reacting in the moment.
• Brian Kotlyar (Episode #118) recommended a structured Notion backlog system groomed weekly where CEO ideas are captured and prioritized by discipline, making trade-offs visible before committing to execution.

Position B — Use a goals framework to self-filter in real-time: Rather than deferring ideas to review cycles, build a clear goals framework that allows you and your team to evaluate ideas in real-time against whether they are unique and valuable. This enables faster decisions without needing to wait for a scheduled review.

• Dmitry Shamis (Episode #238) recommended setting 1–2 high-level goals specific enough to act as guardrails so team members can make independent decisions without constant top-down approval cycles.
• Natalie Marcotullio (Episode #194) also recommended a "unique + valuable" framework that allows real-time filtering of ideas — complementing but partially in tension with her own three-step deferral process.

Context dependency: The defer-and-filter approach may be more important in organizations where leadership generates high volumes of ideas. The real-time framework approach assumes a stable, well-understood strategic direction that not all companies have. Note that Natalie Marcotullio appears on both sides, suggesting these approaches may be complementary rather than mutually exclusive in practice.

Why it matters: How you handle leadership ideas determines whether your team maintains strategic focus or gets pulled into reactive execution — the wrong approach either alienates leadership or destroys planned work.

3. Should you ship marketing work at 80% done, or invest in quality and proper process before launching?

Support summary: 3 vs 2

Position A — Ship at 80%: Ship marketing work at 80% completion to maintain velocity, gather real market feedback faster, and iterate. Waiting for perfection slows momentum and delays learning. Speed compounds, especially at early-stage companies.

• Eli Rubel (Episode #120) explicitly recommended shipping at 80% done for landing pages, emails, creative, and campaigns. Argued that speed and momentum compound at early-stage companies and that real feedback beats internal polish.
• Adam Goyette (Episode #164) recommended labeling initiatives as "tests" to bypass lengthy approval processes and launch faster, getting real data before iterating.

Position B — Invest in upfront process and quality: Proper upfront process — detailed briefs, stakeholder alignment, structured brainstorming with guardrails, and time for ideas to marinate — produces better output and reduces costly rework. Rushing to ship without this foundation leads to mediocre work.

• Eli Rubel (Episode #153) recommended identifying hidden stakeholders before starting creative work and trusting creative experts to execute after proper setup — implying upfront investment in process prevents downstream problems.
• Dave Gerhardt (Episode #214) recommended structured campaign brainstorming with upfront guardrails, reference examples, and letting briefs marinate for a day or two rather than expecting ideas in real-time.
• Sara Lattanzio (Episode #268) recommended investing time in comprehensive briefs for freelancers to prevent back-and-forth and improve output quality.

Context dependency: The 80% shipping advice is explicitly framed for early-stage companies, while the process-first advice may apply more to established teams working with agencies or freelancers. Notably, Eli Rubel appears on both sides across two different episodes, suggesting even the same expert holds tension between these positions depending on context.

Why it matters: The choice between shipping fast and investing in upfront process directly affects both output quality and team velocity — getting the balance wrong either kills momentum or produces work that damages brand credibility.

4. Should status updates and information sharing happen asynchronously, or in structured synchronous meetings?

Support summary: 3 vs 2

Position A — Default to async for status updates: Status updates, information sharing, and one-way communication should be handled asynchronously (via Loom videos, shared docs, or tools like Fellow). Reserve synchronous meeting time exclusively for debate, conflict resolution, and decisions that require real-time interaction.

• Matt Devincentis (Episode #260) explicitly recommended replacing recurring status and information-sharing meetings with async Loom recordings, reserving real-time meetings only for debate and decision-making.
• Mychelle Mollot (Episode #182) recommended using Fellow so status updates are reviewed asynchronously before meetings, with synchronous time reserved for discussion items like problems and challenges.

Position B — Use structured synchronous cadences for alignment: Regular synchronous meetings — weekly leadership priority reviews, weekly squad syncs, and structured one-on-ones — are essential for team alignment, accountability, and surfacing blockers. These should not be replaced by async communication.

• Ruth Zive (Episode #175) recommended a weekly 30-minute synchronous marketing leadership meeting driven by a shared priorities document, with alternating weeks for synchronous problem-solving and async KPI review.
• Sylvia Lepoidevin (Episodes #283 and #199) recommended squad-based team structure with dedicated weekly synchronous meetings for each squad to reduce handoffs and enable faster execution.
• Amanda Goetz (Episodes #244 and #158) recommended running regular standups and OKR reviews as part of a fractional CMO operating model, treating them as essential to team alignment rather than overhead to eliminate.

Context dependency: Async-first approaches are more practical for distributed/global teams across time zones (as Matt Devincentis explicitly notes), while synchronous cadences may be more important for co-located or smaller teams. However, the disagreement about whether status updates belong in meetings is genuine regardless of team distribution. Note that Mychelle Mollot's Fellow recommendation is a hybrid — async prep feeding into synchronous discussion — which may represent a middle path.

Why it matters: The choice between async and sync defaults directly affects team calendar load, focus time, and whether alignment actually happens — defaulting to the wrong mode either wastes hours in unnecessary meetings or creates information silos.

What NOT To Do

• Don't let all-executive councils make rebrand decisions. Large executive groups disconnect from frontline teams and slow decision velocity. Keep the core decision-making group to 4–6 people. (Source: Clare Schmitt, Episode #333)

• Don't act on every leadership idea immediately. Reacting in the moment — especially when tired — leads to saying yes to work that isn't actually a priority. Use structured systems to filter ideas before committing resources. (Source: Natalie Marcotullio, Episode #194; Brian Kotlyar, Episode #118; Danielle Messler, Episode #169)

• Don't let requests arrive via direct messages or ad-hoc asks. Without a formal intake process, one-off requests fragment the team and derail planned work. All requests should go through a centralized channel. (Source: Hannah Rankin, Episode #210)

• Don't use AI to outsource strategic thinking or creative direction. AI lacks lived experience and observational skills. Output is mediocre without human curation. Use AI for execution bottlenecks, not for thinking. (Source: Dmitry Shamis, Episode #238)

• Don't hold meetings for information sharing. One-way communication and status updates should be async. Synchronous time is too valuable to spend on updates that could be a Loom or a shared doc. (Source: Matt Devincentis, Episode #260) (Contested — see Where Experts Disagree)

• Don't leave goals without owners. Goals without a named owner are not goals. Every goal must belong to a specific person or team. (Source: Amrita Mathur, Episode #188)

• Don't attempt to make every aspect of an event flawless. Consciously choose 1–2 key moments to invest in and accept that other aspects won't be perfect. Trying to perfect everything leads to burnout and diffused effort. (Source: Kera Wright, Episode #124)

• Don't assume sales will own post-event follow-up. Assign a dedicated marketing person to own it and monitor execution daily. (Source: Stephanie Christensen, Episode #227)

• Don't run spontaneous brainstorming meetings. Without upfront guardrails, reference examples, and time for ideas to marinate, real-time brainstorming produces weak creative output. (Source: Dave Gerhardt, Episode #214) (Contested — see Where Experts Disagree)

• Don't micromanage creative experts after hiring them. Set clear expectations upfront, then get out of the way. Micromanaging suffocates good work and results in mediocre output. (Source: Eli Rubel, Episode #153)

• Don't allow post-decision sabotage. Once a decision is made, require commitment from all team members even if they disagreed during the feedback phase. Revisiting finalized decisions kills momentum. (Source: Dave Gerhardt, Episode #141)

• Don't spread marketing budget across too many moments. Identify 1–2 major "lightning strike" moments per year and concentrate resources there rather than peanut-butter spreading across many smaller initiatives. (Source: Kyle Coleman, Episode #123)

• Don't treat busy work as unavoidable. Predictable, recurring tasks with known downstream work should be systematized, automated, or eliminated — not repeatedly surprised by. (Source: Dmitry Shamis, Episode #238)

• Don't get married to complex frameworks if your team is early-stage. If goals don't fit on a napkin, they're too complicated. Simplicity is a sign of clarity. (Source: Dave Gerhardt, Episode #188) (Contested — see Where Experts Disagree)

Sources