People management and performance

People Management and Performance

Overview

This skill covers people management and performance practices for B2B marketing leaders, including hiring, delegation, feedback, meeting structure, team culture, AI adoption, and recognition. All practices are sourced exclusively from guests and hosts on the Exit Five podcast. Do not supplement with general management knowledge not represented here—gaps in coverage are intentional.

---

Hiring and Team Composition

Match hires to your company's immediate need, not a generic title. Identify what your company needs most right now (brand, demand gen, product marketing, growth) and hire someone whose core superpower aligns with that need. A brand-focused marketer will struggle with demand gen execution and vice versa. Do not hire a generalist and expect excellence across all functions. (Source: Jason Lemkin, Episode #142)

Hire specialists who are smarter than you in areas where you're weak. As a CMO, deliberately hire VPs and specialists who exceed your expertise in specific functional areas (demand gen, marketing ops, analytics). Acknowledge your gaps openly to your team and ask for master classes from your specialists. This creates a stronger overall organization and prevents you from becoming a bottleneck. (Source: Maura Rivera, Episode #301)

Hire strong functional leaders and ask them detailed questions rather than trying to be expert in every discipline. Marketing leaders do not need deep expertise in every function (PR, demand gen, BDRs, etc.). Hire excellent leaders for each function, ask them detailed questions to understand their approach and reasoning, have them re-explain concepts simply, and trust them while advocating for them. When you don't understand something, ask the leader to explain it simply, then ask follow-up questions about the underlying logic. (Source: Priscilla Barolo, Episodes #302 and #193)

Hire for extreme strengths, not absence of weakness. When building teams, prioritize people with extreme strengths in specific areas rather than people who lack obvious weaknesses. Use strengths-based frameworks (like StrengthsFinder) to identify what each person is uniquely good at, then structure the team so those strengths compound. Invest in turning your own strengths into superpowers rather than spending disproportionate time fixing weaknesses—the ROI is exponentially higher. (Source: Matt Devincentis, Episode #260)

When transitioning from Head of Content to Head of Marketing, hire a product marketer as your first direct report. This creates minimal overlap in responsibilities and ensures coverage across top-of-funnel thought leadership and product-focused messaging. Look for someone with proven experience in messaging and positioning who can simplify complex product stories while maintaining brand personality. (Source: Jess Cook, Episode #266)

Calibrate whether you need to upgrade a team member by meeting peer-level talent informally. Go meet five peer-level professionals (e.g., five VPs of Corporate Communications) without a formal job opening or interview process. Have coffee and ask yourself: if you had someone at that level, would your life change? If yes, consider making a move. If no, keep your current person. This is a low-friction way to assess whether a capability gap is real or whether you're experiencing loyalty bias. (Source: Dave Kellogg, Episode #342)

Use direct CMO LinkedIn outreach for recruiting. When recruiting for open roles, have the CMO directly message candidates on LinkedIn with a simple, direct message (e.g., "I'm hiring this role") rather than relying solely on recruiter outreach. This generates significantly higher response rates because a message from a prospective direct manager carries more weight than generic recruiter contact. (Source: Sylvia Lepoidevin, Episodes #283 and #199)

Allocate approximately 25% of leadership time to continuous recruiting and relationship building. Dedicate roughly 10 hours per week to recruiting and nurturing relationships with potential future hires, even when not actively hiring. This includes coffees, lunches, and networking to build a pipeline of talent. The best leaders maintain this discipline consistently so they have their pick of top talent when a role opens. This is an ongoing leadership responsibility, not a one-time hiring activity. (Source: David Kline, Episode #138)

Eliminate low-value work before hiring to solve an overwork problem. Before hiring to address capacity issues, audit your current work to eliminate unprofitable or low-value activities. Only hire after you've streamlined and confirmed the need is real. (Source: David Kline, Episode #138)

---

Delegation and Autonomy

Delegate challenges to your team rather than solving problems yourself. Resist the urge to solve problems yourself even when you could do it faster. Present challenges to your team and ask them to research, develop recommendations, and come back with proposals. This develops team capabilities, builds confidence, and prevents you from becoming a bottleneck. Your role shifts from executor to coach and decision-maker. (Source: Maura Rivera, Episode #301)

Delegate by co-creating expectations rather than prescribing steps. When delegating, align on the "what" (the outcome and goals) rather than the "how" (specific steps). Have a conversation where the person articulates back how they plan to approach the work. This co-authorship of expectations creates ownership and agency. Ask clarifying questions to understand their thinking, but allow them to execute their way rather than yours. (Source: David Kline, Episode #138)

Hand off ownership gradually while remaining involved in feedback and direction. When delegating a function to a team member, do not fully step away immediately. Remain involved by providing feedback, asking questions, and occasionally diving into the work to understand what's happening. Give the team member autonomy to execute and ship without waiting for approval, but stay informed enough to provide guidance and catch issues early. This is strategic oversight, not micromanagement. (Source: Dave Gerhardt, Episode #143)

Default to autonomy; micromanage only as an exception. Hire mature, capable people and trust them to do their work. Avoid micromanaging as a default. When you feel the urge to micromanage a detail, step back and remind yourself that you hired them because you trust them. Micromanagement should be the exception (e.g., when there is a specific concern), not the norm. (Source: Dave Gerhardt, Episode #169)

Teach the rules of the game rather than dictating execution. Establish clear rules for your team: budget constraints, target customer definitions, overarching goals, and success metrics. Then coach team members on how to play within those rules rather than dictating specific tactics or approving every decision. This scales leadership, enables team autonomy, and creates space for team members to discover and execute ideas the leader never initiated. (Source: Andrew Davies, Episode #195)

Teach your team your decision-making framework so they self-filter ideas. Explicitly teach your team (and CEO) your decision-making framework. When team members bring ideas, practice the framework out loud with them: acknowledge what the idea is trying to accomplish, then explain why it does or doesn't fit. 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)

Assign individual ownership of plan initiatives and goals early in the planning process. Do not leave your marketing plan as a document owned only by the CMO. Assign specific people ownership of each major goal, initiative, or campaign early in the planning process. This ensures accountability, enables better execution tracking, and prevents initiatives from falling through the cracks. (Source: Rowan Tonkin, Episode #197)

---

Feedback and Performance Management

Explicitly communicate your feedback style to reduce misinterpretation. Identify your natural feedback style (direct and blunt, warm and connective, results-focused) and communicate it proactively to your team. Explain that your style is not a personal attack or judgment of their worth. For example: "I give direct, specific feedback quickly. If I don't like something, I'll tell you directly, but that doesn't mean I hate you or think you're bad at your job." This prevents team members from internalizing critical feedback as a reflection of their value. (Source: Dave Gerhardt, Episode #160)

Establish a regular feedback cadence so employees know where they stand. Communicate regularly with employees about their performance and standing, providing both positive and constructive feedback. Employees should not have to ask where they stand or feel uncertain about their performance. When employees respond to constructive feedback, recognize that improvement explicitly. This removes ambiguity and creates psychological safety around feedback. (Source: Rachel Weeks, Episode #273)

Document role expectations quarterly with three core documents. Maintain three written documents for each direct report: (1) a dashboard they own that updates you on their area, (2) a development plan with three bullets (gap, how to close it, how to measure), and (3) a role expectations document that specifies what success looks like and how they would exceed expectations. Review and grade these quarterly together, reconciling any differences in perception. Written documentation creates clarity that verbal conversations alone cannot achieve. (Source: David Kline, Episode #138)

Express expectations as ranges when business outcomes are ambiguous. When you cannot predict exact outcomes due to business ambiguity, express expectations as ranges rather than fixed numbers. For example, instead of "close 4 deals," say "close 3–5 deals." This acknowledges uncertainty while still providing clear direction. (Source: David Kline, Episode #138)

Diagnose underperformance using the Skill and Will framework. When someone is underperforming, work through four diagnostic questions in order: (1) Do they have the resources and tools needed? (2) Have they received adequate training and context? (3) Do they have the skill (ability) to do the job? (4) Do they have the will (motivation) to do the job? Start with will before skill—if someone doesn't want the job, training won't help. If they have both skill and will but are still struggling, consider whether an external hire could catch up in 3–6 months; if yes, it may be time to move on rather than continue investing. (Source: David Kline, Episode #138)

Coach team members on AI over-reliance by detecting it and providing direct corrective feedback. When you detect that a team member has over-relied on AI and the output is obviously AI-generated, provide direct feedback: "It was obvious that you used AI here, let's work on this." Validate your assessment by running the output back through AI to confirm it matches AI's typical patterns. Use this as a coaching moment to reinforce the importance of human judgment, editing, and strategic thinking in the AI-assisted workflow. (Source: Jennifer Cannizzaro, Episode #267)

Use AI to structure coaching feedback for junior team members without rewriting their work. When reviewing work from junior or mid-level team members, input their submission and your shorthand notes into a custom ChatGPT that understands your feedback style. Have the AI structure your feedback to explain the reasoning behind changes rather than just rewriting the work. This teaches team members your decision-making process, builds their confidence, and saves you time on one-on-one coaching. (Source: Sara Ajemian, Episode #288)

(Note: How you deliver feedback—direct directives vs. collaborative questioning—is contested. See Where Experts Disagree.)

---

One-on-Ones and Meeting Structure

(Note: The appropriate structure and purpose of one-on-ones is contested. See Where Experts Disagree.)

Use one-on-ones to solve blockers and align on decisions, not for status updates. Structure one-on-ones to focus on blockers and decision-making rather than status updates. When a direct report brings up a blocker, clarify whether they're asking for awareness or for you to take action. Status updates and project updates should be handled asynchronously or in group meetings. (Source: Priscilla Barolo, Episodes #302 and #193)

Vary one-on-one cadence by seniority and complexity. Senior leaders: weekly. Mid-level: monthly. Junior staff: twice yearly. Use one-on-ones primarily for personnel matters and issues that require private discussion. (Source: Priscilla Barolo, Episode #193)

Use a meeting management tool (e.g., Fellow) to co-create agendas and separate status from discussion. 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, while discussion items (problems, challenges, opportunities) are reserved for synchronous time. This reduces meeting interruptions and allows managers to prepare by reviewing entries in advance. (Source: Mychelle Mollot, Episode #182)

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

Maintain a weekly leadership priorities and problem-solving document. Have each marketing leader fill out a document weekly with: (1) their top priorities for the week, (2) any problems they want to discuss, and (3) any asks of other team members. Use this to drive a 30-minute weekly marketing leadership meeting. Every other week, review synchronously to address problems and cross-team asks; on alternate weeks, address asynchronously and spend meeting time reviewing progress against quarterly KPIs. (Source: Ruth Zive, Episode #175)

Conduct monthly skip-level meetings with non-direct reports. Hold monthly skip-level meetings (20–25 minutes, no agenda) with every person who does not report directly to you. When new team members join, inform them of this practice and encourage them to use the time to share feedback on how you or the company could improve, surface opportunities, or discuss challenges. This helps the CMO stay connected to ground-level insights and triangulate information from across the organization. (Source: Kelly Cheng, Episode #297)

Hold monthly office hours where any team member can book time. Establish a monthly office hours session where any team member can book 15–30 minutes to discuss anything—career development, work challenges, etc. This creates an open-door policy and helps you stay connected to your team's needs and concerns. (Source: Kimberly Storin, Episode #229)

Rotate meeting facilitation and ownership across team members. Assign different team members to own and facilitate recurring team 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. Pair this with a quarterly ritual reset to evaluate whether the meeting is still serving its purpose. (Source: Ashley Faus, Episode #264)

Accommodate different communication preferences by offering multiple input formats in meetings. Not everyone does their best thinking on the fly. When running meetings, offer multiple ways for people to participate: written comments on a page, whiteboard contributions, verbal input, and async follow-up. This ensures you're hearing from all personality types and communication styles, not just the people who think fast on their feet. (Source: Ashley Faus, Episode #264)

Send weekly Loom check-in videos with a structured format. Record a brief weekly Loom video (Friday morning is a good cadence) structured with: (1) accomplishments from the week, (2) shout-outs for great work, (3) top-of-mind items or upcoming priorities. Keep it concise and include a written summary or transcript so people can skim if they prefer. (Source: Molly Sands, Episode #264)

Establish weekly company rituals to communicate strategy, wins, and failures transparently. Create recurring company meetings (e.g., Monday all-hands to discuss weekly commitments, Friday retrospective to review wins and misses) where you openly discuss what the marketing team accomplished, what they missed, and what they learned. Encourage discussion of failures and mistakes, not just wins. Model this transparency from leadership down. (Source: Jess Cook, Episode #266)

Create a monthly forum where team members can propose and discuss new marketing ideas. Establish a monthly marketing initiatives call where team members can bring big ideas to the table without the CMO present. This creates psychological safety for idea generation and allows the team to bubble up ideas for investment. The team then brings recommendations to leadership for discussion. (Source: Kimberly Storin, Episode #229)

Hold quarterly reviews with your entire marketing team to discuss priorities and track progress. Establish a quarterly cadence where you meet with your entire marketing team to review priorities and discuss how the team is tracking against them. This ensures alignment across the organization and gives everyone visibility into what matters most. (Source: Kimberly Storin, Episode #229)

---

Leadership Style and Self-Awareness

Use a "How to Work with Me" document to set expectations with your team. Use AI (like ChatGPT with memory) to generate an honest assessment of your working style, including your strengths and blind spots. Ask the AI to tell you the "hard truths" about how you operate—not the polished version. Use this output to create a "How to Work with Me" document that you share with your team. This sets expectations upfront about your management style, communication preferences, and potential gaps, reducing friction and misalignment. (Source: Kieran Flanagan, Episode #318)

Use a personality or working-style framework to communicate how you work with your team. Use a tool like Insights Discovery or a similar framework to help your team understand how you operate, what to expect from you, and how to work best with you. You can create a simple document outlining your communication style, decision-making approach, and what works best for collaboration. (Source: Peter Mahoney, Episode #188)

Use the Push-Pull leadership model when managing large teams. Divide your leadership attention using a push-pull framework. Each quarter, explicitly identify which initiatives you will "push" on—meaning you will be deeply involved, act as a team member, and drive hard. For everything else, you "pull"—you expect team members to proactively bring issues to you when they need input, but you do not micromanage. Communicate this framework clearly so team members understand your engagement model. (Source: Kieran Flanagan, Episodes #318 and #257)

Triage fire drills and filter requests to protect team focus. Not every urgent request or fire drill needs to cascade to your entire team. Position yourself in the middle to receive incoming requests, assess their true priority, and filter what actually reaches your team. This protects focus and prevents constant context-switching. (Source: Matt Devincentis, Episode #260)

Absorb organizational noise and shield your team from uncertainty until a decision is made. Do not whipsaw your team with every strategic iteration or uncertainty you're experiencing. Keep them focused on executing the current plan until a conscious decision is made to change direction. Once a decision is made, bring them transparently into it. This prevents them from becoming your therapist and keeps them productive. (Source: David Kline, Episode #138)

Create focus for your team as a core leadership responsibility. Help people understand how to prioritize, make trade-offs, and understand your decision-making framework. Be explicit about what matters most. When teams lack focus, they get pulled in too many directions and have to do their real work after hours. Creating focus is more important than adding more meetings or communication tools. (Source: Molly Sands, Episode #264)

Create a guardrail: sleep on high-emotion decisions before acting. When you feel an urgent impulse to respond to a message, make a decision, or take action—especially when emotionally activated—implement a rule to sleep on it before responding. The stronger the urge to act immediately, the greater the need to pause. Most things can wait 24 hours. This is particularly important for impulsive decision-makers or those managing high stress. (Source: Kara Hardin, Episode #160)

Diagnose workplace friction using a three-part interaction framework. When an interaction feels smooth, sticky, or friction-filled, use this framework: (1) What am I bringing to this conversation? What are my vulnerabilities and strengths? (2) What are they bringing? What are their vulnerabilities and strengths? (3) What's happening between us—how are our styles, needs, and vulnerabilities interacting? This helps you separate what's yours, what's theirs, and what's created by the dynamic itself. (Source: Kara Hardin, Episode #160)

Assess whether you're ready to be a CMO by evaluating your willingness to coach and have difficult conversations. Before pursuing a CMO role, honestly assess whether you enjoy coaching and mentoring people and whether you're prepared to have regular difficult conversations. Many people are drawn to CMO roles for the strategic work but become miserable because they underestimate the people management burden. Approach hard conversations with the intent of making someone better at their job. (Source: Mychelle Mollot, Episode #182)

Use a Chief of Staff as an accountability check on CMO scope creep. Hire a strong Chief of Staff who can tell you when you're overstepping your role or diving too deep into execution. This relationship requires trust and directness—the Chief of Staff should feel empowered to push back when the CMO is doing work that others should own. (Source: Peter Mahoney, Episode #128)

Develop functional expertise in areas you don't manage directly through structured learning with leaders. When taking a CMO role managing functions you haven't directly handled (e.g., paid media, SEO), schedule off-the-clock learning sessions with functional leaders. Ask them to teach you what metrics matter, what roadblocks exist, what questions you should ask to help them improve, and what good performance looks like. The goal is to be a good leader who understands the business, not to become a hands-on expert in every discipline. (Source: Kelly Hopping, Episode #255)

Lead by example on operating system discipline. Model the behavior you expect from the team. Use the centralized repository, follow naming conventions, respect the intake process, and align your own work to goals. When you deviate or make mistakes, acknowledge them and correct them. This builds credibility and shows the team that the system is not optional theater. (Source: Jessica Skovira, Episode #210)

Explicitly communicate leadership aspirations to your manager to unlock development opportunities. Tell your direct manager early and clearly that you aspire to a marketing leadership role. Managers who know about your leadership ambitions will flag you as "leadership potential" and actively create opportunities for you to develop the skills needed for that role. The earlier you communicate this, the more time your manager has to intentionally develop you through stretch assignments and cross-functional exposure. (Source: Jessica Andrews, Episode #217)

---

Team Culture and Psychological Safety

Build psychological safety and process accountability for courageous marketing. Create a team culture where members have psychological safety to experiment, fail, and learn without fear of termination. Pair this with "process accountability"—teams must articulate why an experiment serves a clear goal or North Star before executing, but once approved, they have freedom to execute boldly. Leadership should actively push teams to think bigger ("10x, not 10%") and celebrate learnings from failures. (Source: Udi Ledergor, Episode #237)

Build a disagree-and-commit culture to prevent post-decision sabotage. 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)

Defend your team publicly and take responsibility for their mistakes. When something goes wrong with your team's work, publicly take responsibility rather than blaming the team member. This signals to your team that you have their back and creates psychological safety to take risks. (Source: Dan Cmejla, Episode #134)

Normalize failure by discussing what didn't work and iterating without punishment. When a team member's idea or execution doesn't work, have a conversation about why it didn't work and how to approach it differently next time. Frame this as a learning cycle, not a failure. After a few cycles of this approach, team members will feel comfortable taking risks because they see that failure is treated as information, not punishment. (Source: Dan Cmejla, Episode #134)

Establish psychological safety in team onboarding by asking how people want to be managed. During onboarding, ask team members how they want to be managed, how they prefer to receive feedback, and what challenges they face. Use this information to tailor your management approach. This early conversation signals that you care about their preferences and creates a foundation for psychological safety. (Source: Dan Cmejla, Episode #134)

Lead with vulnerability; share when you're stressed to normalize struggle for your team. As a leader, share vulnerable moments with your team. Tell them when you're stressed or overwhelmed. This sets the tone that growth is hard, struggle is normal, and it's okay to not have all the answers. This approach builds psychological safety and encourages your team to be honest about challenges rather than hiding them. (Source: Tara Robertson, Episode #188)

Frame team pushback on new initiatives as constraint-solving, not rejection. When team members push back on new ideas or initiatives, reframe the conversation from "we can't do this" to "how could we make this happen?" Ask what additional resources are needed, what else needs to pause or stop, or what the cost would be in terms of team overwork or morale. This encourages collaborative problem-solving and helps leaders understand real trade-offs. (Source: Andrew Davies, Episode #195)

Balance async work with intentional in-person gatherings. While async work eliminates unnecessary meetings, intentionally schedule in-person team gatherings (Atlassian calls these ITGs—Intentional Togetherness Gatherings) for team building, strategy planning, and relationship building. A small amount of in-person time (quarterly or similar cadence) sustains trust and camaraderie for 2–3 months of distributed async work. This is especially important for new team members. (Source: Matt Devincentis, Episode #260)

Build trust in a small, distributed team by owning visible, recurring deliverables. Establish trust by owning a few high-visibility, recurring deliverables (e.g., a monthly webinar, a twice-monthly newsletter). These create natural touchpoints where teammates see your work flowing through the system without requiring status updates or meetings. Pair this with 1–2 strategic planning meetings per year to align on big-picture priorities. (Source: Amanda Natividad, Episode #205)

Take ownership of your ideas and protect them from committee dilution. When you have conviction in an idea, present it with confidence and be prepared to defend it. Do not let feedback rounds sand it down into something generic. If leadership won't let you run with it, consider whether that's the right environment for your work. The best approach: do the work, present it boldly, and if it fails, own the failure. (Source: Harry Dry, Episode #303)

---

Recognition and Morale

Implement the "10 minutes by Friday" weekly recognition discipline. Set aside 10–15 minutes every Friday in your calendar specifically for recognition. Use this time to send emails or messages to team members and colleagues across the organization acknowledging specific contributions they made that week. The recognition should reference the particular project or behavior. This can be done by any manager or leader without requiring a formal program or platform, and creates a consistent habit of appreciation that improves engagement and retention. (Source: Rachel Weeks, Episode #273)

Increase the frequency of "thank you" to improve morale and motivation. Research cited by this guest shows 75% of US employees say morale and motivation would improve if managers simply said thank you more often. Make saying thank you a deliberate practice, not an afterthought. If you struggle to remember, schedule it into your calendar (e.g., the "10 minutes by Friday" practice) to build the habit. (Source: Rachel Weeks, Episode #273)

Maintain recognition programs during layoffs, funding rounds, and organizational change. During periods of organizational stress (layoffs, acquisitions, funding rounds, AI integration), recognition programs become even more critical to retention and morale. Continuing recognition signals that the company values its remaining employees. Stopping recognition during these periods sends the opposite signal and accelerates departures. (Source: Rachel Weeks, Episode #273)

Build a cross-functional recognition program committee with executive sponsorship. Establish a task force to design and oversee your recognition program that includes HR, marketing, and representatives from different teams across the organization. This committee should solicit input on what types of recognition employees actually want, define the behaviors and values you want to recognize, and develop the brand and visual assets for the program. Executive leadership must actively support and resource the program for it to succeed. (Source: Rachel Weeks, Episode #273)

Measure team morale and job satisfaction as a key performance indicator for marketing initiatives. Beyond revenue and efficiency metrics, measure whether new workflows, tools, or initiatives improve team morale and job satisfaction. Ask: Does this tool make your team happier? Are they doing more of the things that excite them? Are they more passionate about their role? A happier team is more likely to stay, produce better work, and drive better results. (Source: Lindsay O'Brien, Episode #304)

---

Onboarding

Onboard new team members by assigning them to execute a live event. Rather than traditional onboarding, assign new hires to own or co-own a live event (or major event component) immediately. This forces them to learn systems, tools, vendor relationships, and team workflows through real work. It's more effective than classroom training and builds team chemistry faster because people learn how the organization actually works by doing. (Source: Dave Gerhardt, Episode #294)

Extend onboarding with a 3–6 month shadowing period for senior hires. For senior hires (C-level or high-impact roles), expect the new hire to spend 3–6 months primarily shadowing and learning rather than producing work. This allows them to absorb context, build relationships, and understand the organization deeply. While high-performing hires will naturally start taking on work, the expectation should be learning-focused. This approach prevents setting them up for failure and leads to steeper performance trajectories than rushing them into production. (Source: David Kline, Episode #138)

When starting as a fractional CMO, establish structural preconditions and lead with listening. Fractional CMO engagements succeed when two conditions are in place: (1) there is an existing operating rhythm and team structure you can plug into, and (2) the CEO is in lockstep with you and actively supports your work. Once those conditions are confirmed, begin with a listening phase. Introduce yourself, explain your background and why you're there, and make clear you're coming to listen first. Frame your role as helping the team feel less frustrated and make progress on their goals. Speak in the team's language and focus on making their jobs better. Ensure feedback flows both ways—the team should feel comfortable giving you feedback without triangulating through the CEO. (Source: Amanda Goetz, Episodes #244 and #158)

---

AI Adoption and Team Development

(Note: How to frame AI adoption for your team is contested. See Where Experts Disagree.)

Partner the Chief People Officer with the CEO on AI change management. Position the Chief People Officer (or Chief HR Officer) as a co-leader with the CEO on AI adoption strategy. This ensures AI rollout is treated as a change management and human behavior problem, not just a technology problem. The CPO brings organizational culture, employee experience, and change management expertise to the table, keeping the human element central to AI adoption strategy. (Source: Bill Glenn, Episode #328)

Embed AI adoption into annual goal-setting for all team members. Require all team members to set at least one annual goal related to AI, tailored to their function. Goals can range from adopting a specific tool or use case, to exploring and learning (e.g., taking a course), to building capacity or solving a particular problem with AI. This signals that AI adoption is a company priority and ensures accountability for experimentation and learning across the team. (Source: Jennifer Cannizzaro, Episode #267)

Build AI culture through multi-level integration: goals, meetings, one-on-ones, and cross-org initiatives. Embed AI adoption into the organizational culture at multiple levels simultaneously: individual annual goals, team meeting spotlights, one-on-one conversations, small group problem-solving sessions, and cross-functional initiatives. This creates redundancy and reinforcement so AI adoption becomes part of how the team operates, not a one-time initiative. (Source: Jennifer Cannizzaro, Episode #267)

Identify and leverage internal AI power users as change agents. Rather than hiring external AI specialists, identify team members already experimenting with AI tools and empower them as internal change agents. Have them surface their experiments, share learnings, and lead adoption within their functions. This leverages existing talent, builds internal capability, and signals that AI adoption is everyone's responsibility, not a specialized role. (Source: Jess Lytle, Episode #328)

Use teaching assignments to deepen AI learning and expertise. When introducing new AI tools to a team, create assignments that require team members to use the tool and then teach it back to peers. This forces deeper learning, surfaces gaps in understanding, and builds organizational expertise. The teacher learns more than the student in this dynamic. (Source: Jess Lytle, Episode #328)

Empower team members to teach and explain AI tools they've mastered. Have team members who have mastered an AI tool or process teach it back to peers and leadership. Ask them to explain what they learned, what failed, and how they'll iterate—this reinforces that failure is part of the learning process and builds psychological safety around AI experimentation. (Source: Bill Glenn, Episode #328)

Run a weekly internal show-and-tell series where team members share their AI use cases. Establish a recurring weekly meeting (e.g., "How We AI") where different team members present one AI use case they're experimenting with in their day-to-day work. No formal preparation required—just a casual presentation of what they're trying. This creates a low-pressure learning environment, reduces impostor syndrome around AI adoption, and surfaces new use cases and best practices organically. (Source: Tara Robertson, Episode #288)

Train brand teams to be data-driven by uploading performance data to AI for analysis. Help brand and communications teams develop data literacy by uploading their weekly or bi-weekly performance reports (social metrics, engagement data, post performance) into ChatGPT. Ask the AI to identify patterns, suggest what might have caused changes, and recommend experiments based on high and low-performing content. The AI serves as a teaching tool that makes data analysis accessible to non-analysts. (Source: Sara Ajemian, Episode #288)

Help teams reinvest time freed by AI into higher-value work. When AI tools reduce time spent on tactical work, work with employees to identify how they should reinvest that time. Options include: client conversations, strategic learning, exploring new initiatives, or supporting other organizational priorities. Do not assume employees will automatically find high-value uses for freed time. Leaders should actively discuss and structure how that time gets used based on individual needs and organizational goals. (Source: Rachel Weeks, Episode #273)

---

Where Experts Disagree

1. Should managers give direct feedback and directives, or use collaborative questioning to guide teams?

Support summary: 3 vs 1

Position A — Give direct feedback and directives (Kieran Flanagan, Dave Gerhardt)

Kieran Flanagan (Episodes #318 and #257) argued that asking probing questions while actually steering toward a predetermined answer is dishonest, slower, and less respectful of people's time. Teams appreciate craftspeople who say "I want to do it this way" directly. He reiterated this position across two separate episodes, applying it broadly to management style, not just specific contexts.

Dave Gerhardt (Episode #257) endorsed teaching craft skills through marked-up feedback and direct rewrites rather than Socratic questioning, citing that copywriters learn through repetition and seeing expert rewrites. The learner may dislike it in the moment, but they internalize the standard and improve significantly.

Position B — Use collaborative questioning to build team ownership (Dan Cmejla)

Dan Cmejla (Episode #134) recommended presenting ideas as questions ("What do you think of this idea?") rather than directives. He argued this shifts the creative burden to the collective team, increases ownership, and often results in team members improving the idea or making it their own. His concern is that directives position the manager as the sole source of ideas and reduce team creative investment.

Context dependency: Direct feedback may be more appropriate when the manager has deep craft expertise (e.g., copywriting, creative direction) and the goal is skill transfer. Collaborative questioning may be more appropriate when the manager wants to build team ownership of ideas and is not the domain expert. However, both Flanagan and Cmejla are speaking generally about management style, not limiting their advice to specific contexts, making this a genuine disagreement in default approach.

Why it matters: The choice between direct directives and collaborative questioning shapes team culture, learning speed, and ownership. Managers who default to the wrong style risk either slowing skill development or undermining team autonomy and creative investment.

---

2. Should one-on-ones focus on blockers and decisions only, or also include status updates?

Support summary: 2 vs 1

Position A — Blockers and decisions only (Priscilla Barolo)

Priscilla Barolo (Episodes #302 and #193) explicitly structured one-on-ones around blockers and decision-making. When a blocker comes up, she clarifies whether the report wants awareness or action, preventing status-update drift. She recommended using asynchronous PowerPoint updates from leaders instead of one-on-ones for status, reserving one-on-ones for personnel matters and issues requiring private discussion.

Position B — Structured async prep with status included (Mychelle Mollot)

Mychelle Mollot (Episode #182) used the Fellow app to allow team members to add status updates asynchronously throughout the week. The manager reviews them offline before the meeting, while discussion items are reserved for synchronous time. In this model, status is part of the one-on-one ecosystem—just consumed asynchronously rather than read aloud in the meeting. This is a hybrid approach that doesn't fully exclude status from the one-on-one system.

Context dependency: Mollot's approach may suit larger teams where the manager needs a structured intake system, while Barolo's approach may suit smaller teams with more direct communication. However, both are speaking to general one-on-one management practice, making this a genuine disagreement in default structure.

Why it matters: How one-on-ones are structured directly affects whether managers spend synchronous time solving real problems or listening to updates they could have read, which compounds across an entire team's weekly calendar.

---

3. Should leaders frame AI as empowering employees, or acknowledge it may replace some work?

Support summary: 3 vs 1

Position A — Frame AI as empowerment, not replacement (Davang Shah, Rachel Weeks)

Davang Shah (Episode #338) argued that AI cannot replace human creativity, judgment, authentic connection, and trust-building. The future is a "marriage of AI-driven efficiency and human-centered creativity." Leaders should use this framing to retain talent, manage change anxiety, and set realistic expectations.

Rachel Weeks (Episode #273) recommended framing AI tools as capabilities that make employees more powerful and productive, not replacements. She advised connecting the benefit to employee goals (e.g., "this will help you close more deals") and avoiding language that suggests technology can replace human judgment or value. She also argued that continuing recognition programs during AI integration signals the company values employees and doesn't view them as replaceable by technology.

Position B — Acknowledge real trade-offs, including short-term performance dips (Drew Pinta)

Drew Pinta (Episode #346) recommended establishing a top-down mandate that teams can temporarily reduce performance on existing initiatives to invest time in learning AI tools. Leadership should explicitly communicate that short-term metric dips are acceptable during the transition period. This is a more candid framing than pure empowerment messaging—it acknowledges real costs and trade-offs rather than only upside.

Context dependency: These positions are not mutually exclusive in all respects—empowerment framing and acknowledging trade-offs can coexist. However, the empowerment-only camp explicitly avoids language suggesting replacement or cost, while Pinta's approach requires leaders to openly communicate that current work will suffer. This is a genuine disagreement in communication strategy during AI rollout.

Trend note: The most recent episode (346, April 2026) takes the more candid trade-off position, while the empowerment-only framing appears in earlier episodes (338, 273). This may reflect a maturation in AI adoption discourse where early "don't worry" messaging is giving way to more honest acknowledgment of transition costs, but the sample is too small to confirm a trend.

Why it matters: The framing leaders choose when rolling out AI affects employee trust and psychological safety. Overpromising empowerment without acknowledging real disruption can backfire when employees experience actual workload conflicts or role changes.

---

What NOT To Do

Do not use probing questions as a disguise for directives. Asking questions while steering people toward a predetermined answer is slower, less honest, and less respectful of people's time than simply stating your point of view directly. (Source: Kieran Flanagan, Episodes #318 and #257)

Do not whipsaw your team with every strategic uncertainty you're experiencing. Keep your team focused on executing the current plan until a conscious decision is made to change direction. Do not make your team your therapist. (Source: David Kline, Episode #138)

Do not hire to solve an overwork problem before auditing and eliminating low-value work. First audit your current work to eliminate unprofitable or low-value activities. Only hire after you've confirmed the need is real. (Source: David Kline, Episode #138)

Do not let sunk cost fallacy trap you into launching something misaligned with your strategy. If you realize an initiative is misaligned with your strategy or won't deliver the value you intended, scrap it and pivot—even if you're days away from launch. The cost of launching the wrong thing is higher than the cost of delaying to get it right. (Source: Jess Cook, Episode #266)

Do not stop recognition programs during organizational stress. Stopping recognition during layoffs, acquisitions, funding rounds, or AI integration sends the signal that the company views employees as replaceable. This accelerates departures. (Source: Rachel Weeks, Episode #273)

Do not allow post-decision sabotage. After a decision is finalized, do not allow team members to throw rocks at ideas behind closed doors or withhold commitment. Require disagree-and-commit behavior. (Source: Dave Gerhardt, Episode #141)

Do not act on high-emotion impulses immediately. When you feel an urgent impulse to respond or decide while emotionally activated, implement a rule to sleep on it first. The stronger the urge to act immediately, the greater the need to pause. (Source: Kara Hardin, Episode #160)

Do not allow team members to over-rely on AI without coaching. When you detect obviously AI-generated output, provide direct corrective feedback. Use it as a coaching moment to reinforce the importance of human judgment and editing. (Source: Jennifer Cannizzaro, Episode #267)

Do not rush senior hires into production. For C-level or high-impact roles, expect 3–6 months of shadowing and learning before full production. Rushing them into execution before they've absorbed context leads to failure. (Source: David Kline, Episode #138)

Do not enter a fractional CMO engagement without CEO alignment and an existing operating rhythm. Fractional CMO engagements fail when the CEO is not in lockstep with you or when there is no existing team structure to plug into. (Source: Amanda Goetz, Episodes #244 and #158)

Do not treat AI adoption as purely a tools procurement problem. The primary barrier to AI adoption is organizational behavior change, not tool availability. The adjacent practices in this skill—CPO partnership, teaching assignments, show-and-tell sessions, AI goals in annual reviews—operationalize what addressing that barrier actually looks like. (Source: Bill Glenn, Episode #328)

---

Sources

Episode	Guest	Date
#128	Peter Mahoney	2024-04-01
#134	Dan Cmejla	2024-04-22
#138	David Kline	2024-05-06
#141	Dave Gerhardt	2024-05-16
#142	Jason Lemkin	2024-05-20
#143	Dave Gerhardt	2024-05-23
#158	Amanda Goetz	2024-07-15
#160	Dave Gerhardt, Kara Hardin	2024-07-22
#169	Dave Gerhardt, Danielle Messler	2024-08-22
#175	Ruth Zive	2024-09-12
#182	Mychelle Mollot	2024-10-07
#188	Tara Robertson, Peter Mahoney	2024-10-28
#193	Priscilla Barolo	2024-11-14
#194	Natalie Marcotullio	2024-11-18
#195	Andrew Davies	2024-11-21
#197	Rowan Tonkin	2024-11-28
#199	Sylvia Lepoidevin	2024-12-05
#205	Amanda Natividad	2024-12-26
#210	Jessica Skovira	2025-01-13
#217	Jessica Andrews	2025-02-06
#229	Kimberly Storin	2025-03-20
#237	Udi Ledergor	2025-04-14
#244	Amanda Goetz	2025-05-08
#255	Kelly Hopping	2025-06-16
#257	Kieran Flanagan, Dave Gerhardt	2025-06-23
#260	Matt Devincentis	2025-06-30
#264	Ashley Faus, Molly Sands	2025-07-14
#266	Jess Cook	2025-07-21
#267	Jennifer Cannizzaro	2025-07-24
#273	Rachel Weeks	2025-08-14
#283	Sylvia Lepoidevin	2025-09-18
#288	Sara Ajemian, Tara Robertson	2025-10-06
#294	Dave Gerhardt	2025-10-16
#297	Kelly Cheng	2025-10-23
#301	Maura Rivera	2025-11-06
#302	Priscilla Barolo	2025-11-10
#303	Harry Dry	2025-11-13
#304	Lindsay O'Brien	2025-11-17
#318	Kieran Flanagan	2026-01-05
#328	Bill Glenn, Jess Lytle	2026-02-11
#338	Davang Shah	2026-03-17
#342	Dave Kellogg	2026-03-31
#346	Drew Pinta	2026-04-13