What product ops does and when your company needs it

Executive overview

Product managers carry too much: customer research, stakeholder alignment, tooling, planning, and internal education all compete with the core job of building great product. Product ops relieves that pressure by owning the surrounding system so PMs can focus on customers and outcomes.

The role has two definitions: a thing (a system a strong product leader builds) and a person or team (a dedicated partner to PMs, and eventually a strategic advisor to the CPO). Both are valid; companies don't always need humans to fill the gap.

The core insight: product ops exists to build the system, then get out of the way — moving toward higher-leverage strategic work as processes mature.

What triggered the rise of product ops

• Problems always existed; the role formalised around 2019 as growth, product-led tactics, and org complexity converged
• Rapid pandemic-era growth across industries exposed gaps in voice-of-customer management, internal alignment, and stakeholder transparency
• As CPO scope expanded from "deliver features" to "drive business outcomes," PMs needed a support structure analogous to what marketing and sales ops already had
• Appointing a PM to liaise with other ops teams risked their product portfolio and customer goals

What product ops people actually do

• Voice of customer management — aggregating qualitative and quantitative inputs from customer success, sales, research, and NPS; synthesising them for PMs; educating revenue teams so not every complaint requires a product change
• Tooling — owning the PM tool stack (Pendo, Salesforce, Looker, Zapier, etc.) to ensure PMs have a complete data picture; distinct from the planning tool stack
• Content and education strategy — weaving education into the product (in-app guides, Zendesk articles); treating content as part of the definition of done; enabling PLG loops around retention and upgrade
• Process and planning — often the first wedge into less mature orgs; streamlining how teams plan and share roadmap status; distinct from pure agile facilitation by deep product and customer knowledge
• Internal transparency — bridging product and revenue teams; surfacing what's coming and what to do with it, not just that it exists; the line between product ops and PMM is that PMM positions and sells, product ops educates internally

Signs your company needs product ops

• PMs spend significant time fielding questions from the revenue team instead of talking to customers
• Outcomes aren't tracked or communicated consistently across the org
• Internal teams know something is launching but don't know how to prepare or position it
• A bad launch exposed gaps in cross-functional readiness (the Pendo origin story)
• Quality of inbound questions from sales and success is low — reactive firefighting rather than strategic input

Getting buy-in from product leaders and PMs

• Frame it around PM time: "Do you want your PMs fielding revenue questions, or talking to customers?"
• Frame it around scale: passionate individual PMs doing this for their vertical doesn't compound; product ops makes it consistent across the org
• Buy-in must come from CPO or head of product level — without it, the role stalls as a perceived threat
• PMs should never give up customer time; everything else is on the table

The ops-as-inefficiency debate

• Ops alignment across mature functions (marketing, sales, product) is a natural evolution, not a symptom of dysfunction
• The stronger version of the critique is valid: product ops should stand up systems and processes, then hand them off or automate them — not maintain them indefinitely
• Successful product ops people are comfortable letting go; they continuously move toward higher-leverage work
• AI and automation will accelerate this transition; teams that treat process ownership as a permanent identity will struggle

Career path into product ops

• Day-to-day product ops managers often come from management consulting, customer success, or technical success
• Product ops leaders (first hire, director level) almost always have hands-on product management experience — essential for knowing where to place effort and for credibility with engineering and CPO
• Fit signals: love of cross-functional team health, curiosity about the inner workings of the business, comfort with letting go of processes you built
• Red flag in job descriptions: no clear success metrics or definition of outcomes for the role
• The role is no longer seen primarily as a threat by PMs — more experienced PMs are choosing to move into it

How Pendo structures product ops

• Business units led by GMs (all with PM backgrounds), senior directors, and cross-functional product teams beneath
• Product ops people are embedded but shared across two or three teams rather than dedicated 1:1
• Allocation is revisited each quarter based on goals, not a fixed ratio
• Early-stage products get lighter-touch ops ("respect the hustle") — faster voice-of-customer loops, less process overhead
• Mature products get more structured voice-of-customer synthesis and planning rigour

One change with outsized impact

• Bringing engineers into customer meetings — even as observers — shifted planning significantly
• Engineers gained direct exposure to customer pain and delight; their voice carried more weight in the product development lifecycle
• Initially met with nerves; quickly became something engineers wanted more of