Nov 16, 2023 · 1h 19m · lennys-podcast
The ultimate guide to product operations | Melissa Perri and Denise Tilles
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview with Lenny Rachitsky, product leaders Melissa Perri and Denise Tilles unpack the core concepts of their book, 'Product Operations,' demonstrating how dedicated operational infrastructure frees product managers from administrative burdens to focus on strategic execution. They outline the three foundational pillars of product ops, lean team sizing, and practical implementation blueprints for high-growth startups and large enterprises.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 21.9% of the talking time here. How this is scored →
Lenny as informed peer 3.9 Guest teaching 3.8 Guest disagreement 0.9 Lenny pushing back 1.3
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 38:02 Defending product ops against the anti-ops framing
Melissa counters Casey Winters' premise that ops roles simply compensate for inadequate software, arguing ops acts as a lean builder of internal systems.
Hardest push from Lenny ▶ 37:55 Lenny cites Casey Winters on ops vs software efficiencyLenny challenges the necessity of adding operational roles by citing Casey Winters' view that operational headcount often masks product inefficiencies.
Biggest teaching moment ▶ 1:02:00 Melissa explains why executive portfolio views cannot live in JiraMelissa recounts how an enterprise CEO got lost digging through thousands of individual Jira tickets, demonstrating why high-level portfolio infrastructure is essential.
Lenny holds their own ▶ 20:50 Lenny compares product ops delegation to the startup engineering tradeoffLenny synthesizes operational delegation with the classic dilemma of engineers resisting non-coding project tasks, proving his deep operational product knowledge.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| The Emergence and Widespread Growth of Product Operations | 4 | 3 | 1 | 1 | Lenny sets context by citing fast-growing tech companies like OpenAI, Stripe, and Ramp that use product ops. Melissa and Denise explain the timeline of the discipline and how Blake Samick seeded it across multiple major firms. | |
| Overcoming PM Apprehension and Enabling Strategic Work | 5 | 4 | 1 | 2 | Lenny voices the natural hesitation PMs have regarding handing over data harvesting and user calls. Melissa firmly clarifies that product operations does not strip decision rights but removes distracting operational burden like writing MongoDB queries. | |
| The Three Pillars of Product Operations Explained | 4 | 5 | 1 | 1 | Denise outlines the three core pillars of product operations: business data, customer insights, and process governance. Melissa educates Lenny on how high-growth startups prioritize data insights while enterprise transformations focus heavily on governance and roadmapping systems. | |
| Product Management Evolution and Reducing Operational Overhead | 6 | 3 | 1 | 2 | Lenny notes that product management historically resists specialization and draws parallels to startup engineering tradeoffs. Melissa and Denise explain that leadership overhead and cognitive context switching make dedicated ops infrastructure essential at scale. | |
| Preserving PM Decision Rights, GTM Alignment, and Role Boundaries | 5 | 4 | 1 | 1 | Lenny recaps the boundaries of core PM responsibilities such as strategy and trade-offs. Denise adds go-to-market alignment as a critical bridge where product ops eliminates cross-departmental friction. | |
| Deep Dive on Business and Data Insights for Leaders and PMs | 5 | 5 | 1 | 2 | Lenny pushes on the idea that analyzing data is inherently core to product management. Melissa explains that product ops constructs repeatable executive dashboards and data views so PMs and CPOs spend time interpreting strategy rather than wrestling with SQL and board slide preparation. | |
| Sponsor Message: Jira Product Discovery (Mid-Roll) | 5 | 4 | 2 | 3 | Lenny brings up Casey Winters' contrarian perspective that operational headcount often signals product deficiencies. Melissa pushes back slightly, arguing that product ops functions as a lean leverage mechanism to build tools for product teams rather than an army of manual coordinators. | |
| Rollout Strategy and Hiring the First Product Ops Specialist | 4 | 5 | 1 | 1 | Denise and Melissa detail early rollout sequencing, advising teams to start with one person targeting the highest-friction pillar. Melissa differentiates between analytical consultant profiles for data pillars and research ops backgrounds for qualitative insight systems. | |
| Organizational Reporting Lines and Working with Executive Leadership | 3 | 4 | 1 | 1 | Melissa emphasizes that product ops must report directly to the head of product to function as an executive force multiplier and right-hand operator for strategic data. | |
| Case Study: Implementing Product Operations at Athenahealth | 3 | 6 | 1 | 1 | Melissa delivers an in-depth case study on rolling out product ops across 360+ PMs at Athenahealth. She explains how Jira failed to provide portfolio visibility to the CEO and how establishing governance and data tooling stabilized product strategy through corporate restructuring. | |
| Lightning Round: Favorite Books, Media, Questions, and Mottos | 2 | 2 | 0 | 0 | A collaborative lightning round where guests share favorite books, interviewing techniques, product tools like Dragonboat and Dovetail, and personal mottos. | |
| Where to Find the Book and Connect with the Authors | 1 | 1 | 0 | 0 | Standard wrap-up segment where Melissa and Denise share contact details and invite listeners to provide real-world product ops feedback. |
Statements from this episode (17)
Perri: Blake Samick established product operations at Uber, Stripe, and OpenAI
“The head of product operations at Uber and the person who started it, Blake Samick, is a case study in our book, and he also did it at Stripe, and he does it at OpenAI”
Tilles: 60% of masterclass students now operate a product ops function
“When we started offering this class in 2020, about 60% were products curious. And as time has gone on, it's really gone down and people have started to add it. They just want to understand what's the best way to optimize it. So I would say it's gone from that …”
Tilles: Product managers spend 20% to 30% of time harvesting data
“In my role on the operating side and managing teams and Melissa as well, more and more product managers are taking on the data harvesting, the data implementation, and, you know, just to get data to work with, they're spending, you know, 20, 30% of their time.”
Perri: Product ops informs PMs without removing decision rights
“Product operations does not take away decision making rights from the product manager. It's there to inform them.”
Perri: Startups adopt product ops for data; enterprises for process
“So we usually see that high growth companies start with business data and insights and make sure that they have, they can actually monitor what they're doing and get the strategic inputs. We see larger companies and enterprises kind of go more towards the proc…”
Perri: Jira does not work for enterprise-wide product roadmaps
“And, like, JIRA does not work for that, right? You need a portfolio tool to be able to roll that up Into something that makes sense.”
Rachitsky: More than half of companies will adopt product ops within years
“Today, half of companies essentially have a product ops role. And I'm guessing in another few years, it'll be much higher.”
Perri: Many Harvard MBAs abandoned PM careers after role simulation
“I, you know, I saw with my MBA students at Harvard too, we do a whole class They play a product manager. I had a lot of people opt out of being a product manager at the end of it. They were like, I did not realize it was like that, right? Like I did not realiz…”
Perri: PMs should never outsource product decision-making to product ops
“You should never be like outsourcing your decision making to a product ops person. That's not the point. Like they're the product manager for the product managers. That's how I think about it, right? So their decisions should be around how do I operationalize …”
Perri: Product ops is not project management or stakeholder trade-off arbitration
“They're not project managers. They're not the people who are going to be on top of your developers, like watching them build things, making sure that everything's out on time. That's not their role either. They're not going to handle hard stakeholder conversat…”
Perri: ARR becomes strategically actionable only when segmented by customer and product
“ARR is interesting to me, but it's not as interesting to me as ARR by customer segment, right? It's not as interesting as ARR by product line. It's not as interesting if I take that and then look at it by retention or adoption by product or feature set or adop…”
Perri: PMs must master data analysis even if product ops handles SQL
“And I think for product managers, you still need to be super comfortable with data. Like if you can't read these charts, if you can't see, understand trends, if, you know, and a lot of times too, if you're putting this stuff in Looker or, you know, a BI tool, …”
Perri: A 1-to-1 product ops to product manager ratio is fundamentally wrong
“I don't have a hard and fast rule on that one, but I would say like if you're at a one-to-one ratio, like you're doing it wrong.”
Perri: Agile coaches without product management experience struggle in product ops
“And agile coaches who have never been a product manager before in a well-run company are going to struggle there because they're going to revert back to agile processes and optimizing for things like scrum, but they're not going to do what that role is designe…”
Perri: Hire consultants instead of database engineers for data product ops
“What I wouldn't hire for that role as a first person is like a data.
It's not a database engineer, right?
Like that's not what we're doing.
We're not like
Sequel-ing, like turning things into the right SQL tables.
Like we're instead trying to get the info…”
Perri: High-growth CPOs should make product ops their first hire
“And we say to a lot of CPOs, especially like high growth companies, like make your first hire just a product ops person to help you get this data out and start looking at it because that helps them with board meetings. It helps them set strategy.”