The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/Customer Success/The Customer Success Playbook
The Customer Success Playbook artwork

Customer Success Playbook Podcast S3 E65 - Jake Mckee - Community VS Data Driven Road Map

The Customer Success Playbook · 2025-06-25 · 18 min

0:00--:--

Key moments - from our scoring

Substance score

56 / 100

Five dimensions, 20 points each

Insight Density12 / 20
Originality11 / 20
Guest Caliber14 / 20
Specificity & Evidence9 / 20
Conversational Craft10 / 20

Jake McKee, the community strategist known for his work at LEGO, tackles the fundamental tension between community passion and data-driven decision-making. Rather than treating these as opposing forces, Jake argues they're deeply interconnected - data needs qualitative context to avoid bias (citing how healthcare metrics can obscure systemic access issues), and passionate customer feedback requires deeper listening to understand root causes beyond surface complaints. The episode challenges the traditional 'black box' product development model where customer voice is collected upfront, then locked away during six-month or year-long development cycles. Instead, Jake introduces community-driven product development: ongoing engagement with passionate customers throughout the entire roadmap and development process, not just verification at the end. He emphasizes starting small with existing relationships - identifying super-users, leveraging customer success teams who already have daily customer contact, using platforms customers already inhabit (Slack, Reddit, Facebook groups), and focusing on relationship-building over launching perfect platforms. For companies without formal communities, Jake recommends tapping unofficial spaces and participating authentically rather than commanding attention. The approach recognizes that the best customer feedback often comes from your customer success team identifying the smartest customers, not just active platform members.

Key takeaways

  • →The best approach integrates qualitative customer insights with data analysis throughout development, not sequestered at the beginning, to catch biases and blind spots in metrics.
  • →Start community programs small with handful of engaged customers and existing tools (Slack, Facebook, Reddit) rather than investing in complex platforms before validating the approach.
  • →Customer Success teams are underutilized assets for identifying passionate customers and facilitating peer connections - they want to do more than transactional support.
  • →The 'everybody goes home happy' principle means both company and customers must gain value; conversations should be ongoing relationships, not one-off feedback sessions.
  • →Community-driven product development keeps customer enthusiasm and voice embedded throughout six-month or longer cycles, preventing the disconnection that happens in traditional waterfall models.

In this episode

  1. 1Jake McKee's Background at Lego and Community Building Philosophy
  2. 2Creating Shared Purpose: From Disposable Products to Creative Mediums
  3. 3Personal Interests and Off-the-Beaten-Path Austin Recommendations
  4. 4Balancing Passionate Customer Feedback with Data-Driven Metrics
  5. 5Community-Driven Product Development Approach
  6. 6Building Customer Communities from Scratch: Starting Small and Manual
  7. 7Leveraging Existing Platforms and Customer Success Teams for Community Programs

Mentioned

LegoKevin MetzgerRoman ReonJake McKeeSlackFacebookSalesforceReddit

Guests

Jake McKee

Topics in this episode

Customer success teamsCustomer advisory boardsdata analysisReddit communitiesCommunity-driven product developmentLEGO community buildingData bias in metricsSuper-users identificationSlack community programsQualitative vs. quantitative customer feedbackRelationship-based product roadmapscustomer success playbookCommunity-driven developmentproduct feedbackpassionate customers

Questions this episode answers

How do you know if passionate customer feedback or data should guide your product roadmap?

Neither should dominate alone - passionate customer feedback often signals important underlying needs that data metrics may miss or misinterpret, while data requires qualitative context to understand what's really being measured. The answer becomes clear when you engage customers in ongoing dialogue throughout development, not just upfront.

What's the difference between community-driven product development and traditional customer feedback collection?

Traditional product development collects feedback upfront, then locks customers out during months-long development in a 'black box,' removing their voice and enthusiasm. Community-driven development keeps customers engaged throughout the entire cycle in ongoing conversation, ensuring their voice influences decisions continuously.

Where should you find passionate customers if you don't have an official community platform?

Start with your customer success team (they know the smartest customers), identify super-users, look at unofficial communities like relevant Reddit threads, and participate authentically in spaces where customers already gather rather than launching new platforms.

What does Jake McKee mean by 'everybody goes home happy'?

Both the company and customers must gain mutual value from the relationship; if only one side benefits, the relationship won't sustain. Companies must clearly articulate what they need from customers (retention goals, new launches) while genuinely delivering on customer desires.

Should you start with a customer advisory board or smaller community programs?

Start small and today with what you have - use existing tools like Slack or Facebook, identify a handful of engaged customers, and manually facilitate connections before investing in professional platforms or formal advisory boards.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

12 / 20

The episode contains some substantive frameworks like 'everybody goes home happy' and 'community-driven product development,' but much of the content is repetitive elaboration on relationship-building principles and considerable padding with personal anecdotes (Lego flowers, scale modeling, Austin restaurants). The core insight about balancing passionate customer feedback with data is meaningful but not densely packed, with significant throat-clearing and tangential discussion.

everybody goes home happy. It's a mantra of community building that is really focused on this idea that I heard so many times from my colleagues at Lego that, oh, you know we just gotta do stuff for them and there's no return for us. That's a bad deal
I'm being more data driven with your qualitative and more qualitative with your data I think really is a good place to start

Originality

11 / 20

While Jake presents 'community-driven product development' as a framework, the underlying ideas about customer relationships, mutual benefit, and continuous engagement are well-established in the SaaS/product community. The approach lacks sharp contrarianism or first-principles thinking; it reads as applied best practice rather than novel insight. The Lego anecdotes feel like brand storytelling rather than original thinking about product development.

we're not here to sell boxes. We're here really both me as a community person representing the company to promote this idea that Lego is a creative medium
really understanding what's below the surface on why they're giving that particular feedback positive and negative

Guest Caliber

14 / 20

Jake McKee has genuine practitioner credibility from his years at Lego leading community and has built a consulting practice around community strategy. However, he's primarily a community/brand specialist rather than a product leader or operator who owns shipping roadmaps at scale. The episode frames him as a 'community guy' expert, which is narrower than the core question about balancing customer input with product metrics, where a CPO or head of product might offer deeper authority.

Jake McKee, the community guy, Roman
Spent years at Lego

Specificity & Evidence

9 / 20

The episode lacks concrete examples, named companies, metrics, or timelines to support its claims. Beyond vague references to Lego and a hypothetical oil rig drill bit company, there are no case studies, data points, or specific metrics showing how the framework performs. The advice relies on generalities ('start small,' 'have conversations') without evidence of tangible outcomes or measurable impact.

If you're making drill bits for oil wells in the gulf. There's still gonna be somebody who's very passionate about that
we'll do it in their existing Slack, we'll do it on a private Facebook group just because that's where all their customers are

Conversational Craft

10 / 20

The hosts ask soft, permissive questions that allow Jake to meander through long personal stories before reaching substantive points. The main question about balancing community feedback vs. data is solid, but follow-ups are gentle and rarely push for specificity or challenge assumptions. Kevin's question about customer advisory boards is cut short with Jake's consultant disclaimer, and there's little evidence of the hosts pressing for concrete guidance or testing claims.

For the smaller communities or for those building that kind of community recommend like customer advisory boards and things like that. And how, how do you pulling to make sure you get the feedback and content. I have to give my, my consultant disclaimer, that depends
Alright, so what's the coolest lesson those master builders over at Lego taught you about the concept of community?

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

community33customer19start13building11feedback11data11customers11jake10lego10passionate9first7product7driven6question6place6development6

Episode notes

Send us Fan Mail What happens when passionate customer feedback clashes with cold, hard data? Jake McKee tackles this age-old product dilemma with wisdom earned from years at Lego and building communities for Fortune 500 brands. This episode of the customer success playbook reveals why treating community building as relationship development - not just feedback collection - transforms how companies balance emotional customer input with analytical metrics. McKee's "everybody goes home happy" philosophy demonstrates how sustainable product decisions emerge when companies design mutually beneficial relationships rather than extracting value from user communities. From scale modeling to high-end fusion restaurants, this conversation weaves personal insights with professional strategies for community-driven product development. Detailed Analysis McKee's approach to resolving the tension between passionate customer feedback and data-driven metrics represents a sophisticated understanding of modern product development challenges.

Full transcript

18 min

Transcribed and scored by The B2B Podcast Index.

Customer success. Welcome back to the Customer Success Playbook podcast. I'm Kevin Metzger here again with my co-host Roman Reon. We're joined by Jake McKee, the community guy, Roman.

We've already had a really engaging first show on human driven AI design. Are you ready for today? I, I can't wait. This is gonna be great.

But Kev, before we tackle our one big question, you know, let's do a quick round of personal questions so our audience can get to know Jake a little better. Jake, you on board for that? Absolutely. You spent years at Lego, so I know our audience is jealous, probably like I am, which is awesome.

Alright, so what's the coolest lesson those master builders over at Lego taught you about the concept of community? Well, I gotta give you two. There's so much that came out of that that I, I don't know if I can narrow it down to just one thing, but. Yeah, the, the first one was my, my mantra that for direct customer engagement and community work has, has lasted me a career at this point, which is everybody goes home happy.

It's a mantra of community building that is really focused on this idea that I heard so many times from my colleagues at Lego that, oh, you know we just gotta do stuff for them and there's no return for us. That's a bad deal, right? We don't want that. They don't want that because if we're not getting anything as a, from the company side out of this connection, this relationship with the, the community base, we're not gonna do it very long.

Right. We might do a project or two and then lose interest or, or not find value for it and cut the funding or the, the, the time investment. So. By the same token you know, really understanding what the fans want and what they're interested in, not just what they're complaining about, or it's getting to know somebody through the anger or through the upset or through the questions instead of in spite of it, right?

So if they're upset about something, what's really driving that in the background? What's gonna make them happy? What are they looking for? And then how do we have a conversation between company and customer on an ongoing, regular basis where that.

Direct connection happens, and I can say to them, look, I really want to deliver that kind of set to you or that ability to buy these kind of parts. What I need in return though, because this year we're working on retention or we're working on launching this new project or we're doing, working on whatever it might be. That's what I'm working on. I need you guys to help me with that.

Here's three ideas. And they go, oh, no problem. We can do that. And then it becomes this mutually beneficial relationship and it really is a relationship at that point.

Right. You heard on Monday, I'm, I always talk about relationships. That's really fundamentally the work that I do is building these relationships between company, customer, and now ais. But yeah, it's really building that relationship is, is number one.

The other, the second I'll give you is the idea that I established fairly early on in my work, which was Legos, a creative medium. And today, you know, we see Lego on everybody's desks at all kinds of office buildings all across the world. And you know, I'm always surprised by the people that are outside the realm of who you think would have Lego on their desk at work. But I recently ran into a client that said, Hey, come over here.

You know, I wanna show you this woman's desk and. There's this middle aged woman that had a desk hovered in Lego flowers, right? Something that wouldn't have happened 10 years ago, it just wouldn't have been a normal thing. Right now it is.

And I think part of that comes down to the message that I always try to get across, that we're not here to sell boxes. We're here, really both me as a community person representing the company. Me as a community person working with the community members themselves, and both of those two entities on either side as well. We're all here to promote this idea that Lego is a creative medium because if I can get you to believe it's a creative medium, I can get you to feel proud about going and talking about the fact that you have a Lego room in your house with tens of thousands of bricks, right?

I can get you excited about buying a, a Christmas present that's Lego and maybe a little bit more expensive than something else you were considering for your grandkid that Christmas season. You're thinking, well, I'm, you are your grandfather, right? Yeah, exactly. Well, the, the grand, the grandchild, you're thinking, well, this is a great toy.

Right? I'm giving them a creative medium, not just a disposable toy. Right. But the grandfather as well might be as, as excited to participate in, in building that kit with the grandkid is as the grandkid is.

Right. So there's, and it's a creative medium, bringing them together. So it's really thinking about when it comes to community building, how do you step beyond? Business is there for, or what the customer demands are and what's that shared purpose in between?

That's so critical. We actually had, I won't mention names. We had a former guest, we were talking about what they do to kind of unwind outside of work, which is sort of a foreshadowing to a question that may be coming up for you. But.

What, what he said was, and he pulled up pictures, giant Lego sets, like giant, the Titanic. Yeah. Empire State Building Titanic table. Right.

It was awesome. So what's maybe an off the beaten path in Austin that we should visit if we come, if we come to your town and visit Austin? Man. So it's almost certainly gonna be trunks that I'll recommend to you because these days, you know, I'm, I'm not cool and hanging out on sixth Street with, with, you know, college kids.

Neither are, are we, so restaurants are perfect. Yeah, that's right. But yeah, my wife and I are, are, are huge foodies. That's tends to be majority of our date nights is going out to interesting restaurants.

And the one, first and foremost recommendation, although it's not quite as you know, hole in the wall as it used to be thankfully is a place called Conge. C-A-N-J-E. That's a, a real high-end fusion Jamaican Caribbean food type of place. It is.

That sounds good. Absolutely fantastic. And I think they were in the running for Michelin Star this last time. Missed it.

And I'm not sure how they're just off the charts good, but also they're not one of those places like French Laundry where you go into and you think, okay, I'm never having that kind of food again. But it was great for the one experience I crave their jerk chicken on a weekly basis. I haven't had Jamaican here in Atlanta, Kevin, in a while, but now that Jake's mentioned that, I think I'm gonna make a run. You know what?

Well there's another one, there's one over there's one not too far away. I can't remember what it's called, but we might, I'll get the Google Maps pin after, after the show, so. Alright, well let's Jake, last one, we'll do a quick one. When you're out, when you're not working outside of leg wing, what do you do to relax?

Mostly relax. My main hobby is scale modeling. So I build very complex, very small things. Oh, awesome.

And yeah, these days I've added the the 3D two, three different 3D printers and laser cutters, and. All kinds of other stuff in addition to all the hand created items. So, you know, I'm making a World War making a fully detailed, very accurate world War II Club mobile from the American Red Cross from Oh wow. Where they'd roll up on the battlefield and serve donuts and coffee to to the, the soldiers.

And, you know, it's a fascinating subject. Yeah, it's very cool. But it's one 35th scale and everything I've been pouring over plans and. Oh, tearing up the internet, trying to find the minimal pictures that that exist to be able to 3D model this appropriately and then print it out and bring a big diam out of it.

So I say, you know, relax. It's mostly relaxing. I really enjoy it, loves it. There are times when I want to tear my hair out, as you might imagine, but you know, that's all.

That's all hobby fun. If you're not mad at it, sometimes you're not doing it right. That's right, exactly. I love it.

That's right. I love it. You ready for one big question, Kev? Yeah, why don't we get into it?

So, Jake, when passionate community feedback conflicts with data-driven product metrics, how do you decide which voice guides the roadmap? Yeah, I think that's a really good question and I think it, it's hard to answer simply, so you gotta, you gotta bear with me on this one a little bit. So there's a, there, there may not be real distinction between what the passionate customers are saying and what the data's telling you. And I think that that often.

This is where if I, my wife and I'm really angry 'cause I had a bad day. She reacts to my anger. With anger. I kind of, you know, I don't know, I just get more angry.

Right? But there's something wonderful about saying, when, when she says to me, Hey, you, you seem really, how's your day? You doing all right? Can I give you a hug?

Right. Like, it's just, it's, it's, I think there's, there's a lot of that that goes on when we start talking about passionate customer. Passionate customer, to really first and foremost understand what's below the surface on why they're. Giving that particular feedback positive and negative, right?

People tend to, you know, accept the positive much quicker than they do the negative in, in some ways. But also, you know, when you say positive, it's sort of like our own human connections, right? When somebody says something good about you, it tends to bounce off a little bit more than when they say something negative and that really sticks with you, right? First and foremost is really understanding what's the dynamic of those passionate customers.

And this is where, you know, your community team or your community professionals will come in very handy because they can often translate and interpret some of that feedback. And I think that that not enough of that happens before we start to compare it with the data pieces. By the same token you know, data is its own tricky beast because. Just because it's data doesn't mean it's, it's valid for consideration or even fully valid for consideration just because you have something that says, you know, African American medical patients seek less care.

Well, how do you interpret that? Does that mean they're more healthy or does it mean that they have a harder access generally speaking to, to care? That there's some biases in the healthcare system that influence them, and you're really trying to make sure that you are being more data driven with your qualitative and more. Qualitative with your data I think really is a, is a good place to start understanding both of those things.

The second part of the answer though is, okay, so you've, you've kind of this apart, you understand the data a little better. You understand where some of the holes in the data might be, and you're starting to plug those with knowledge from direct customer conversation and vice versa, and you've got a pretty clear picture. The traditional product approach has been fairly sequestered, right? Where we have bookends of collection upfront, where we collect all of our, our, our research, it's our requirement documents, you know, whatever it might be that we need to, to get in place before we go start the development process.

We get our hands around that. We hug it real tight. We walk into the, to the product development. We kick the door shut, maybe lock it a couple of times, and then start working in dark.

And every once in a while we might stick our head out and say, Hey, I need a little bit of feedback. But by and large, the product cycle happens inside that, that black box. Right. And then when we're done, we pop up and verification starts is what we built Functional?

Is it good? Right. And there's a whole huge range. This is me as the community guy talking.

I have my own biases on this, but I really believe that. That what happens there is we get that customer voice removed so far from that cycle, especially if those cycles are six months or a year or 18 months long, right? Which some of them can be you know, how are we keeping that voice and therefore that enthusiasm for solutioning in place throughout that development process. And I think that that's a process I call community driven product development and how we go about putting those kind of programs in place.

And really back to your original question, how do we balance these two? You start to see it and feel it, right? You start to understand the data and the reasons why people might have responded with something on a survey. You might, you also using and en engaging with you and asking questions in certain ways over time.

Not just a one-off, you know, feedback session, but you know, could be weeks or months that you have these folks involved. And I think, you know, I'm, I know I'm biased, but I think that's one of the best ways to, to find a. Reality to potential data inputs. Right?

And, you know, how do you go about that? That's, you know, you can do small little programs, you can do longer time you know, six months, year long programs. Or you can do one-off sessions that last more than just a, you know, few questions worth, right? But, you know, whatever it is really thinking about your community mindset of, okay, if we're gonna listen to passionate customers, we gotta treat them.

In the, in, in a relationship format, and we have to really connect over time to understand them a little bit more deeply. And then, and then it's to balance itself out and, and answers become clear as any other input of you know, any, any other thought right, that goes into these roadmap plannings. If you have a community that is such an amazing resource and it's so hard to get these that wanna build out these robust customer communities and it's, they don't have 'em, right?

Like, yeah, the community not there. And so if you have one and you, like you said, Jake, you can tap into it not just to get ideas, but the validate 'em and bounce things along the way, and there's different approaches to that. It is such an amazing resource that how lucky and fortunate are those product teams where you can actually get real feedback Oh, absolutely. From people that are engaged, that care, that are invested and yeah, it's, it's, it's amazing.

Right. And I'll tell you there, there's something. So yes to all of that. One thing that I will say is a very important distinction is we're not just talking about pulling folks from from making an active community base, right?

Active customer community platform, and going to those folks. Kevin, you mentioned, you know, passionate customers and that could mean a whole bunch of things depending on what your company does, how you cater to them, right? If you're making drill bits for oil wells in the gulf. There's still gonna be somebody who's very passionate about that.

You may not have tens of thousands of people in a active customer community, but there are gonna be some people who want to talk about it, who you need to hear from. You also need to balance out with other kinds of voices, right? Like finding the passionate customers. They may come from community platforms, they may come from other community programs and efforts you're doing, but they may also come from your customer.

Success team goes, man, this guy is one of the smartest customers we've ever had, and he, we needed for his knowledge to come into, we're doing right. Our, our first oil rig drill bit shout out, which I love. Talk about a unique community. That's, I love it though.

Like he said, Jake, there's probably one guy that probably all knows everything in the world about drill bits and, and you know, as he, he hasn't it. So ke do you have another follow up before we wrap up our Wednesday episode? For the smaller communities or for those building that kind of community recommend like customer advisory boards and things like that. And how, how do you pulling to make sure you get the feedback and content.

I have to give my, my consultant disclaimer, that depends. There's a lot of, you know, que there's a lot of questions to ask before I can answer that particular question, but generally speaking, the answer I always give when somebody says, where should we start is, I say today in small right? I think there's far too much. Effort that gets put into trying to build a risk-free, professionalized, perfect platform.

And I'll, I'll use my fingers when I say perfect, right? But some sort of perfect platform that will, immediately engage every potential person that might want to come join this community, immediately take off, and it'll immediately be important and impactful to everybody involved, including the company. That's not usually what happens. Right?

The same way that I can't, I, I, if I'm smart, I'm not gonna meet somebody at a bar and asking to marry me that night and say, I love you by the time that drinks are are empty. Right. We've never been to this. You're not drinking the rough stuff.

Yeah, clearly not. Or enough of it. But when we, you know, we're building relationships and so being able to find, you know, a handful of people to get smart first, right? This is all part of a community building strategy.

How do you look at at super users? How do you start having customer conversations in a, and maybe a more community centric kind of way that isn't just give us feedback about the product, but give us feedback about the experience. Give us feedback about how you feel about us as a company. Give us feedback about.

How much you want to connect with your peers. Oh, what do you want from them when you connect? Oh, that's cool. Well, let me start introducing some people around, right?

Let me to go outta my way to say you like X and you like X. Why don't you guys meet? You know, let me, let me introduction. I.

It can be as simple as that to start a, and again, I'll use my Coty Fingers, a community program, right? Or community process. That said, there's other times where a, a brand may have they may not have their own official brand community specifically for their products that they run as a company and that sort of thing, but there may be you know, places on Reddit that are very well trafficked, right? There may be, unofficial communities that are built up, how do you start participating there and, and listening and you know, showing up just like you would anywhere else?

Right? Instead of blasting in and saying, I'm here, pay attention, I'm in charge. I'm the company. Right?

How do you come in and say, Hey. I'm here. Do you mind if I sit down? Right.

It is a very different dynamic, but I like the idea of starting now. There's always something you can do to learn more, to start building relationships, building connections and, and bridges to your, your customer base. And, and that can 50 different ways, including, you know, from a customer success standpoint, those folks talk to customers all day long. They want more connection.

Typically, from what I've seen in my experience, those customer success teams want to do more. They want to do more with their customers. They wanna get their customers together with other customers, right? So.

Can we do some of that manually before we get to a bunch of tools? Is there smaller tools that can facilitate some of those things? You know, these, these community driven development programs I use, i I built for, for companies often, we'll, we'll do it in their existing Slack, we'll do it on a private Facebook group just because. That's where all their customers are.

And it's easier that way, right? It doesn't have to be big, huge, complex, you know, hundreds of thousands of dollars of implementation no matter what Salesforce tells you. Jake, awesome stuff. Thanks for sharing your insights on community driven development and, and how to into that community.

So we're Hump Day is over. We're on the back half of the week. Jake's gonna join us Friday, Friday to explore experience designed again. We'll talk about how you don't lose in touch to our audience subscribes.

You don't miss it. You'll get a notification on your phone. You'll know when we, when we drop the new episode. If you're enjoying joining this series, don't forget to share it with your colleagues.

Give us a review and we will see you Friday. Until next time, Kevin, keep on.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • How B2B Marketers Use Customer Marketing for ExpansionB2B Marketing with Fexingo · on Customer advisory boards83 / 100
  • 89 - Is founder-led GTM a strength or a risk for SaaS investorsB2B SaaS Marketing Snacks · on Customer advisory boards80 / 100
  • How to Build Reddit and Discord Communities That Drive Sales: Music industry secrets that work for any business (episode #146)How I Made it in Marketing · on Reddit communities80 / 100
  • The CXLive! Episode 98: The Insight Flywheel: Making EBC Conversations Count in The Age of AI with Dmitry RisukhinThe CX Live! · on Customer advisory boards78 / 100
  • How Glossier Built a Community-First Beauty BrandThe CMO Podcast with Fexingo · on Customer advisory boards72 / 100
  • 90% of Startups Fail: What $100m Sales Teams Do Differently with Ethan SchechterBuilt Not Born: The Startup Go-To-Market Podcast · on Customer success teams65 / 100

More from The Customer Success Playbook

All episodes →
  • Customer Success Playbook - Final Episode with Kevin and Roman31 / 100
  • Customer Success Playbook Podcast S3 E72 - Adrian Swinscoe - Enhancing Customer Experience with AI55 / 100
  • Customer Success Playbook Podcast S3 E71 - Adrian Swinscoe - Unlocking Value in Customer Journeys48 / 100
  • Customer Success Playbook Podcast S3 E70 - Adrian Swinscoe - Data and Customer Storytelling74 / 100
  • Customer Success Playbook S3 E69 - Gayle Gorvett - Scaling AI Governance Without Killing Innovation65 / 100
Explore the best B2B Customer Success podcasts →
All The Customer Success Playbook episodes →