Lenny's PodcastUnderstanding the role of product ops | Christine Itwaru (Pendo)
CHAPTERS
- 0:00 – 2:39
Christine’s path from product management to product ops at Pendo
The episode opens with Lenny introducing Christine Itwaru and framing why product operations is suddenly a hot topic. Christine shares her product roots and the customer empathy that shapes how she thinks about product work.
- •Why Lenny wanted a dedicated deep dive on product ops
- •Christine’s PM background and customer-first mindset
- •The episode’s goals: define product ops, when to hire it, and career considerations
- 2:39 – 5:01
How Ben Williams connected Christine to the show—and validated the need for product ops
Christine tells a full-circle story about an early conversation with Ben Williams, who pushed her to share product ops learnings more broadly. The story highlights how common product-org pain points are—and how product ops emerged as a response.
- •Ben’s reaction: “You need to talk to more people about this stuff”
- •Early product ops challenges at Pendo mirrored across the industry
- •Christine’s motivation to “give back” to the product community
- 5:01 – 6:11
Defining product ops: a system you build and/or a team you hire
Christine breaks product ops into two core definitions: it’s both an operating system that helps product teams thrive and a function (person/team) that partners with PMs and leaders. Mature product ops teams evolve into strategic advisory partners to product leadership.
- •Product ops as “a thing you do”: creating systems that help product teams thrive
- •Product ops as “a role”: a partner to PMs, and later a strategic advisor to product leaders
- •Using qualitative + quantitative inputs to enable better decisions
- 6:11 – 10:45
Why product ops suddenly took off: the “summer of product ops” and the perfect storm
Christine explains why product ops felt like it “appeared” around 2019, despite the underlying problems being longstanding. Growth, product-led motion, and rising expectations for cross-functional alignment created the conditions for product ops to accelerate.
- •Problems weren’t new—visibility and urgency changed
- •2019 as an inflection point (plus pandemic-era growth pressures)
- •Voice-of-customer synthesis and internal transparency as recurring drivers
- •CPO expectations expanding from output to outcomes and business impact
- 10:45 – 16:07
What product ops actually does: core responsibilities and where friction can arise
Lenny pushes for a concrete list of what product ops teams handle day-to-day. Christine covers common scopes—VoC synthesis, tooling, enablement/education, and sometimes process/program management—plus how to avoid role conflict with PMs.
- •Clarifying accountability to avoid PM vs. product ops friction
- •Voice of customer: synthesizing inputs and feeding planning cycles
- •Tooling: optimizing the PM’s “tool sack” (data + systems connectivity)
- •Education/content as part of “definition of done,” especially for PLG
- •Early-stage product ops often starts with process/planning standardization
- 16:07 – 18:24
How Pendo operationalized voice of customer: transparency and shared data loops
Christine shares how Pendo used product ops to bring sales, success, TAMs, and services into the same room to align on what customers were really saying. The goal wasn’t just collecting feedback—it was creating shared understanding and action across teams.
- •Different revenue roles hearing different (often conflicting) customer needs
- •Using shared sessions to build cross-functional alignment and readiness
- •Segmenting feedback (prospects vs. customers; by persona/segment)
- •Reducing unnecessary “product change” asks via enablement and docs updates
- 18:24 – 22:37
Where user research fits: partnering with UX research to validate and focus insights
Lenny asks how product ops relates to user research, given PMs and research teams also gather insights. Christine explains the division of labor at Pendo: research runs proactive and evaluative research, while product ops aggregates operational signals and partners to synthesize priorities.
- •Pendo’s research team sits under UX and supports strategy + ongoing testing
- •Product ops aggregates operational/customer signals (e.g., NPS noise, VoC trends)
- •Collaborative synthesis: product ops + research to validate or dispute themes
- •Ensuring insights align with product direction (or trigger deeper investigation)
- 22:37 – 24:37
Not just for B2B: product ops as a transparency and readiness function across industries
Christine challenges the assumption that product ops is only for B2B companies with sales and CS stakeholders. She argues the common thread is cross-functional transparency and readiness—needs that exist in large B2C organizations too.
- •Product ops shows up more visibly in B2B, but the need exists beyond it
- •B2C enterprises can have massive internal cross-functional complexity
- •Readiness: preparing internal teams and customers for change
- •Transparency and alignment as universal product scaling requirements
- 24:37 – 27:41
How to get buy-in: selling product ops to leaders and skeptical PMs
Christine outlines the arguments that most reliably earn executive and team buy-in. The core framing: protect PM time for customers and outcomes, and scale transparency so it isn’t dependent on a single heroic PM.
- •Start with: what are PMs measured on, and what should they focus on?
- •Pitch to leaders: stop PMs from constant revenue-team firefighting
- •Pitch to leaders: create scalable transparency and consistent outcome tracking
- •Successful rollouts usually require strong C-level/CPO sponsorship
- 27:41 – 29:47
What PMs should never offload: the irreducible core of product management
Christine makes a strong claim: PMs should never give up spending time with customers and observing pain firsthand. Product ops can remove noise, but the PM’s customer connection is non-negotiable.
- •Customer empathy as the foundation of good product decisions
- •Product ops exists to filter noise—not replace PM-customer contact
- •How the PM role has expanded over time, increasing the need for support
- 29:47 – 31:31
Before product ops exists: who does the work, and why planning/process is a common entry point
Lenny asks who handles product ops-type work before the role exists. Christine explains it typically falls on PMs (and sometimes agile/program roles), and that early product ops hires often start by making planning consistent—while bringing deeper product-and-customer context than pure program management.
- •Product ops work is usually done by PMs pre-hire
- •In less mature orgs, the first ask is often “streamline planning”
- •Key differentiator: product ops understands product, customer, and business mechanics
- •Why program management/agile can overlap but isn’t identical
- 31:31 – 37:24
Responding to Casey Winters: are ops roles a band-aid for inefficiency?
Christine addresses the critique that ops teams can signal organizational inefficiency. She argues ops is often a natural outcome of growth and complexity—and agrees that product ops should automate/hand off repeatable systems to focus humans on higher-leverage strategic work.
- •Ops as a sign of growth/opportunity, not always inefficiency
- •The goal: stand up systems/processes, then “get out of the way”
- •Mature product ops becomes strategic advisory and impact-driven
- •Comfort with change: automate, hand off, and continuously refocus
- 37:24 – 46:08
When you need product ops: Pendo’s “bad launch” story and measuring transparency gaps
Christine shares the moment that pushed Pendo to formalize product ops: a major launch went poorly due to readiness and transparency breakdowns. She explains how they diagnosed the problem, measured time drains and question volume, and built a repeatable product digest to improve alignment.
- •Warning sign: lack of transparency up/across/down the org
- •Pendo’s trigger: a major launch where teams knew “it was coming” but not how to act
- •Diagnosing with surveys: PM time spent firefighting vs. customer time; revenue question frequency
- •Creating a “product digest” focused on readiness (not just dates/status)
- 46:08 – 1:06:39
Product ops vs. product marketing, product ops career fit, and hiring advice (plus Pendo structure & lightning round)
Christine draws a clear boundary: PMM positions and sells; product ops educates and enables internal teams to use and support the product effectively. She then covers who thrives in product ops, where practitioners come from, job-description red flags, how Pendo structures product teams, and closes with a lightning round of recommendations.
- •PMM vs. product ops: positioning/selling vs. education/readiness and internal enablement
- •Who’s a fit: systems thinkers, cross-functional collaborators, data + synthesis oriented problem solvers
- •Common backgrounds: consulting, customer/technical success; leaders often come from PM
- •Red flag: unclear success metrics/outcomes for the role
- •Pendo structure: GMs over revenue streams, directors/PMs under them, shared product ops coverage across teams
- •Lightning round: books, podcasts, tools, and a process change—bringing engineers into customer meetings
