The Accountability Question (Selling Product Ops Internally)
Don't argue scope with defensive PMs — ask leaders what they hold PMs accountable to, then show what's crowding it out.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 91%
Product ops routinely dies on arrival because PMs read it as a land grab and leaders read it as unproven overhead. Itwaru's counter is to refuse the territory argument entirely and reframe around accountability: ask the leader what they are actually holding their PMs accountable for. Once the answer is 'understanding the customer and driving outcomes', the case makes itself, because everything else on the PM's plate is by definition not that. She then closes with exactly two pitch bullets, and insists the buy-in must come from the CPO or CEO level, not from peer PMs.
Origin
Christine Itwaru's coaching pattern, developed across her own rollout at Pendo and repeated with dozens of Pendo customers and product-community members who came to her saying their product ops rollout had stalled against internal resistance.
Core principles
- 01Scope arguments are unwinnable; accountability questions are.
- 02The PM's scarcest asset is time with customers and engineers — everything else is negotiable.
- 03Resistance to product ops is almost always a symptom of missing top-level buy-in, not of PM stubbornness.
- 04Two bullets beat a deck: firefighting displaces customer time, and one-off excellence doesn't scale.
- 05You must be able to articulate what the role drives for the business, not what tasks it absorbs.
How to run it
- 1
Ask the leader the accountability question
Before any pitch, ask: what are your people responsible for, and what are you holding them accountable to? Are you holding your PMs accountable to truly understanding the customer and elevating strategic insight — or to something else?
Pro tip This question gets everyone on the same page fast because almost no leader will say out loud that they hold PMs accountable to answering sales' questions.
- 2
Follow with the measurement question
Ask how they are measuring PM outcomes and where that is made transparent. This surfaces the second gap: outcomes that are measured inconsistently or only for the teams with an unusually diligent PM.
- 3
Deliver the two bullets that stick
Bullet one: do you want your PMs constantly fielding questions from your revenue team when they could be spending time with customers? Bullet two: how does this work happen consistently and at scale, rather than depending on one passionate person in one vertical?
Pro tip Itwaru reports these are the two that land most reliably. Both are about the PM's time and the org's scale — neither is about product ops' scope.
Watch out Do not lead with a task list of what product ops will take over — that is precisely the framing that makes PMs defensive.
- 4
Secure buy-in at CEO / CPO level before rollout
Get explicit endorsement from the CEO, CPO, or head of product, articulated as what the role will drive for them — not as a directive to the PM org. Every stalled rollout Itwaru has seen traces back to missing buy-in at this level.
Pro tip Frame it forward: mature product ops people become strategic advisors to the product leader — so the ask is 'here is what you get from me and this team', not 'here is a new process for your PMs'.
Watch out Rolling out product ops with only PM-level agreement guarantees the 'you're stepping on my toes' fight, and you will lose it.
- 5
Draw the lines against adjacent roles
Be ready to explain what distinguishes product ops from program management and agile facilitation: product ops people understand the product, the customer, and the inner workings of the business. And what distinguishes it from product marketing: PMM positions and sells; product ops educates internal teams on the value and the how.
In the wild
Itwaru repeatedly had people from the product community come to her saying they had tried to stand up product ops and it went nowhere — the role was seen as stepping on too many toes. In every case she traced it back to the same thing: they still had buy-in left to secure at the top.
→ The rollouts that succeeded and demonstrably drew the lines were the ones with explicit CEO/CPO-level sponsorship framed as what the role drives for the business.
Asked by Lenny for the bullet points that actually convince a product leader, Itwaru named exactly two: PMs fielding revenue-team questions instead of being with customers, and excellence that exists in one vertical because one person is passionate about it but never scales across the org.
→ Lenny's visible reaction confirmed the first bullet lands immediately; Itwaru identifies these two as the ones that 'stick the most' across her customer conversations.
Common mistakes
Pitching product ops as task relief
Listing what you will take off PMs' plates invites a boundary negotiation and reads as encroachment. Anchoring on what PMs are accountable to sidesteps the fight entirely.
Starting the rollout at the PM layer
Without CEO/CPO endorsement, product ops has no mandate and every scope conflict becomes a peer-to-peer standoff. Buy-in at the top is the precondition, not a nice-to-have.
Blocking PMs from customers to 'protect their time'
Itwaru is emphatic that customer contact is the one thing PMs must never offload. Companies that block PMs from customers 'are not product companies'. Product ops protects that time; it never absorbs it.
Is it for you?
Best for
An aspiring first product ops hire, or a product leader trying to justify the function to a CEO while pre-empting the PM org reading it as a threat.
Not ideal for
Orgs where the head of product is already the bottleneck being defended — if the accountability answer is genuinely 'shipping on time', product ops is not the fix you need.
From the transcript
“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”
“number one do you want your PMS to constantly be Fielding questions from your Revenue team when they could be spending time with customers”
“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…”
“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…”
From the episode
Understanding the role of product ops
Christine Itwaru (Pendo)