Lenny's Podcast / episode intelligence
Speakers in the public record
Claim mix
Evidence policy
Every row below preserves an exact excerpt. Identified speakers are linked; unresolved voices are labeled and excluded from people counts.
Claim ledger
15 published records
01 / evaluation
“Natural thing to do, let's write up this thing in Zendesk, but it's also about how we weave education into the product and we use Pendo again.”
02 / belief
“Yeah, it's a PM and then I would say, because what I'm seeing in less mature product orgs who first bring in product ops, the first thing they ask them to do is streamline the planning process.”
03 / belief
“I think there's that data piece that they really like to lean into and advisory, and then the leadership ones coming in from product to leader roles.”
04 / evaluation
“Is this happening consistently across the board? So, one probably seeing product teams across so many different places is you might have somebody who's really passionate and really good at doing this stuff for their own vertical and then it doesn't scale.”
05 / belief
“I mentioned that it's really hard right now to put a number to the success of the role or on the success of the role, but if there's no, "This is how you will be measured or this is what we're looking at as a successful outcome for this person in this role," I would say that's probably a red flag.”
06 / preference
“Leaders Eat Last, Simon Sinek. I really like that book too. That's more leadership style and making sure you putting in your team first, which is something I strongly believe in.”
07 / recommendation
“I strongly advocate for product ops leaders to have done that role, to have actually had hands-on product experience building and understanding customer problems and feeling that pain, because you very quickly realize where to place your efforts and where your team's efforts should go.”
08 / evaluation
“Generally, I will tell you it's because they still have a bit of buying in the top to get done.”
09 / recommendation
“Got it. So, the way to think about this role, because I imagine most people haven't ever had a product ops person in their company is there's a slice of the PM role that companies are finding is valuable to put on a different person that has different skillsets that can take this endless load that PMs have.”
10 / preference
“I'm so curious what parts of the role get sliced off over time because I love that.”
11 / preference
“As a product person, it means a lot to have that, because if you have direct reports, you obviously want them to be happy and healthy, but as a product person, you have this system around you even if you're not having people that report into you where you feel ownership to make sure these people are healthy.”
12 / evaluation
“The customers started to come up and we started to feel it a bit more and I felt like there was this huge need for a voice of customer management and synthesis of both this qualitative and quantitative data as a theme that I saw arising across our customer base or even just folks that were reaching out about this role as they saw Pendo was putting it down.”
13 / evaluation
“I think maybe that is because I have a product background. So, I felt that pain very acutely, but I will say for the majority of people I always speak to who don't have that product background, they're coming from consulting or from technical success or from some other group marketing maybe, it does feel relatively new because they're starting to dive into that space a little bit.”
14 / commitment
“I myself recently switched roles here at Pendo because I did what I said I was going to do, which was stand up the system, stand up the things that we knew we needed to do that were going to either be given off to another team or automated and then get the rest of the humans that are here to do the other strategic things for the product team.”
15 / evaluation
“" Our PMs, they would get the whole readout with us, but we brought those folks in a room together. It was really cool because I think our head of professional services team at one point was like, "Whoa, this could truly impact what we do from an onboarding perspective and now we have this data.”