💡

InsightHunt

Hunt the Insights

C

Christine Itwaru

Episode #60

Product Operations Leader

Pendo

👥Team & Culture⚡Execution🔍User Research

📝Full Transcript

13,211 words
Christine Itwaru (00:00:00): 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 mouse, and I was just like, "Oh, my gosh. What's this guy doing?" Lenny (00:00:23): 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 Itwaru. Christine is a long-time 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 was until I have this conversation with Christine. (00:00:49): 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. So, with that, I bring you Christine Itwaru after a short word from our wonderful sponsors. (00:01:15): 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 lennysjobs.com/talent. If you're a hiring manager, you can sign up and get access to hundred...

💡 Key Takeaways

  • 1Product Ops is not just a role but a system; if you can't hire a person, you must still build the system to shield PMs from internal noise.
  • 2The primary signal that you need Product Ops is when PMs spend more time fielding internal questions from Sales/CS than talking to actual customers.
  • 3Distinguish Product Ops from Product Marketing (PMM): PMM helps the world understand the product; Product Ops helps the internal revenue teams understand the product's value and readiness.
  • 4Use a 'Product Digest' not just for status updates, but to teach internal teams how to get customers ready for changes.
  • 5When analyzing Voice of Customer (VoC), bring Sales and CS into the same room; often their needs conflict, and they need to hear that friction directly to align.
  • 6Product Ops should aim to automate its initial tactical work (like manual reporting) to evolve into strategic advisory roles over time.
  • 7Bringing engineers into customer calls is a low-effort, high-impact way to increase development velocity and empathy.

📚Methodologies (3)

👥 Team & Culture

A diagnostic framework to measure the inefficiency tax currently levied on Product Managers by internal stakeholders.

Core Principles

  • 1.Survey the Product Team: Quantify the percentage of time PMs spend on 'firefighting' internal questions versus 'quality time' with external customers.
  • 2.Survey the Revenue Team: Quantify the friction Sales and CS experience in getting product answers (e.g., 'How often do you have to hunt for information?').
  • 3.Identify the Transparency Gap: If PMs feel overburdened but Revenue teams still feel uninformed, you have a structural transparency failure, not a personnel failure.
  • +1 more...

"Do you want your PMs to constantly be fielding questions from your revenue team when they could be spending time with customers?"

#product#viability#audit
View Deep Dive →
⚡ Execution

A structured communication strategy that shifts focus from 'what is launching' to 'how the company gets ready' for the launch.

Core Principles

  • 1.Decouple Awareness from Readiness: Knowing a feature is coming (Awareness) is different from knowing what to do with it (Readiness). Focus on the latter.
  • 2.Create the 'Product Digest': A curated internal publication that translates feature updates into actionable steps for Sales and Success.
  • 3.Define the PMM vs. Ops Line: PMM handles external positioning; Ops handles internal value education (e.g., 'How does this feature impact a CSM's quarterly account review?').
  • +1 more...

"People can know when [a feature] is coming, but they need to know what it is they need to do with it."

#internal#launch#readiness
View Deep Dive →
🔍 User Research

A governance model for ingesting, validating, and acting on qualitative and quantitative customer feedback without overwhelming PMs.

Core Principles

  • 1.Aggregate Diverse Inputs: Combine NPS themes, risk data from churned accounts, and high-priority deal blockers into a single view.
  • 2.Convene the 'Revenue Room': Bring Sales, Success, and Product leaders together to review the aggregated data simultaneously. Let them hear each other's conflicting priorities.
  • 3.Validate via Research: Use the Product Ops team to hand off these raw themes to User Research for validation (is this a trend or a loud noise?).
  • +1 more...

"We were able to educate our revenue team on behalf of the product team and say, 'Guys, not everything requires a product change.'"

#cross-functional#synthesis#research
View Deep Dive →
← Browse All Episodes