Mato just raised pre-seed Read more
Podcast charts
Published by Charlotte Ward
Customer Support Leaders have been there, on the front line with customers. They understand how things work, and the value of support. They understand the needs and foibles of their customer base. Unlike most other disciplines, there’s no training for this role. No two CS Leadership roles are alike. No two CS Leaders are alike. So this is our opportunity to hear from those leaders and learn from them. Whether you’re a CS leader now, or you aspire to be, this is the podcast for you! Hear different leaders discuss a topic with me, Charlotte Ward.
On the charts
Every published chart this podcast appears in, in the snapshot behind this page. Each one links to the chart it came off.
The Mato Topic Intelligence Platform does not report this podcast as charting in a published category in this snapshot.
From the feed
The latest episodes published to this podcast’s own RSS feed. Titles and descriptions are the publisher’s.
Send us Fan Mail “Escalate to engineering” sounds normal, but it quietly shapes how your whole company treats support. We challenge that default and replace it with a more accurate model: routing work to the right skill set, while keeping escalation for the moments that truly need higher priority and attention. Along the way, we explore how small language choices change ownership, expectations, and trust between customer support and engineering teams. Alex Batchelor, founder and CEO of Pebble, shares what happens when support gets the same technical context engineers use: logs, error monitoring, product analytics, documentation, and code-level clues. We talk about turning customer signals into product improvements without getting trapped at either extreme of the spectrum: raw data with no story, or vivid anecdotes with no proof. The goal is practical support operations that reduce context switching, shorten time-to-resolution, and create feedback loops engineering can actually act on. We also dig into proactive support and the future of AI in customer support. If your systems can detect an integration token expiring or a recurring error before a customer files a ticket, you can reach out first and create a genuinely delightful customer experience. And as automation handles the basics, we look at where humans add the most value: building the support system, solving the hardest technical tickets, and delivering consultative support that feels closer to a partnership than a transaction. If you want tighter engineering collaboration, cleaner ticket routing, and a more scalable technical support model, listen now. Subscribe, share this with a support or engineering leader, and leave a review with your biggest takeaway. Support the show
Send us Fan Mail Chaos in customer support rarely starts as chaos. It starts as “organic” growth, a few heroic workarounds, a helpful engineer jumping into Zendesk, or a fast acquisition that bolts on a new product and a new team without a shared operating system. Then the outcomes get unpredictable: escalations drag, customers hear different answers, and everyone feels busy while nothing feels steady. We dig into how to bring cohesion back without killing the good parts that made the team successful in the first place. Colin Flanigan joins me to unpack what he does in technical support leadership across B2B SaaS, including the messy reality of joining after rapid change. We talk about the first weeks on the job as a blend of journalist and analyst: running a genuine listening tour, collecting complaints as signals, building a friction map, and then validating the story with real support metrics. From there, we explore how to use proven frameworks (not rigid prescriptions), where bespoke work matters most (especially voice of the customer programs), and why many “technical” problems are actually broken communication systems across teams. We also go deep on the human side of change management: how to earn trust even when people do not fully agree, how to recruit champions from the people who care most about specific pain points, and why early wins in the first 60 to 90 days matter. We finish with practical leadership tactics like disagree-and-commit, time-boxed experiments, not optimizing for edge cases, and setting clear boundaries between support, engineering, and product so goodwill does not turn into resentment. If you want sharper support operations, stronger cross-functional alignment, and more predictable customer experience outcomes, listen now. Subscribe, share this with a support leader who is cleaning up chaos, and leave a review with the one boundary you wish your org would clarify. Support the show
Send us Fan Mail Servant leadership gets talked about a lot, but it’s often treated like a vague “be nice to people” slogan. We take a sharper angle: servant leadership in customer support is competence plus care. That means knowing what you’re doing and genuinely caring about your team, then using both to remove obstacles so they can do their best work. Along the way, we explore why this approach applies not just to “the team” in the abstract, but to the day-to-day dynamic between you, each direct report, and the stakeholders around you. We dig into what servant leaders actually look like at work: humble enough to admit what they don’t know, wise enough to set boundaries, and disciplined about not confusing compassion with complacency. We talk about the difference between being transparent and over-sharing, including the idea that a support leader sometimes has to protect the team from unnecessary stress while still keeping trust intact. We also unpack fairness and organisational justice, how favouritism can quietly poison a team, and how involving people in hiring and role design can prevent competition and build alignment. If you’re new to management or moving from individual contributor to leader, this conversation gets practical fast. We cover the temptation to stay busy by “doing the work,” why early delegation matters, how to operate at the right level even when you still spend time in the queue, and how to say no in a way that validates feelings without dodging responsibility. Listen for concrete support leadership takeaways on stakeholder management, setting expectations, and leading with that rare mix of dignity and humility. If it resonates, subscribe, share with a fellow support leader, and leave a review. Support the show
Send us Fan Mail Trust doesn’t magically appear because you got the title, and it definitely doesn’t return because you delivered one heroic win. When a customer support team has been burned by toxic management, constant escalations, broken processes, or a product that keeps letting customers down, “prove it” becomes the default setting. We dig into what it means to lead from that reality and how to rebuild credibility without trying to play therapist or pretending everything is fine. Ash Rhodes returns to the Customer Support Leaders Podcast with a fixer’s view of customer experience leadership. We talk about why workplace trust starts lower than trust in everyday life, and how stress responses like fight, flight, fawn, and freeze can show up at work as silence, avoidance, hidden problems, or people checking out. From there, we get practical: earning trust through consistency, showing up every day, and making sure your advocacy is visible to the team that needs it most. We also unpack a mistake many new support leaders make, quietly working behind the scenes while the team assumes nothing is changing. Spending time in the queue helps you truly understand the pain, but the real job is fixing the ecosystem: processes, staffing signals, cross-functional relationships, and feedback loops. Finally, we talk honestly about burnout, the mental load of support leadership, and why community spaces like Support Driven and therapy can be essential, not optional. If you’ve ever stepped into a low-trust environment and wondered how to turn it around, this one’s for you. Subscribe, share it with a fellow support leader, and leave a review with the trust-building habit that has worked best for you. Support the show
Send us Fan Mail AI can make customer support faster, cheaper, and more consistent, but it can also quietly destroy trust when it becomes a wall between customers and real help. Charlotte Ward sits down with customer experience expert Shep Hyken to get brutally clear on what never changes: customers want to be happy, they want you to take care of them, they want it to be easy, and when something breaks they want it fixed. The channel is secondary. The feeling is the product. We unpack why Amazon is one of the few brands that can run an overwhelmingly digital service model without making customers feel abandoned, and what most companies get wrong when they use AI as contact deflection. Shep shares why the human touch is not going away, it is flipping into a competitive advantage that strengthens the digital experience. We also get into proactive communication that reduces anger (knowledge is power), why “silence kills trust”, and how to design escalation so customers do not have to repeat themselves. You will also hear surprising research on support preferences across generations, what it means when Gen Z starts choosing the phone more often for real problems, and why “time to happiness” may be a better north star than average handle time. If you are building AI customer service, contact center automation, self-service, or omnichannel support, this conversation will help you keep speed without sacrificing the relationship. Subscribe, share this with a CX leader on your team, and leave a review with the one place you think AI should never be the only option. Support the show
Send us Fan Mail Great support can look “perfect” on paper and still fail the customer in real life. That tension is what we dig into with Carl Lenocker, a senior customer success executive, executive coach, and longtime support leader, as we unpack a simple idea with big consequences: outcomes over optics. We get concrete about how traditional support KPIs like first contact resolution, time to answer, and fast ticket closure can quietly create the wrong behaviours. When the business rewards speed and box-checking, teams get pushed toward rushed calls, prematurely closed cases, and fewer relationship-building moments. Carl shares lessons from running global support at HP and why many of these pressures ultimately trace back to money, cost cutting, and the old “support as a cost center” story, especially during the outsourcing era. From there, we look forward. We talk about AI in customer support as a way to handle simple issues quickly, and why the real opportunity is to reinvest human time into premium, consultative, relationship-driven support that prevents the next ticket and protects renewals. We also call out action faking, including performative QBRs, and Carl breaks down what actually matters in a customer business review: business objectives, progress, and risks, not 50-slide theatre. If you lead support or you’re building a career in post-sale, you’ll leave with sharper language for executives, better internal alignment, and a clearer way to prove value beyond dashboards. Subscribe for more conversations like this, share this with a support leader who needs it, and leave a review with the metric you think your team should stop worshipping. Support the show
Send us Fan Mail Support teams don’t usually fail because they “don’t care” or “aren’t working hard enough.” They fail because they scale on instinct, accumulate tribal knowledge, and measure whatever is easiest until the whole system starts to wobble. We sit down with Neal Travis, Head of Customer Experience and Operations at AIHR, to talk about measuring support maturity in a way that leads to real decisions, not a prettier dashboard. Neal shares how a small team can support a large customer base by getting ruthless about what support owns and how the work is designed. We walk through Neal's support maturity framework built around three domains: knowledge, quality, and data and insights. On the knowledge side, we dig into self-service experience, internal knowledge management, and training that prepares the team for what’s coming next, not just onboarding. We also unpack why “supportability” is an outcome when documentation, enablement, and cross-team alignment are strong, and why customers learning changes before support does is always a red flag. From there we move into quality, separating communication quality (standards, coaching, QA programmes, onboarding for great conversations) from operating quality (channels, capacity, coverage, incident management, and the reality of a messy support tech stack). Finally, we get practical about support metrics and measurement architecture: choosing the right metrics, understanding trade-offs like handle time vs after-call work, building reliable data infrastructure, and turning voice of the customer into action that closes the loop. If you want a clear picture of where your support function is mature and where it’s fragile, this conversation gives you a map. Subscribe for more, share this with a support leader who’s trying to scale, and leave a review with the one domain you’re working on next. Support the show
Send us Fan Mail Your one-on-ones shouldn’t feel like a weekly status treadmill where we do all the talking and our team does all the nodding. Charlotte Ward sits down with Greg Skirving to unpack a deceptively simple leadership shift: the reverse one-on-one, where the direct report leads with their perspective instead of waiting for the manager’s agenda. Greg walks us through his practical structure a three-slide monthly check-in covering accomplishments, challenges, and what the person wants to improve next. We talk about why this works especially well in customer support and technical support environments that are drowning in metrics like tickets closed and MTTR, while so much real value goes uncounted: mentoring, onboarding, process fixes, cross-functional help, and customer moments that protect renewals. The goal isn’t more paperwork, it’s clearer thinking, better coaching, and a more honest view of impact. We also dig into the change management piece: why the first few rounds can be awkward, how to coach ICs who dislike “talking about themselves,” and how presenting internally becomes a safe way to build communication and confidence that carries into customer calls, incident leadership, and even career moves into pre-sales, implementation, or project roles. By the end, we connect the dots to a simple career advantage: building an ongoing evidence file that makes self-evaluations and promotion conversations easier because the proof is already collected. If you want one-on-ones that create growth and not just updates, listen now, then subscribe, share with a fellow support leader, and leave a review. What would you change about your one-on-ones first? Support the show
Send us Fan Mail Mary Poppins is “practically perfect” and that makes her a surprisingly useful guide for modern customer support leadership. We (Charlotte Ward and Jason Yun, Head of Provider Success at Prax Health) use the film’s songs and characters to translate timeless ideas into practical support team lessons: hire for kindness and wit, stay close to the frontline, and remember that people at work still want to be seen, heard, and understood even when the market feels harsher than it did a few years ago. We talk about advocacy and allyship through “Sister Suffragette”, and we confront the Mr Banks trap: getting rigid, comfortable, and oblivious while chaos quietly builds around you. From there we get extremely tactical with “A Spoonful of Sugar”, unpacking how support leaders deliver bad news, write appeasement emails, de escalate tense calls, and keep dignity intact for customers and agents. We also call out the gap between big vendor visions and what teams actually need day to day, including an honest take on AI in customer support and why hype rarely matches real budgets or proven outcomes. Along the way, Bert becomes the model for a different kind of leadership voice: the storyteller who reframes, suggests alternatives, and helps people change without being shamed. We close with “Let’s Go Fly A Kite” and a simple north star for the future of customer success and customer support: let automation handle the boring clicks while humans lead with trust, relationship building, and product insight that actually improves the customer experience. If this made you rethink your own leadership style, subscribe, share the episode with a fellow support leader, and leave a review. Support the show
Send us Fan Mail Most coaching goes wrong before the coaching conversation even starts. If we only review a tiny sample of calls, chats, or tickets, we end up “coaching the seventh hole” and missing the real issue that shows up earlier in the customer journey, like unclear expectation setting or a pattern that repeats across channels. I’m joined by Rob Dwyer, Senior Technical Account Manager at Level AI and CX Executive in Residence, to unpack how AI can identify coaching opportunities without pretending to replace leadership. We use a surprisingly useful golf analogy to explain the core problem: agents are “playing” all day long, on different levels of difficulty, while supervisors are juggling escalations, PTO, reporting, and intraday chaos. In that reality, humans cannot reliably watch enough work to spot true patterns, but AI can, because pattern recognition is exactly what these models do well. We also get practical about what “signals” can look like, including an omnichannel example where an agent sounds fantastic on the phone but struggles with written communication in email and ticket replies. That’s a hidden coaching gap unless you’re analysing conversations across voice and async work. Along the way, we talk about using AI to highlight strengths so recognition is specific, and how this can help newly promoted managers calibrate quickly between foundational coaching and skill refinement. If you want coaching that feels fair, evidence-based, and actually improves customer experience, listen now, then subscribe, share this with a fellow support leader, and leave a review with the biggest coaching blind spot you see on your team. Support the show
Send us Fan Mail Your calendar says “1:1s,” but your brain hears “context switching.” Charlotte Ward sits down with Reagan Helms, VP of Customer Experience at Planning Center, to unpack a practical way AI can make us better managers: a management assistant that strengthens one-on-ones without turning leadership into autopilot. We get specific about how Reagan built his system and how it evolved, from separate AI chats per employee to a persistent copilot that can pull the right notes at the right time. We talk about the real-world plumbing behind “AI for managers” including Notion as a human-friendly interface, why Notion can be painful as a retrieval layer, when spreadsheets are the simplest high-performance backbone, and how a vector database can unlock faster search across qualitative coaching history. We also dig into meeting transcription, prompt refinement, and the discipline of verifying outputs so the manager stays responsible for the data and the decisions. Then we zoom out to the leadership impact: fuller agendas, fewer forgotten commitments, and an “impartial mirror” that helps you sanity-check whether you communicated clearly or whether an annoying behaviour is actually your coaching taking root. We also tackle the trust side head-on, with boundaries and consent so AI support doesn’t drift into surveillance or creep your team out. If you’re leading customer support, customer experience, or any growing team, hit play, share it with another manager, and subscribe for more. After you listen, leave a review and tell us: what would you want an AI management assistant to handle first? Support the show
Send us Fan Mail A lot has changed since the start of the year and not just job titles and cities. Charlotte Ward sits down with returning guest Alec Maloney to take stock of what is actually happening inside modern customer support teams as AI, automation, and faster tooling collide with the day-to-day reality of customers, tickets, and people management. We get practical about the new build vs buy trade-offs for AI in customer service. Alec shares what it looks like to evaluate vendor platforms and aim to shift a meaningful chunk of ticket volume to AI-assisted chat and email, while Charlotte explains why her instinct is often to build custom systems that fit the exact workflow. Along the way we talk Zendesk reporting, scripts generated with AI, and why “solve the problem in front of you” has become a useful operating principle for support operations and CX leadership. Then we zoom out to the bigger changes: blurred boundaries between support, ops, and adjacent functions, the need for centralised knowledge (Notion, Confluence, knowledge bases) to make AI effective, and the weird new shape of career progression. Title compression and flatter orgs mean growth can feel like more scope and more influence rather than a clean promotion, which raises real questions about sustainability, delegation, and what different team members actually want from their careers. If you lead customer support, CX, or support ops and you are trying to make AI useful without losing the human layer, this conversation will give you language, examples, and a few sharp edges to think about. Subscribe, share this with a fellow support leader, and leave a review with the one change you are seeing most in your own team. Support the show
Send us Fan Mail AI can generate a clean looking knowledge article in seconds, but that speed comes with a trap: it makes bad knowledge easier to publish and easier to surface. Leslie O’Flahavan joins me to unpack a simple claim with big consequences for customer support leaders and knowledge management teams: AI won’t fix your knowledge quality problem, it will expose it. We get practical about what AI can do well (drafting, simplifying language, reformatting for different audiences) and what it cannot do for you (understanding the real human reader who is stressed, new to the task, or missing context). Leslie explains why writing is more than editing and why relying only on revision can create “brain flab” as teams stop practising planning and organising. We also dig into a better way to judge content: stop asking users whether they like it and start asking whether they can complete the task with your self service help. From there, we explore concrete tactics to make the reader real again: using daily ticket feedback as gold, building articles around customer questions, and designing knowledge base and FAQ structure that works for both humans and AI search. If you’re feeling AI fatigue, this conversation reframes the moment as an opportunity to do more meaningful knowledge gardening, not less. Subscribe for more conversations on support leadership, AI in customer service, and knowledge base strategy, and if this helps, share it with a teammate and leave a quick review. Support the show
Send us Fan Mail The office can be a productivity killer or a leadership advantage, and the difference usually comes down to one thing: whether we design the day or let the day design us. I’m joined by Andrew Rios to get real about returning to the office after years of remote work, and what it takes to make that shift sustainable for customer support leaders running busy teams. We dig into the practical mechanics that decide whether office life works: owning your calendar from day one, carrying over non negotiables like school runs and family time, and factoring in commute time so your week doesn’t silently stretch. Andrew shares how he protects evenings over the long haul even in a role where outages and service interruptions can happen, and why it can take time to build the right rules of engagement. Then we get into the hard part: getting work done when people can see you. We talk deep work blocks, the hidden cost of context switching, and how “Do you have a minute?” can derail an entire morning. Andrew explains how he sets office norms, sometimes even stepping into a coffee shop to recreate a remote focus setup, and how he turns walk up escalations into coaching moments that build team autonomy over time. If you’re navigating return to office, hybrid work, or simply trying to protect focus and work life balance in a contact center or support environment, this one is packed with tactics you can use immediately. Subscribe for more practical customer support leadership conversations, share this with a leader who’s struggling with office interruptions, and leave a review with your best calendar boundary. Support the show
Send us Fan Mail AI in customer support gets reduced to one tired idea: ship a chatbot and cut tickets. That mindset misses where the real leverage is. We sit down with Robert Cabral, Head of Customer Experience at Runway, to talk about “AI beyond the queue” and what it looks like when an AI-first company uses automation to scale service while protecting the customer relationship. We get practical about the messy middle: migrating long-lived support reporting, pulling data from multiple sources, and turning scattered metrics into a clear weekly narrative that product and leadership can actually act on. Robert shares how AI helps teams find the story inside ticket data, platform usage, and escalations, and why reporting is only valuable when it drives a better customer experience, a better product roadmap, and a better day-to-day for the support team. Then we move past talk and into action. We discuss chatbot foundations for product education, plus higher-impact automations that do real work, like refund handling with strict guardrails and human escalation when context is missing. We also explore how AI enables support teams to build internal tools and repeatable templates, even without traditional engineering backgrounds, and why that capability can become a career accelerator across CX, product, QA, and engineering. We close on leadership: how to address the fear that AI will replace support roles, how to set customer-focused goals, and how to plan for different outcomes if AI resolves 90% of questions or falls short. If you care about customer support AI, CX automation, AI reporting, and building durable teams in a fast-changing landscape, you’ll want this one. Subscribe, share with a fellow support leader, and leave a review if it helps you rethink your AI roadmap. Support the show
Send us Fan Mail Getting laid off can scramble more than your finances. It can shake your identity, your confidence, and the story you’ve been told about what “success” in customer support leadership is supposed to look like. That’s why this conversation with Jenny Dempsey hit so hard: she went from a clear leadership path in customer experience to two years of uncertainty, experimenting with consulting, and rebuilding from a place that felt anything but predictable. We talk about the moment she realized a leadership title no longer matched her values. Jenny shares what it was like to apply for individual contributor roles with 20 years of experience, get judged as “overqualified,” and wrestle with the temptation to downplay her background just to get hired. We also unpack a healthier approach: owning the choice, leading without the org-chart label, and focusing on skills that actually create impact like clear communication, customer empathy, and making work easier for the team. Then we zoom out to the unexpected parallel that ties it all together: her furniture flipping business. The product is different, but the customer journey is the same. Setting expectations, choosing the right channel, giving progress updates, and protecting trust when timelines are long. Charlotte puts it simply: silence kills trust. If you’re navigating layoffs, a career pivot, burnout, or a non-linear support career path, you’ll leave with practical mindset shifts and a better way to tell your story. Subscribe for more real conversations about customer support careers, share this with a friend who’s rethinking their next move, and leave a review with the title you’re ready to stop chasing. Support the show
Send us Fan Mail Customers are talking about you where your VOC program rarely looks and it’s shaping revenue, retention, and trust. Nate Brown joins me to introduce Fearless CX, a bold and practical way to lead customer experience in a time when fear is high, teams are tempted to retreat into silos, and “insular thinking” makes cross-functional work painfully slow. We dig into what Fearless CX looks like inside the organization: leaders acting as a beacon, building trust through character and conviction, and creating psychological safety without drifting into comfort or inertia. The goal is healthy tension where people can challenge ideas, learn fast, and collaborate across the enterprise to produce a consistent customer experience outcome. Then we get tactical about modern voice of customer strategy. Nate explains “wild sentiment” the unstructured feedback living on Reddit, YouTube, third-party communities, and public reviews. We talk about how AI search is changing customer support behavior, why customers often solve problems without ever contacting the brand, and how AI-enabled customer experience management platforms can finally harmonize structured and unstructured feedback into real themes, tags, and actionable insights. If you want a customer experience strategy that survives uncertainty and actually earns trust, press play. Subscribe, share this with a CX or support leader, and leave a review, then tell me: where do you think your customers are shaping your brand story today? Support the show
Send us Fan Mail AI is starting to take the queue. So what’s left for a customer support team once automation handles triage, repetitive questions, onboarding, and a big chunk of ticket volume? Ryan Klausner joins me to get specific about “life after AI” and why the future of support is bigger than faster replies. We talk about how human-first support can still thrive while using AI in customer service in a way that actually improves the customer experience. We dig into the real shift: moving from reactive ticket handling to proactive support that prevents issues before they hit. That means treating support as a central intelligence function, using AI to surface friction in the customer journey, spotting trends early, and turning messy contact data into clear insights that product and marketing teams can act on. We also get honest about the cultural and coaching work required to help frontline teams become strategic operators, not just great responders. Ryan shares what new roles and skills are emerging, from conversational analysis and prompt design to owning knowledge bases, self-service, and customer education. We also unpack trust, why “fake empathy” from bots can backfire, and how to build a better resolution path with smart escalation and truly white glove human help for complex scenarios. If you’re thinking about customer support careers, CX strategy, or AI driven customer experience, this one will sharpen your view of what’s next. If this conversation helps, subscribe, share it with a support leader on your team, and leave a review with your biggest takeaway. What part of support would you automate first, and what would you protect for humans? Support the show
Send us Fan Mail AI is already in your support queue, but the real question is what it’s doing to your career path. I’m joined by Hilary Dudek, Head of Customer Experience at Gamma, to get specific about how AI is reshaping customer support roles and why the “bots are coming for our jobs” narrative misses the most important part: new jobs are being created right now. We dig into what AI chatbots are genuinely good at, like handling simple requests and searching your help center faster than any human can, and where they still struggle, especially around empathy, reassurance, and messy edge cases. We also talk about the shift away from chatbots masquerading as humans and toward clearer, more transparent bot experiences that set expectations and make handoffs to human support feel natural. From there we go deep on the emerging roles: AI Support Engineer, support architect, and the growing need for people who can manage connectors across documentation, Slack, email, CRM, and data warehouses. We cover prompt engineering, knowledge management, routing and triage, hallucination risk, and why sensitive areas like billing and legal context still require careful human oversight. Hilary also shares a practical example of rapid experimentation: building a “support psychic” with AI that predicts likely follow-up questions and suggested responses from recent ticket patterns. If you lead support operations, manage customer experience, or you’re on the frontline wondering how to stay relevant, this conversation is a roadmap for leaning in with confidence. Subscribe, share this with your team, and leave a review, then tell me: what AI-powered support role do you want to see next? Support the show
Send us Fan Mail Growth rarely happens on a straight line, and neither should coaching. We sat down with Andrew Rios, Head of Customer Experience at Cityside Fiber, to explore how leaders can tailor their coaching as people mature—from fresh hires forming their professional identity to seasoned operators who navigate constraints with judgment and calm. Andrew draws on an unexpected source—coaching youth sports—to reveal practical tactics that translate directly to support leadership. We start with the early-career stage, where strong opinions and limited exposure often collide. Andrew’s approach is simple and effective: observe first, set clear expectations, explain the why, and check for understanding without condescension. He shares how to model the behavior you want, turn feedback into co-created next steps, and transform “I’m right” energy into team-first outcomes. Along the way, we talk about relatable storytelling, sticky lessons, and the value of asking people to reflect back what they heard so alignment sticks beyond the meeting. As the conversation moves to senior ICs and emerging leaders, we shift to the realities of budgets, staffing, and process limits. Here, coaching is less about task accuracy and more about decision quality, trade-offs, and influence without authority. Andrew explains how transparency builds trust, how to run adult reflection loops (“If you could do it again, what changes?”), and why change usually takes longer than a 90-day plan. We also dig into inheriting teams, decoding norms from past workplaces, and preventing message drift by re-anchoring the why at regular intervals—even with your top performers. Throughout, vulnerability is the backbone. Andrew talks openly about owning mistakes on the field and at work, thanking the team for the save, and using those moments to strengthen culture. If you’re a support leader, manager, or senior IC looking to evolve your coaching playbook, this conversation offers concrete tools and a mindset shift: meet people where they are, coach for where they want to go, and resist coaching them where they don’t. If this resonated, follow the show, share it with a fellow leader, and leave a quick review to help more people find these conversations. Support the show
Ranking source
Apple Podcasts rankings via the Mato Topic Intelligence Platform.
Observed September 15, 2026. Cached outside the daily freshness window; the positions keep the date they were taken on.
Apple and Apple Podcasts are trademarks of Apple Inc., registered in the U.S. and other countries.
Pairs with
Bring this source into Mato to read its transferable patterns, then turn them into an original show for your own audience.