Lenny's Podcast: Product | Career | Growth - Understanding the role of product ops | Christine Itwaru (Pendo)

Episode Date: February 16, 2023

Brought to you by Amplitude—Build better products: https://amplitude.com/ | Lenny’s Job Board—Hire the best product people. Find the best product gigs: https://www.lennysjobs.com/talent | Vanta���Automate compliance. Simplify security: https://vanta.com/lenny—Christine Itwaru is a longtime product operations leader at Pendo and more recently has taken on the larger role of Principal Strategist there. Before leading product ops, Christine spent 12 years in product management. In this episode, we delve into the rapidly growing field of product ops and discover how Christine is part of shaping the role industry-wide. She helps us define the role of product operations, what kind of person would be a good fit for the product ops role, when your company would benefit from product ops, and what red flags to look for if you decide to go down this path. Find the full transcript here: https://www.lennyspodcast.com/understanding-the-role-of-product-ops-christine-itwaru-pendo/#transcriptWhere to find Christine Itwaru:• Twitter: https://twitter.com/christineitwaru• LinkedIn: https://www.linkedin.com/in/christineitwaru/• Website: https://theproductheart.com/Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/Referenced:• Ben Williams on Lenny’s Podcast: https://www.podpage.com/lennys-podcast/how-snyk-built-a-product-led-growth-juggernaut-ben-williams-vp-of-product-at-snyk/• Pendo: https://go.pendo.io/• Marty Cagan on Lenny’s Podcast: https://www.lennyspodcast.com/the-nature-of-product-marty-cagan-silicon-valley-product-group/• Salesforce: https://www.salesforce.com/• Looker: https://www.looker.com/• Tray: https://tray.io/• Zapier: https://zapier.com/• Zendesk: https://www.zendesk.com/• Casey Winters on Lenny’s Podcast: https://www.lennyspodcast.com/how-to-sell-your-ideas-and-rise-within-your-company-casey-winters-eventbrite/• Inspired: How to Create Tech Products Customers Love: https://www.amazon.com/INSPIRED-Create-Tech-Products-Customers/dp/1119387507/• Leaders Eat Last: Why Some Teams Pull Together and Others Don’t: https://www.amazon.com/Leaders-Eat-Last-Together-Others/dp/1591848016/• The Product-Led Organization: Drive Growth by Putting Product at the Center of Your Customer Experience: https://www.amazon.com/Product-Led-Organization-Putting-Customer-Experience/dp/1119660874• Product Roadmaps Relaunched: How to Set Direction while Embracing Uncertainty: https://www.amazon.com/Product-Roadmaps-Relaunched-Direction-Uncertainty/dp/149197172X/• The Product Experience podcast: https://www.mindtheproduct.com/the-product-experience/• Matilda the Musical: https://www.imdb.com/title/tt3447590/• Rise on Disney+: https://www.disneyplus.com/movies/rise/6Yv1uRnw2uAJ• Miro: https://miro.com/• Figma: https://www.figma.com/• Seismic: https://seismic.com/• Gong: https://www.gong.io/In this episode, we cover:(00:00) Christine’s background(02:34) How working with Ben Williams led Christine to Lenny’s Podcast(05:02) The role of product ops in product management(07:31) How 2019 became “the summer of product ops”(11:19) The different ways product ops can assist product teams(15:50) How Pendo used product ops to bring teams together and share data(18:15) Where user research fits in (22:39) How product ops are being utilized—and not exclusively in B2B companies(24:47) How to convince a product leader that you need product ops(27:41) Why customer experience is the core of a PM’s role(29:47) Who is doing the work of the product ops person before that role is created(31:37) Christine’s response to Casey Winters’s take on ops teams(37:40) Signs your company could benefit from a product ops team(30:56) How a lack of transparency led to Pendo adding product ops(46:11) The line between product ops and product marketing(47:30) Who might be a good fit for a product ops role(53:39) Red flags for product ops roles (that apply to any role) (54:08) How product teams are structured at Pendo(57:18) Lightning roundProduction and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [e-mail]. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.lennysnewsletter.com/subscribe

Speaking as a former PM, I would not ever give up spending time with customers and watching their pain. That's how I fell in love with product, was I saw my internal customer 12 years back now, fighting with the keyboard, fighting with the mouth. And I was just like, oh my gosh, what's this guy doing? Welcome to Lenny's podcast where I interview world-class product leaders and growth experts to learn from their hard-won experiences building and growing today's most successful. products. Today, my guest is Christine at Waru. Christine is a longtime product ops leader at Pendo, a role that she transitioned into from product management. I've been hearing more and more about the rise of product ops, and I've never really understood what the role it was until I had this conversation with Christine. We dig into what product ops people do day to day, where the line is

between their role and product management, whether you should consider getting into the role, whether your company would benefit from product ops. We also have an interesting discussion around whether ops roles in general are a sign of inefficiency at your company. I learned a ton from this conversation and Christine is awesome. And so with that, I bring you Christine and Waru after a short word from our wonderful sponsors. This episode is brought to you by Amplitude. If you're setting up your analytics stack but not using Amplitude, what are you doing? Anyone can sell you analytics, while Amplitude unlocks the power of your product and guides you every step of the way. Get the right data, ask the right questions, get the right.

answers and make growth happen. To get started with Amplitude for free, visit Amplitude.com. Amplitude, power to your products. Are you hiring? Or on the flip side, are you looking for a new opportunity? Well, either way, check out Lenny'sjobs.com slash talent. If you're a hiring manager, you can sign up and get access to hundreds of hand-created people who are open to new opportunities. Thousands of people apply to join this collective, and I personally review an accept just about 10% of them. You won't find a better place to hire product managers and growth leaders. Join almost 100 other companies for actively hiring through this collective.

And if you're looking around for a new opportunity, actively or passively, join the collective. It's free, you can be anonymous, and you can even hide yourself from specific companies. You can also leave any time, and you'll only hear from companies that you want to hear from. Check out Lenny's jobs.com slash talent. Christine, welcome to the podcast. Thank you. I'm so happy to be here, Lenny. First of all, I just wanted to give a big thank you to Ben Williams, who was a previous

guest on this podcast, who suggested you join this podcast and who connected us. And we were chatting earlier, and you said you have a story about Ben. And so what is that? I do. Absolute thanks to Ben for connecting us. So when he made the intro, I was super excited, one, because it's you. And two, because I love hearing for Ben. And I was like, oh, great.

Like, he's doing all these wonderful things and whatnot. And I just remember in that moment, my first conversation with Ben, which was really early in the days of starting product operations at Pendo. And we were going through all these just really crazy things that he was going through. And his team as a customer of Pendo at the time. And he's like, sitting there just kind of staring and just, I was like, oh, you're okay? And he's like, yeah, and fine. I thought that I was just throwing him off at every turn. And he said to me, you know, I bet you I'm not the only person who has.

these questions. And I bet you I'm not the only person that's thinking about all these problems that probably seem very normal and natural. I don't know. I bet all of us are going through. This is why I'm building product ops here. But when he said it, he was just like, I really think there are a lot more people that you need to talk to about this stuff. So, and I was just, it's just kind of full circle, right? I think he connected us and he was one of the reasons I started to say one of the best things that my first Boston product always told me was, you know, have to find a way to give back. And when he said that to me, I was like, I wonder if this is one of the ways that I can start to get back to the product community. Awesome. Well, here we are. And obviously,

we're going to be talking about product ops. You've been in the product ops role for seemingly feels like as long as the role has existed. I'd love to know when you think the role actually, and we're going to talk about just like when this kind of spurred happened in product ops. And I hate this term, but it feels like you're kind of a thought leader in the product ops space. I've never actually worked with anyone in product ops. I've never had a product ops team. and so I have a ton of questions. I imagine many people listening also haven't and are also just curious about this emerging role.

And so what I'm hoping we do with our chat is to help people understand do they need a product ops team? Would that be beneficial to their company? Whether people should be considered moving into product ops, whether they're in PM or something else right now. And then just generally, helping people understand this emerging role of product ops.

Does that sound good? Yes, thank you, number one. That was really kind. And two, yes, I'm happy to dive in. Okay, sweet. So I think we have to start with the basics. What's just like the simplest way to understand the role of product ops and especially in relation to product management? I've had many ways of describing this in the past and it generally centered around the latter of what I'm going to tell you or the second part of this. But I'm breaking it down now into two, into two simple things. One is it is a thing you do. Product operations for a VP or a head of product or product manager. is the creation of some sort of system that allows you to thrive or allows your team to thrive in product management. And the second is what we've seen more of over the last couple of years.

And it's the more common definition. It's the emergence of the role itself is why it's so common. It's a person or the people, the group of individuals who are strong partners to the product manager. And then for more mature product ops teams, end up people being more strategic advisors to the head of product. So your CPO or your VP. again, when it comes to data, qualitative, quantitative, anything that they feel can help the CPU or the head of product make more strategic decisions and well-unformed decision. Got it. It feels like there's been this big inflection and emergence of the role in the past couple years, past few years. I'm curious what you think triggered that. And if that's true,

if it feels like it's just kind of emerged in the last couple years. And yeah, and then just like, why do you think that has happened? This is interesting because as a former product manager and product leader, I don't think the things are new. Absolutely. And that's what I go back to the story about Ben, it's like, I'm like, no, none of this stuff feels really interesting. And, you know, it's just stuff that we have to deal with in product. And so the problems have always been there. I think maybe that is because I have a product back. And so I felt that pain very acutely. But I will say for the majority of people who I 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. Yeah, it does feel

relatively new because they're starting to dive into that space a little bit. But I will say that for me in particular, at Pendo, it was the summer of 2019 that this really picked up. And I remember a colleague of mine, shout out to Shannon. He's no longer with this, but he was one of the original people on the Peno product team. He said, you know, I think this is the summer, the birth product tops. And I just started laughing. And he was like, I'm telling you, it's everywhere. All of a sudden, and everybody's just like, we need something. We need to make product better. And I thought that was awesome because we had already started talking about it. And so it took me a bit to understand what was going on across tech that was making this thing so big. And I'm very grateful because we have so many

great customers that reach out and say, help us understand how you're doing this. And I'm like, well, help you understand what's going on. And so for me, it went. beyond the problems that we would solve as a product team with Dependo product. It went into how can we help you as an organization solve pain that you're feeling within your product team that trickles out of the business, right? That's interesting. There was the summer of product ops. What happened there?

Why was there a summer of product ops? Why was everyone starting to get excited and kind of creating product ops teams? Yeah, I'll dive in. And it's like 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. There was a lot of pain around internal alignment and

general transparency to stakeholders up across your revenue team members. And then for a lot of people during this time, growth was a massive propeller of the need for product ops. I remember just sitting here in this office and getting these random, every industry almost was like, yeah, I'm thinking about doing this and I really need to do this, a pandemic, blah. It was growth during the pandemic, especially within industries such as home furnishings and making their living space a whole lot better. All of a sudden we started to see that rise. But we're all experiencing this massive amount of growth across some of these startups and really

rapidly growing companies. And we were also moving more towards these product. tactics, product-led growth. And all of these things, I feel like made this perfect storm for product operations to come in and sort of start calming things down. I personally believe there's this natural evolution that happens at any mature function when it starts to grow in an industry and across an organization. So think about marketing or sales, right? This just started to happen with product managers. And for me, I was sitting there going, well, you're going to appoint a PM to liaise with other ops teams and the business, but at what risk, right? Their product portfolio, the growth and

adoption of their product, all these goals that they have to hit today in order to build a better tomorrow for their customers. And so I feel like that was the moment to say, okay, how do we give them the structure that they needed to thrive, right? Because the CPO is in charge of so much more than product people have historically been in charge of, right? I'll probably talk about Marty Kagan several times here, right? I really do admire and respect him. I think one of the things that he always talks about as future teams versus, you know, high-performing teams and focusing on outcomes.

And TPO's went from, okay, deliver, deliver, deliver, to really increase business metrics or, you know, just help drive the bottom line versus just really look at the product. And you really have to figure out what that means for the product team at March. 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 kind of like a sloth, slice of the PM role that companies are finding is valuable to put on a different person that has different skill sets. They can take this like endless load that PMs have. Like PMs have so many things to do and their job is so full of responsibilities. Yeah.

That there's a sliver of stuff that a product ops person can take off. I'd be curious too. And feel free to comment on that. But I'm also curious, you mentioned a few specific things that the product ops folks do. It'd be cool to just like go through a bullet list of just those sorts of. things like you said kind of responsible for voice of the customer pieces alignment across stakeholders whatever like if you could just go through some of those that be that makes it really concrete I think for people to understand how wow this person I could have someone do all these

for me that be amazing. In some ways I've got this question a lot from product managers who are concerned about the rise of this role or product leaders who are concerned that it was going to create some sort of controversy or friction between product ops people and product managers and the way I've coached people to get around that is really what are your people responsible for? What are you holding them accountable to? Are you holding the product manager accountable to elevating the strategic insights so that they are going to elevate it to everyone else and then everyone else is going to go out there and build the thing and, you know, drive the value? Or are you holding them accountable to truly understanding the customer in whatever way possible, especially going on and talking to the customer, please don't have anybody ever take that right in? and really spending time with their engineers and the customers in order to drive a better experience, right? And so if they've got to spend all this time, which is our most valuable asset, with those two entities,

everything else still has to get. And so I think that, yes, there was a point of friction, but I feel like now it's been a nice change where I'm seeing people in products. They know, I want to do product jobs now. Who was a former product? And the second part of that, you said, let's go through the list of tactical things. And yes, voice of customer management is definitely one of the things that we're seeing more. I would say, I don't want to say mature because then I feel like I'm saying mature up your peak. But the ones who have matured a bit, I feel like they are focusing more on the voice of customer element.

So quantitative analysis, qualitative, bringing all of these different inputs that would traditionally be handled by product manager through, you know, looking across the aisle at their PMM or looking. can get different data sources to the surface when they're going through their product development and life cycle planning. And really figuring out to what that balances. I think there's an art. You can do voice of customer in two ways. You can do it one in like this process way where you're feeding it to a really mature longstanding product team who has mature product or you have this voice of customer thing that you have to do for for teams that are actually building something new. And they're really trying to move fast. So how do you really get them what they need in order to experiment and iterate on the next thing that they're doing. That's one aspect. Another one is tooling. We see this more for

folks who don't yet have tools under control in their product org. And I'm not saying everybody has this, right? We had someone at one point handle whatever tools connected to Pendo and make sure that those systems are set up for maximum outcomes for the product manager. And so Pendo is connected to Salesforce. We're connected to Looker. We're connected to all these tray, all these different, you know, And so what does the product manager need to achieve out of all those things that ultimately drives our experience for Penda ourselves? You get very meta here. That person was responsible for that.

And that's all also a part of the data component. The other things that we're seeing are more along the lines of content strategy and being really intentional about making content and education a part of the product process, right, and the delivery process. So taking a look at how they maximize the outcomes from the outcome that the product manager is driving so that they can help increase retention, growth and all of the good stuff for the product. So those are some of the things that we're seeing. And then there's also this component that happens or this piece of it that happens in the beginning when you're standing a product dumps for a product team that does not have much process in. And that's the bit that's a bit controversial because folks are like,

Is this just program management? Is this just a different flavor of Agile? And so what we're seeing is this, you know, what are these folks doing? Are they managing and facilitating the product development lifecycle? Are they doing things with the rest of the organization? So I feel like this one's a little bit up in the air. Some are actually agile facilitators as well. But I am seeing emergence of some companies that have the program management team

under the products umbrella to help with this. massive amount of things that they have to manage across the board. Oh, that's a really interesting point on the last piece. I want to dig in on that a little bit. Just to summarize what you shared, so some of the kind of key roles of a product ops person, there's this voice of customer element. And just to understand what you mean by that,

the team is aggregating feedback from customers and feedback from customer support and sales and things like that and like sharing it with the product manager to give them clear conclusions and like takeaways so that the PM doesn't have to sit there and filter their all's data. Is that a way to think about it? That's one part of it.

We actually developed this really cool way of doing it here at Pendo, which is the transparency is a word that we love here. And what we found, that there was just not this need for the Revenue Org to be transparent and say, hey, this is what we're hearing. Product people please listen or vice versa. Like, here's what we're doing for your customer.

There was this interesting moment where we realized that our sales team was screaming for something and our success team was screaming for something else, but our Tams were looking at something else, right? And so they're all wonderful, relevant things that our customers wanted, but we were like, wonder if they're aware that, like, they've got all these amazing things and they're kind of, you know, talking about it separately.

And our PMs, they would get the whole readout, you know, with us. But we brought those folks in a room together. And it was really cool because it was like, I think our head of our professional services team at one point was like, whoa, like this can truly impact what we do from an onboarding perspective. And now we have this data and then how do we then strengthen this area in the product? So it wasn't just about the component. So I don't know if other companies are doing it like that,

but I was very proud of the way we ended up doing that here. But the PM, yes, got risk data, high priority deals, feedback from our feedback product. What are we hearing from prospects versus paying customers? What segments are saying what? All that stuff got fed over to the PM and then validated through our research team or disputed through our research team, which is really cool. is a really good partnership with our research team. But on the other side, what was really nice, too, was we were able to educate our revenue team on behalf of the product team and say,

you know, guys, like not everything requires a product change. So if you're saying there's customers that have friction around this one area of this product, maybe it's enabling. Maybe it's something that we need to help you guys understand a little bit better so that you can make their experience better. Or maybe we need to help your presentation. It's just very simple things like that, that just ended up coming up this voice of customer process. So essentially, it's just finding ways to make the PM more focused and allow them to focus on the things they want to focus on and reduce workload. On the user research piece, I'm curious.

So it feels like there's a lot of, there's user research coming in, PMs are involved in user research. There's a research team. Where does the product ops team fit in there? Or is it focused on like internal alignment stakeholder feedback more versus like external customer feedback? Yeah. And, you know, again, I'll say this probably several times,

this every company is doing it in their own little bit of flavor. I'll tell you that here and from a couple of companies that I'm seeing outside a Pendop. Our user research team sits with our UX team. They report into our head of UX and they are responsible for proactive research and making sure that we are aligning to our strategy, right, and saying, okay, here's what our folks are saying, here is why we're going after this market or this new thing that we're doing. let's start going out there and validating or checking with some of these key personas, right,

and what we need to do. And then they are also a part of the ongoing development process or product development process. So, you know, testing stuff out, making sure that they're doing user interviews and all that good stuff. So if they sit as a partner to us, we work very closely together. And again, I'll give you that example of voice of customer, which is we have all of this input coming in from our customer success or post sales teams. and we know we're about to invest in our guides area of the product. We have all of this.

What do we do with it? We couple that with I'm personal or responsible for NPS, or I was for a very long time. I'm seeing a lot of noise around guides. So I take all of that, we pull it all together, and we give it to our head of research and say, all right, let's all make sense of all this together, right? Is this something that is in line with the direction that the product team is going,

the guides team, or is this something that we're going to need to dig a little bit more into to see if their efforts right now where they're growing are not, where there should be going. The other two bullet points just to kind of make sure I totally understand you help with tooling. The product ops teams helps just like optimize the tooling to build product, right? Is that a simple way to think about? Just make sure the product development process is efficient. Yeah, we partner with the program management team and the tools that they use for product development stuff. I would say it's more what are the things that the product manager needs in order to be successful. And so we look at Pendo, right? We do use our own product. Like I'm

in quite a lot. Salesforce is another thing. So how does that I'll plug into our own product and what data are we looking to get out of there? So our PMs have a complete picture in Pando. Trey is another one I mentioned. Zapier was another one that we had used. So it's more about the PM's tool stack versus the PM's planning tool stack

if you want to draw that distinction. Got it. Okay. That is helpful. And then content strategy, by that you mean internal documentation to train sales and customer support? or is there also like help the product team build out product marketing content and things like that? Oh, neither.

Or a bit. I guess what we have done is fed into both of those technical documentation, technical. Like we use Zendesk as another tool, right? So we use Zendesk as another part of our tool stack to support our customers. And so a brand new feature comes out. A 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, money, sorry. I'm not looking for you. That's right. It's actually a really good tool. So we do use Pendo guides and we just release, let's just say, we just release our NPS themes. So a pain in my team spot has been manual labor around NPS themes and qualitative data. And so we design this experience for customers who are in this beta so that they can, in the product, understand what it is.

And then if they really need more, they can go out to the technical documentation. But it's about the education for the customer. And I mentioned earlier, treating content as a part of the development lifecycle process. You really want to treat it as a part of definition of done, right? And so that team's responsible for all of them. And when you think about product-led growth and the emergence of that in particular over the last couple of years, it's all about creating that experience and keeps people in and helps them upgrade, right? And so they work alongside product marketing to develop these playbooks for what they're doing in-app

to create less friction and drive more engagement. Got it. Okay, that makes a lot more sense. Would it be safe to say that product ops is essentially for B2B companies where there's all these internal stakeholders, sales, customer support, marketing, things like that. And that's the kind of work that you can take off the product manager's plate. My personal experience, and I think all people would agree with me,

has led me to believe that's not accurate. It's emerged a lot more in B2B, or I think we, They've seen it a lot more in B2B, or at least people talking about it. And I'm curious as to why. And I wonder if it's because we're sharing because we're all trying to go through this thing together, serving each other. And then the other is serving the customer. So it's not like, hey, help me figure this thing out. I mentioned, like I was so lucky.

And I still am so lucky to work with so many people in my network, in our customer base, to help them understand the rule or determine whether they even needed this thing or not. Without calling out names, there are some really big companies in retail and finance. in some industries that you would not expect, 4B to C, larger, well-established companies who we all know and love and maybe not even love, maybe the experience is bad for us, right? So they also do have a lot more cross-functional engagement internally

than we would even think of. So I don't know if it's because we're used to this world and we haven't thought about that side of it, but it's really interesting. I think the common thread is the cross-functional transparency and then transparency out to the customer. And so I mentioned transparency is a big word for us, but readiness is another one, right?

And so readiness means a lot. You have to your teams you need to get ready internally, but you really need to get customers ready for something new as well. And everybody needs to feel aligned. So it plays a massive part in what the product manager and the product team needs to consider, advocate for, deliver, and communicate about. I feel like no matter the size or industry.

I imagine a lot of PMs listening to this, have this kind of like two-minded view right now of like on the one hand somebody could take all the work off my plate that's awesome on the other it's like oh okay there's another stakeholder after loop into every meeting and they're going to be doing this work that's kind of cool and important that man i'm not going to get to do anymore and that's weird what have you found is the best way to convince a p.m to this is like wow this would make your life so much better and this is really yeah i go back to that that question that i have asked leaders when helping them stand the which is what are you looking at your PMs to drive and how are you measuring their success?

And that generally just helps everybody get on the same page really quickly. I've had customers or I've had folks come to me in the product community that say, I've tried this and it's just not going anywhere. There's resistance to the role because they feel like it's stepping on too many toes and whatnot. And generally, generally, I will tell you, it's because they still have a bit of buying in the top to get done. And I'm seeing that the most successful ones that are drawing the lines and showing that this role is valuable are the people that have their buying from their CEO, CPO at that level or their head of product and saying, hey, this is what this role means for you.

So I don't want to say it needs to be directive. I do want to say that you need to be able to articulate the value to somebody who's heading up essentially businesses, right, and saying, here's what this role is going to drive for you at the end of the day. the very mature product ops orgs end up having people that are strategic advisors to a product leader. And so once you can show that this is what you'll also get as a result of me and this other person or me and this team doing this, it ends up being an easier conversation. What are like a couple bullet points that are most effective to convince a product leader? Product ops is going to make a big impact and benefit you. And then just like an ICPM is like, I don't want this person on my team.

Like, what actually works there to get buy-in? Yeah, number one, do you want your PMs to constantly be fielding questions from your revenue team when they could be spending time with customers? Yeah, you're shaking your head. That one seems to be the one. Yeah, that's a good one. Yeah, I can count on one hand the companies who have blocked their product managers from speaking to customers. And those companies are not product companies. I mean, they do not believe in product management.

They might say they do, but they don't. So that's number one. number two is how are you measuring your outcomes? And where are you making this all transparent, right? Is this happening consistently across the board? Right. So one probably we see in product teams across, I mean, 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. So how are you doing this at scale so that your stakeholders are building this trust in you and making sure that they get the best out of the product team in any given turn.

I say those are the two bullet points that seem to stick the most, is that quality time giving the PM what they need, which is their time, to be able to drive the outcomes for the customer. What is it that you think a PM will never offload, if that makes sense? Like, in your perspective, what's like the core of a PM's role versus maybe product ops for now and then maybe potentially other roles that take off some of the stuff on their plate. Speaking as a former PM,

I would not ever give up spending time with customers and watching their pain. That sounds really bad customers, I'm sorry. But, you know, that's how I fell in love was product, was I saw my internal customer 12 years back now

fighting with the keyboard, fighting with the mouth. And I was just like, oh my gosh, what's this guy doing? And I think, it was an experience that some people might say, oh, I never want to be in that situation again because it made me feel very uncomfortable that my product is not doing for this person

what it needs to, but for me, it was how do I make this thing do what it needs to for this gentleman? How do I make this thing better? And I cannot see product managers saying, I don't want to be a part of that conversation. Then you know what? I'm going to say it, then don't be in product.

I love it. Yeah. I'm so curious what parts of the role. get sliced off over time because I love that that's the core of it. It's just like build great products that your customers want and use and want to pay for. And then what else can people help you with along the side? Because, yeah, if you have a role, it's just crazy. So many things going on.

It's crazy. This article that I wrote, I dug into the history of product management. And it's like 100 years old in its form right now. It's true in this current form, but it's about 100 years old. And just the evolution of what product managers have historically been responsible. before. And then if you think about just really sit down and think about what the world is turned into today and how much noise we have coming at us, right? We talked about put yourself onto not disturb mode. And I learned a long time ago, put myself into the disturbed mode.

And so imagine having a partner that helps you filter that noise. Yeah, quite useful. Yeah. Along those lines, I was going to go in a different direction. But as you mentioned that, There's all these roles adjacent to PM. There's program managers, project managers, agile product owners and all. And then now product ops. I guess before a team has product ops, let me just ask this one straightforward question. Which of those roles generally does the thing that product ops can do for you? Is it the PM or is it one of these other roles?

It's a PM. It's a PM. Okay. 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. So

I would say it's a PM and maybe the Agile or yeah, right, that's probably what it is today. I feel like program management and agile are starting to get a little bit close to each other in what they do. And so it's most of the PM stuff because we're doing elements

of their job that they have off to the side versus being able to focus on. But again, in lesser mature orgs, the first thing is How do I actually just get the people to plan the same way and give me the thing that they're planning to do it? That's interesting what you said there. That may be often a wedge to a product ops person joining their company maybe as a first product ops person, as the planning helping with the planning process.

Is that kind of what you find? It could be the only thing that distinguishes product operations folks from program managers and Agile is that product operations people know, understand the product, the customer, and the inner workings of the business. Cool. Yeah, Marty Kagan has some hot takes there about how product owners are never going to, never going to be great product managers. They don't really understand the customer needs and building product. Anyway, that's a whole other topic. I want to talk about the career path, but before we get there, I want to go in a spicy direction. So Casey Winters, he is a guest on this podcast at one point. And he wrote this hot take many years ago about this kind of premise that operations in general often is kind of a, a, like a band-aid for inefficiency at a company. And companies often hire a bunch of ops people to just solve a problem. And often, there are much better ways to solve that problem. For example, tooling or a new process.

And his take is often a person doing the thing as often should be the last resort. Or it's like a temporary gap. And then over time, you should strive to find a more efficient way to solve that problem than people. and I don't think he's saying like ops people in general or not necessary. It's just, it's an easy default. So I'm curious what you think of that take.

And generally, do you think product ops is this long term we're going to need more and more of this? Or is there, I don't know, different path that's solving the problem that product ops solves and spicy take warning? Yes, I remember this. I'll address that inefficiency comment first, right?

I mentioned a little bit earlier as roles in any industry, or I guess any role matures, like marketing or sales, this ops thing ends up being this natural progression. And it's not just because the role itself is maturing, it's also because the org is maturing. So what I found is, and what I'm finding with customers, is that ops alignment across companies

is what often ends up keeping the companies moving and keeping everybody aligned. And so to say ops teams are generally a sign of inefficiency or the need for them as a sign of inefficiency is not always accurate, it's generally a sign of growth and opportunity. And people are really just trying to stay in line and do the best for the people that are doing the thing, the product managing, the marketing, the selling within that org.

Overall, though, I will say I will agree with his points about getting in and maybe giving it off and using humans for other things. I wrote something recently, and I highlight something that he mentions here in this article and what he mentioned on your podcast, which is ways product ops want to and should be standing up whatever processes or systems are needed

and then get out of the way so we can focus on driving more strategic value. I keep mentioning that more mature product ops folks end up being a very good strategic advisor to leaders in product and to the product teams. And that continues to be my belief. From day one, this has been my own personal goal for myself and for my team. I myself recently switched roles here at Penn.

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 we're 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. Some of those are how do we increase retention? Like I mentioned, how do we focus on growth in this one area? How do we make the experience better in app? How do we do more better voice of customer management? My energy now. I'm able to now go towards more impactful things for not just the product team and the product community, but for our customers at large. So I'm basically saying, I did what I needed to do,

and I'm ready to go. So I think that's something, though, that people need to be very, very comfortable with, like, very comfortable with. And if you change course and change your tune two, three years into doing this and you built this team, you're like, here's what you're doing. Manage this process. People are going to lose their minds. Like, change. Change is constant, but telling someone, I no longer need you to do that. It makes them a little bit nervous, right? So for years when I was interviewing folks for my team, I made that one point abundantly clear to them. Get into this role if you're comfortable letting go of things and moving on to something that is well worth your time.

The company is going to change. A process is going to need to be tweaked. The company is going to change. Something's going to need to be automated. We're going to need to cut something else. Maybe chat TPT is going to make things. very clear that humans are not always going to be doing the same things and we need to focus our energy elsewhere, but people do need to get comfortable with that. I love that take.

Generally, I think it aligns with what Casey's saying, like what you're saying, what I'm hearing is you may be a product ops person today doing a bunch of stuff. Your job, in a sense, should be to automate as much of that as you can and find more strategic higher level things you could be doing instead of sitting there connecting Salesforce to Zendesk and, you know, maintaining that. Or I could be creating customer feedback in theory. It could be a tool that could do that for you. And that's kind of part of the job. Is that roughly what you're saying?

That's exactly what I'm saying. This episode is brought to you by Vanta, helping you streamline your security compliance to accelerate growth. If your business stores any data in the cloud, then you've likely been asked or are you going to be asked about your SOC2 compliance? SoC2 is a way to prove your companies taking proper security measures to protect customer data and builds trust. with customers and partners, especially those with serious security requirements.

Also, if you want to sell to the enterprise, proving security is essential. Sock 2 can either open the door for bigger and better deals or it can put your business on hold. If you don't have a sock 2, there's a good chance you won't even get a seat at the table. But getting a sock to report can be a huge burden, especially for startups. It's time consuming, tedious, and expensive. Enter Vanta. Over 3,000 fast. growing companies use Vanta to automate up to 90% of the work involved with SOC2.

Vanta can get you ready for security audits in weeks instead of months, less than a third of the time that it usually takes. For a limited time, Lenny's podcast listeners get $1,000 off Vanta. Just go to vanta.com slash Lenny. That's V-A-T-A-com slash Lenny to learn more and to claim your discount. Get started today. Zooming out a little bit and kind of building on the stuff we've been just talking about, What would you say are just signs that your company would benefit from a product ops team

and that you're kind of a fit for building a product ops team? I touched on us quite a bit, but that lack of transparency in many directions up, across, down sometimes. Like, people aren't very transparent about, hey, this came up planning and here's what we need to do. So it's relevant for, you know, stakeholder management, getting stuff out to customers, internal teams and making sure they're aligned. Revenue teams in particular, that was the first thing we focused on. Appendo was really aligning our success org and our sales org to the product team.

And we monitored success just within, I think it was a quarter, was the time bound space that we headed in on quality of inbound to the product team. So that was really cool. It was just more like thematic questions around tell us what you guys do because our customers would benefit from this versus teach me how to do this thing. I wanted to dig into the transparency piece. Is that the same point as the transparency piece? or those two different kind of heuristics?

That's transparency, yeah. So what happened was we realized that we share this story actually quite openly, and I'll share it here again, which is one of the things that kicked off products for us was we had a really bad launch, a really, really bad launch. And it was a moment in company history where we realized that there was not transparency across the aisle, and there was this lack of readiness across the organization and out to customers for what was coming. It wasn't this piece that folks say, oh, well, they didn't.

know this was coming? Well, there's two things. There's the knowing something's coming, and then there's the knowing what to do with. And you can use just some sort of status keeping thing to say, this is coming in Q4, and as you get closer, here's the date. But it's what to do with it and how to position it and how to talk about and all the things that was missing from. And it was really bad, money. It was really bad. And it was my fifth week here. And it was a moment of, well, I promised myself, I'm not going to let this happen. That was one of the things where I said, I'm going to start to focus a little bit more on product ops within this director position I had just as director of product. And then I spun off and I think we need to do this thing and make it a bit more formal.

Just to dig on the story a little bit. So I didn't know this. So you were a product manager at Pendo. There was this huge, let's not say a disaster, bad, bad launch. And you kind of recognize there's this gap that maybe I could fill that somebody needs to fill and that you want to take that on. Can you talk a bit more about that? That's really interesting. Yeah, they brought me in as their first director level. And so I was doing a bit of director plus a little bit of I-C stuff because we were starting to build up our product team. And yes,

that lodge happened. And the product area was under development for about eight months from what I can remember. And I came in with the assumption and also knowing fully well that I am a brand new layer in this product team and product people want ownership. They crave autonomy. They crave trust and all of that good stuff. I know that firsthand. I did not want to jump in and say, have you done X, Y, and Z, especially in the first four weeks of me being there? And yeah, it did not go very well. And so we recognized that we had more opportunity that we should have grabbed on to to test more with customers, to find feedback loops that were going to be healthy for the team and for our customers, to stand up ways for us to measure changes and

impact of changes that this thing was making to our customers. This was the biggest launch in our company history since the launch of the product. And so it was a moment where we all sat down very openly and shared with each other what we all could have done better and it wasn't just the product team. So, you know, I truly believe with a really healthy product operations person or team, you have that ability to impact change across a company. And so, yes, we look at that story and one day, I remember us sitting there and one day we're going to look back at this story and we're going to saying, oh, I remember that, and we do now, four years later or four and a half years later. But, yes, I felt really passionate about making sure that that didn't happen.

The gaps you found are there's just like this lack of internal alignment sales, didn't know what was going on, customer support, didn't know what was going on. Like that, felt like that's where the gap was, because that's kind of what led to this product opportunity, right? Yes, there was a lack of alignment across, again, like, they knew it was coming. They just didn't know the extent of what to expect and how to prepare. customers or prospects for the change the way that we should have. There was definitely training. There was stuff being done. It just could have been a whole lot better. So there were gaps there.

One more point was the piece after that was, you know, I love people. I love managing people. I love healthy team environment and dynamics. And that 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. And I remember even in my early days of being at PM, I wanted my engineers to be super happy. I wanted them to be proud of work that they were doing and I wanted them to be comfortable letting go of things that we no longer needed. And I remember that moment being like looking around and looking at our engineers and seeing

that they were like, hold on what, like, you know, where do we go now? Like, what do we do right now? And, you We wanted to take that moment and make it less about firefighting and more about being responsible and really customer obsessed. And so, you know, that was our moment, our moment or one of our moments for thinking about, okay, we might need product operations formalized here. It's interesting that your mind went to product ops because I think most companies would be like, oh, the product manager of this product screwed up. They didn't communicate enough to insurance sales. They didn't set up the marketing material well. You know, it's like often falls on the product team. product manager. What made you realize, oh, this is a product ops role and I need to move into

that role versus there we are? Yeah, I didn't say in that moment we need a product ops rule. All I said in that moment was we need to create a system so that this doesn't happen again. And that goes back to my definition of what product ops is. It's a thing and it is also a person or a group of people. So it could be one or the other, right? So I want to make sure we decouple that. It does not have to be humans. It can be that there's a system being created that is from, I'm a strong product person who knows how to get this team to be healthy. That's a really good way of thinking about it. That clarifies it in a big way.

Thank you. You were talking about transparency and just like a sign that maybe you need product ops. And I think the thing that stuck would be there is just the quality of questions the product team gets from, say, sales, right? Is that kind of where you narrowing? Yeah. I get a lot of questions around, you know, I'm investing in this. Like, how do I measure the effectiveness of the team, like all of these things? and it is really not easy to measure this in a quantitative measure just yet. Maybe one day, right?

Actually, yes, no, one day, I feel like it might be coming sooner than we think. So what we did was we looked at that transparency problem. We sent out this survey across both product managers and the sales and success teams. And we said, you know, where's your time going PMs, right? And how much time are you giving one average to the revenue team to firefight? How much time do you have with customers? It's quality time. And then on the flip side to the revenue. And then on the flip side to the revenue. And then on the flip side to the revenue. And then, team, how many times do you find yourself asking questions? You know, like, and we gave all of these like, you know, one to five, blah, blah, blah, those sorts of things so that we can figure out where to place our energy. And we came up with this, okay, well, it seems like there's a lack of transparency across the two groups. Let's start with getting data out or information out to the revenue team from the product org. We created this product digest. It still exists today and it's matured quite a bit, but it, I go back to this whole, people can know when they're coming, but they

need to know what it is they need to do with it. So this thing was less about this thing's coming next quarter to go tell your customers it's more about here's how you get ready for it. Here's how you get jazzed about. And then the handoff, which is probably a question you're going to have at some point, which is what's your line between PMM and products. The handoff is that we don't teach them to sell. We don't teach them to position. But we know that the product intimately enough to help them understand the new value, to help them understand how to use the thing and to make sure that they're hitting the ground. Let's ask that question if there's anything anymore. And what is that line between product ops and product marketing? Yeah, I always say this.

And it's worked. I haven't seen anybody dispute it yet. But product marketing positions and helps the revenue team sell. Their lead gen, you know, for all of the outbound and the campaigns that they're running. And they are marketing, right? They're helping you at the end of the day, make this thing sound amazing and do the right things with it. And for us, it's about educating. It's about helping our internal folks, our internal revenue team, understand what is the added value? How do you now do this thing? How does this impact your role, right? We focus a bit on the customer success persona, for example, on PENDO.

Customer success managers can go in, they can see their account health and what's going on and blah, blah, blah. How does this impact you as a customer success rep? And how do you then help your customers understand the value from? Not, hey, can you help us upsell this thing and here's how you do it? Great answer. Makes a lot of sense to me. Final topic, the career path of a product ops person. A lot of people listening to this podcast are either PMs today or I want to be PMs or thinking about becoming product. And I'll say product manager because PM can mean a lot of things.

And it's interesting there's this new path that people can explore product ops. I'm curious who you think might be a fit for the product ops role versus the product manager role, like someone deciding, oh man, maybe I should go down this other route. What do you think are just signs that maybe you'd be a better fit where you enjoy that better? I love that question because it makes me feel that this role has become embraced a bit more when I hear questions. Like in the past it was, do we need this role and how do we help get the buy-in?

And now it's more the acceptance of a product manager to maybe one to even become this. And I'm seeing more PMs, like I said, go into the space. So it's no longer being seen so much as a threat. It's being seen as this partner. and I love, so just one, I'll say that. I think if you're someone like me who absolutely loves, and I mentioned the story about the engineers and the team health and stuff, if you love creating that healthy team environment and one where there's cross-functional collaboration

and it fuels you to empower the team more, it's a wonderful fit for you. Again, I was a PM for years and I felt that pain so much and how much we had to do in order to make this small change and then figure out whether it's valuable. and I knew that there had to be a better way to get better outcomes to happen. But I also know that better outcomes don't just mean for the product. It means better outcomes for the entire product team, for the customer experience at large, and ultimately for the business.

And so I think that that's one thing. If you're curious and you really want to learn more about that side of the house, one of the beautiful things I saw was one of my product managers, fall more in love with understanding the business as she was starting to mature in her product. career and I thought that was really cool. She had already had product background and she was like, I want to understand the inner workings here so that I know how to help these people. So the other thing is I think if you're a PM having issues with the role that you're currently in, I think need to remember that you are there to solve problems. And that's a very simple thing that we talked

about. What are the things that PMs won't shed and shouldn't shed and then go and talk to customers? we have to talk to customers in order to solve the problems, figure out the right problems to solve. You do that in product ops as well. You don't have to go out to customers externally, but my customers and the people I speak to are internally. And they are helping me understand

the pain that the product team is tied to. So if you don't love solving problems through building brand new features and building a product then how can you help contribute to solving other ones if you're true problem solve or think about whether you want to do that. So if you know the pain, what can you do to build a better

experience overall can ultimately impact your business. Do you find most product ops people, at least at this point, are former product managers? Like, what would be the pie chart of last job was product manager versus not of existing product ops people? I got to put out in a new survey. I do. I really have to put out on a survey. Initially, I saw a lot more folks moving in from management consulting, from customer success, from technical success. I haven't seen anyone from sales move in yet. And I have seen a couple PMs. Now, that's the day-to-day prod-ops manager. I will tell you that the people who are standing up the product ops orgs and being the first prod-ops higher, the kind of like leadership level, are former product people. And 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 are, you're very quickly realized where to place your efforts and where your team's effort should go. And that helps you from an efficiency perspective. And the business knows you're not just dilly-dallying. That's really interesting. That makes a lot of sense. Just the roles you named again, where product opt people come from, he said customer success. What are the others again? I have seen technical success. I've seen management consulting. Yeah, that would that, the management consulting piece makes a bit, makes a ton of sense to me. I think there's a data piece that they really

like to lean into an advisory. But yeah, and then the leadership one's coming in from product leader roles. And that's been a happy change too, right? Seeing a director say, I know want to move into a position to coach the teams and to help build a stronger product team overall. And I don't feel like building product. Fascinating. For someone that's like, wow, I want to do this job. This sounds rad. What advice would you give for people to pursue this role and get a gig in product ops? Well, one, it's a good thing that there's no shortage of these rules. I would say that there are a lot of these roles open out in the industry.

Be intentional about what you want to do because right now it's still in a bit of, well, what are we doing in product operations as a product management community? And there's no consistency, industry to industry, size to size, team to team. It is very different. So really think about your strengths. Do you love data? Are you a person who thrives on being able to make beauty out of this mess that you're seeing, right? And advise people and help them understand maybe this is a direction that we should be going in.

Are you technical where you're like, no, I actually really enjoy doing the quantitative side of things. And you love, you truly enjoy working with data science teams and you really like to bring that data aspect to the product team. You could probably find a mix of both, right? There are people who like doing both of those things. do you thrive on just generally I mentioned this and I keep saying it like standing up that system because you know that if you had it you would have been a better PM. Like I think that that's a big thing there. If people realize that there's a better way to do it and they no longer have to do it all,

but they can do a slice of it in order to drive efficiency for the organization, then start, you know, thinking about going out there and doing it. And the other thing too is look at those roles and make sure that you find tooth comb those job descriptions. some of them are very big because they're trying to figure it out on their own as well. So the more you know what you want to do as a chronic person, the more you know what to lead out from these roles. Are there red flags when you're looking at a product-out-the-job description

of like, this isn't really the kind of role you want? I think this is a red flag for any role. 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 regular. That's table stakes.

People need to have on their job descriptions. Final question? Yes. Something I try to get to with people from new companies that I haven't talked to before is just to get a general sense of how the product org is structured at the company, just because people are always curious, just like how do you structure product teams? And so I guess broadly, I left you here just like how is the Pendo Tea product team structured, like what are the buckets? And then also, is their product ops person integrated

into each cross-functional product team? Yeah, I too love to learn about this. We're broken into major areas of the business or revenue streams, and we have general managers over those. And the GMs actually sit in the product team, which is nice. All have PM background. All really, really experienced and incredible. We also have a head of growth. So there's that component to it as well. Then you generally got the senior directors, their teams of product managers who are responsible for different areas in the products. So we've got one product that's our core product and very mature broken down into different components there. We have a newer product where that's just one straight product team versus like having many different directors. We do have a product ups person

integrated into these teams. I'd say probably all of them at this point. But the key thing here is they share themselves across two or three teams. Something going through listeners minds right now is Christine, is there a ratio of product dumps people to team? I would say that at one point I felt like there might have been and I don't think that I don't think that's the case anymore. And it's again, based on my experience and I'm learning, we operate pretty lean and a lot of people are having to operate. It's very lean right now. So every few quarters, we look at our goals. We determine who or what goals need a product ops person and for what reason. We're really intentional about it. As an example, I use this saying respect the hustle with my team a little bit for the newer product that's still

kind of finding its way. And the last thing you want to do as a product with somebody who I had a legacy product in my last job, one that I was building from the ground up and one that I was just responsible for getting out the door sunsetsetting at some point. You don't want anyone stifling creativity with any sort of process or some time bound this or anything like that. So the last thing you want to do is introduce something in there that feels like that. You want them to hit the ground running. And so we don't over index on things like a certain planning process or, you know, you need to get this to us because the other teams have. It's like, we need to know this thing by this time frame. We'll do what we need to do from there.

That's it. And we're also quicker with the data, right? Like voice of customer stuff takes a little bit longer for a more mature product team and or. This is more like, what are we learning right now and how quickly can we communicate this over to that team so they can iterate really quickly. Awesome. And to come back to the structure just briefly, so you have GMs, business units, within the business units,

you have directors of product, the report up to the GM, within each and the directors of product have cross-functional product team that they operate that build specific features and elements of the larger product. And then there's a product ops person supporting some of these teams

and they share it across teams. Yep, and you've got, everybody rolls up to a CPO. CPO's got, yes, got all of this. Christine, with that, we've reached our very excited, Lightning Round. I've got six questions for you. I'm going to just fire them away. Does that sound good? Yes, let's do it. Let's do it. Two or three books that you recommend most to other people.

Classic is inspired by Marty Kagan. It's one of the reasons I really fell in love with the product. It's inspirational. Leaders Eat Last. Simon Zinnick, I really like that book too. That's more leadership style and making sure you're putting your team first, which is something I strongly believe in. This is a plug, but I also really like the book and it's very practical so it falls in that category which is the product led organization by our CEO Todd Olson. Really good book for right now especially with people really going through this transformation. And there's an old box when I have that's standing on that shell. It's product roadmaps relaunched. It is really old. Like I mean, I don't want to date myself, but it's almost 20 years old when I was in college. But it's really, really valuable. And I can I can reference it just for a quick, oh yeah, I forgot about that.

from a communication perspective for a roadmap. Like, this is really cool. Favorite other podcast? The Product Experience Podcast for Mind the Product. I really like that one. A little bit similar to this other favorite one I'm on right now. But lots of really good product people and just very practical advice too. I really like the, for leadership, I like HBR IdeaCast.

It's just, again, I like to balance the business side and the people side with the call on leaderships. Favorite recent movie or TV show? Because I have kids. my brain is flooded generally with kid shows. I would say this year, it was between the new Matilda movie, which is based on the Broadway

production, which was based on the old Matilda movie, but it's really, really good, really well done. And then there's this movie, I think it's called Rise. Have you seen it? It's about the Giannis. I cannot say, forgive me his last name, but he's on the Milwaukee Bucks,

basketball player. It's about overcoming adversity and just struggle and really pushing through and giving it your all. And I think that one is a really good one. Add it to your list if you have and it's called Rise. TV, I have food. I don't have a favorite TV show. I've just finished watching White Lotus if that was qualifies. It's a,

the most popular mentioned TV show on this podcast. Yeah, I would say for TV in general, you give me anything food. I love cooking. I'll cook an entire massive meal, three-course, whatever, sit down and eat it while I'm watching. So, yeah. Yum. Favorite interview question that you like to ask when you're interviewing people? If you could choose any career outside of what you're doing, what would it be in life?

What do you look for in an answer there that tells you that this is a strong candidate versus not? There are skills that are a part of that other role that I would lean into. So like if somebody were to ask me that question, I would tell you a chef. And it's about experience and it's about constantly refining your craft. And it's about constantly looking to delight. And I think that speaks to my love for product. It's all about that and state for the customer. So I always ask that question and I look to see, you know, what is it?

Are they looking for fame? Are they looking for, you know, just a temporary role? It's really telling. Like you dig into the qualities of what makes a good. good candidate for the other thing and you can figure out a lot. Fascinating. And if they're watching this and learning the secret, that's a good sign too. They're doing the research. Yeah. Top five SaaS products that you love, use at work other than Pendo I got to think Penda. We already know. We already know that's on the list. I have Penda.

Yeah, I love Mero. I love Mero so much. During the pandemic, this became an essential tool for so many teams. Like I brought it into our company and I was a big advocate for it in my last one as well. just the collaboration and connection. Figma along the same lines, I think Figma's really great at that for our design team and the rest of products. So that one's been really good. Seismic is one that I really like as well. That's the content management system for our go-to-market teams. So it really plays well into like that. How do we make sure we give them what they need and the tool that they need to be in? Gong is another one. I think gong's really great. I've watched them go from the early days and we were, I think we were an early customer or we were using it early on.

And just the way that they help, they'd pivoted, I think they pivoted at some point or they've definitely up there messaging on the coaching for their teams. And us being able to dig into the qualitative insights that we get on those calls as product people is really good too. So yeah. Great list. Ones that people haven't mentioned before. So that's always fun.

Final question. What's something relatively minor that you've changed in Pendo's product development process that has had a tremendous impact on the way that you built product. This one's going to sound really elementary. So, or for some people, really elementary. But for some people, they're going to be like, uh-huh, I totally feel that. Early on, we started bringing in engineers to customer meetings more and more. And, you know, you don't want to typecasts or profile an engineer, but generally they're

not raising their hand really being like, yeah, I'm going to come and join blah, blah, like they wanted to make sure they're doing their job and building the experience. But it's so simple and it's so effective. And when we started doing it, the response from the engineering team was great. And then also it helped us dig into a different side of the customer while we were on call sometimes. Some of them were flies on the wall. Some of them were actually engaging with the engineers and help them increase their confidence in speaking to customers. So I don't know.

I feel like that just ended up changing a lot of the way that we started planning and making sure that their voice had a certain amount of weight or even more weight than it. it before in the product development life cycle. We respect their time. I remember some were very nervous and were like, oh, I got to do all this other stuff. But, you know, they're like, okay, I'll try it. And then all of a sudden, they're like, well, I really want to do this more and more. But it's just really being able to see that pain for them firsthand from a customer or the delight and frustration was very impactful. So that's my answer. And I feel like if you're not doing that as a product manager or product leader, then you better get on that train real fast. Because it really, it's life-changing for the entire team.

That is an awesome answer. This is the first time I've asked this question. I think I'm going to make it a standard question now because I feel like we're going to get all kinds of cool nuggets. So thank you for starting it off with a bang. Christine, thank you so much for joining me. I learned more about product ops in an hour than I've learned in years and years of reading about it online.

And so thanks for making the time. Thanks for sharing all your wisdom. Two final questions. Where can folks find you online if they want to reach out, learn more, maybe ask you some questions, about product ops? And then how can listeners be useful to you? They can connect with me on LinkedIn. You'll put that up on shore. Twitter, same. And I've got my own site to theproduct heart.com. Started posting on product management, prod ops. I'm going to start doing some stuff on careers,

all that good stuff. How can they be useful? So don't laugh at me, people. I needed a Twitter reset. And so I had that for 13 years, and then I no longer did. And now I do it. So it just helped me rebuilt over there and just kind of get get back on that site. So long term, that's more immediate, but I would say help me understand what's going on in product and product apps. I will continue to do things like this and share more about what I'm learning, but I need to learn more from other people as well. And that's an amazing, incredible part of my job that I'm about to do. And there's, there's just a lot of pain right now all around us in the tech industry, I think about today and probably the next year or so. And for people who are really questioning their next steps in their product

careers, whether they stay in it, whether they, you know, move into something adjacent or relevant, they're looking to sharpen their skills, maybe make a slight pivot to ops, whatever it is, right? I'm really interested to just gather more data on this and see how it all plays out while also trying to see if I can make some connection. So I've been able to do that. Let's go full circle back to Dan. Like Ben did this for me and you, right? I think that it's really important And the product community is smaller than we think. It's large and it feels expansive, but it's smaller than we think. And I think we're all facing an interesting time where people may be again questioning that next move or struggling. It would just be amazing for us to share.

So cheesies as it may sound product ops for me was an easy way to be able to connect the dot and be that partner, right? Talk about the transparency and alignment. And I just, if there's a way that this community can help empower me to do more of that, for all of you, I think that that would be incredibly helpful. What a beautiful way to end it. Christine, thank you again for being here. Thank you. Oh, this is so fun.

So much fun. Bye, everyone. Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review, as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at Lerner. Lenny'spodcast.com. See you in the next episode.